neomutt
micro-editor
neomutt | micro-editor | |
---|---|---|
11 | 227 | |
3,082 | 23,986 | |
1.3% | - | |
9.8 | 9.4 | |
6 days ago | 5 days ago | |
C | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
neomutt
-
Show HN: Inbox Zero – open-source email assistant
https://github.com/neomutt/neomutt is a mature project with similar functionality in its arsenal via tagging and vim bindings, not limited to gmail either. You can also write emails in vim/$EDITOR fluidly.
-
How to build neomutt from scratch with notmuch support?
I checked out the neomut repo and notmuch repo and unpacked ncurses 6.4
-
How to compile neomutt with notmuch support?
git clone https://github.com/neomutt/neomutt ./configure --notmuch --with-notmuch=/usr/local/lib/notmuch And because it gives me the error: Checking for DocBook DTDs... Error: couldn't execute "xmlcatalog": no such file or directory ... I just disable it, because I don't need a book:
- How to set up Neomutt for Gmail?
- Neomutt flatpak! First stab at a flatpakaged neomutt...
-
Mutt 2.2.0
I think it's always worth mentioning neomutt[1] when mutt comes up these days. Development is fairly active [2] and a lot of patches that people have been working on over the years have been merged, like the various header compression techniques, sidebar, search and unified inbox with notmuch etc.
[1] https://neomutt.org/feature
[2] https://github.com/neomutt/neomutt
-
neomutt + vieb
based on this: https://github.com/neomutt/neomutt/issues/717
- Help developing terminal based applications
-
Example / precedents and best practices for salt formulas which build software from a git repo?
I'd also like to do a similar thing with neomutt, which will definitely have to be built from source.
micro-editor
- Ask HN: What software sparks joy when using?
- Modeless Vim
-
Essential Command Line Tools for Developers
To see more screenshots of micro, showcasing some of the default color schemes, see here.
-
Go: What We Got Right, What We Got Wrong
Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:
- gdu: a NCDU clone, much faster on SSD mounts [1]
- duf: a `df` clone with a nicer interface [2]
- massren: a `vidir` clone (simpler to use but with fewer options) [3]
- gotop: a `top` clone [4]
- micro: a nice TUI editor [5]
Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.
[1]: https://github.com/dundee/gdu
[2]: https://github.com/muesli/duf
[3]: https://github.com/laurent22/massren
[4]: https://github.com/xxxserxxx/gotop
[5]: https://github.com/zyedidia/micro
-
Text Editor: Data Structures
> The worst way to store and manipulate text is to use an array.
Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.
Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.
Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).
[1] https://github.com/zyedidia/micro
[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...
[3] https://github.com/cessen/ropey/pull/67
- A nano like text editor built with pure C
-
A simple guide for configuring sudo and doas
There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:
-
what terminal emulator do you use and why?
found that micro has dedicated info page for copy paste
-
Microsoft is exploring adding a command line text editor into Windows, and it wants your feedback
micro: winget install zyedidia.micro
- What is the best basic ass text editor?
What are some alternatives?
mutt-office365 - A mutt configuration file ready for Office 365
helix - A post-modern modal text editor.
offlineimap - Read/sync your IMAP mailboxes (python2) [LEGACY: move to offlineimap3]
filemanager-plugin - A file manager plugin for the editor "Micro"
sd - Intuitive find & replace CLI (sed alternative)
kakoune - mawww's experiment for a better code editor
Sylpheed - A mirror of the official sylpheed svn repository located at svn://sylpheed.sraoss.jp/sylpheed. The mirror does not include the branches.
xclip - Command line interface to the X11 clipboard
neovim - Vim-fork focused on extensibility and usability
vim-surround - surround.vim: Delete/change/add parentheses/quotes/XML-tags/much more with ease
nntpit - minimalist reddit2nntp gateway
editorconfig-core-go - EditorConfig Core written in Go