What is Reddit's opinion of
Micro?
From 3.5 billion Reddit comments
➔ Micro website
By popularity on Reddit, this Service is:
59 reviews of this app found across Reddit:
Check out <code>micro</code> sometime. It has a similar ease-of-use focused design, but uses standard "modern" editor shortcuts so it works kind of like a terminal-based notepad.exe, except with more features and extensible via Lua. So kind of like notepad++ for the terminal I guess. I still tend to use vim and emacs for most things but micro replaced my "fuckit, use nano" moments.
Remapping keys is normal, but you really can't configure the modes out of vim. If you want to do things like select and copy text from insert mode, then you want a different editor. It is theoretically possible to force vim to do things in ways it really isn't supposed to do them, but if that is your plan then there is no reason to use vim. I recommend instead something like micro which is a decent command line editor which is probably much closer to what you are used to.
Vim is much more powerful than micro, but in order to access that power you have to be willing to learn it.
I recommend taking a look at micro (sudo snap install micro --classic). It's basically a modern nano with all of the shortcuts etc that you would expect in a graphical text editor.
Again, gotta plug micro, it's got even better defaults (like ctrl-S to save, like literally every other app you use), syntax highlighting so you can more quickly see if you fucked something up when editing a config file, quality mouse support so you can highlight and copy and paste text just like a GUI editor, multiple cursors so you can so shit like change indents quickly, and a plugin system. All without complicating the whole ordeal, it's a nano replacement and not vim, emacs, or a complete IDE by itself.
There are a lot underrated, but well known standard tools (like grep, sed, awk, journalctl, etc).
But there is this one tool, I wasn't aware of for a long time and using it constantly since then:
micro - it is such a nice editor, that I really wondered how I was able to miss it and still don't get why distributions integrate nano as a default editor instead. ;)
Nano is great for quick little edits in various config files and that sort of thing - but over the last year or so I've found myself using Micro more and more. It's a happy medium between a simple editor such as Nano and the more feature-rich 'I Can't Believe It's Not An IDE?!' VSCode.
Hmmm, come to think of it, Micro offer roughly the same functionality that Notepadqq do but none of that GUI fluff. :)
Is quite good, you can extend it as you like, is made in Go but last time i've check you can write plugins are in LUA.
I just start using micro. Very light and very easy to use. Plus I like it.
https://micro-editor.github.io/
As for GUI text editor's. I really like Pluma with all the extra plugin's.
I get my work done using either or.
I was using Spacemacs for a while. Just moving on now. Sometime down the road, I'll be trying out NeoVim. Yes, I know how to use Vim and Emacs text editors.
My favorite CLI that I always go to is ne. When I want to get away what I'm currently using. I just like to change batters sometimes.
I like all text editor's. I try about everyone there is out there. I miss a few, especially the new one's. Like we need another Text Editor. I always say why not.
Try micro,
it has the usual keybindings
(except for tabs, Alt , is previous tab and Alt . is next tab).
For that, I highly suggest checking out the micro text editor, as it's basically an enhanced version of nano. Still dead simple to use, but it has better keybindings (ctrl-S to save, ctrl-Q to quit, ctrl-c and v to copy and paste, etc), it'll do multiple cursors, built in mouse support so you can just highlight and copy text as though you were using a GUI editor, it has plugin support to do syntax highlighting which is really handy for editing config files, whole kit and kaboodle. It makes for a very pleasant nano replacement.
I've been trying out neovim recently myself, and yeah it's a p steep learning curve. I do like that I don't have to shift my grip much from home row to do most stuff, but the need to tap the ESC key a bunch and the inevitable accident of finding out I'm in the wrong mode and typing a bunch of complete nonsense commands that fuck everything up, then hitting U iunno how many times to try to get back to where I was, it's just a mess. Like having to hit ESC to go back to using hjkl as arrow keys, the maybe one good bit of nvim I can really, really appreciate, it just negates the ergonomics improvement. I'd rather just use both my keyboard and mouse simultaneously to quickly and precisely select and then edit the text I want without having to stop a second to think about how I'm going to navigate my cursor wherever.
I knew someone was going to say that, though I came to the comments to make the same joke just in case nobody already had. :)
If that's what OP wants to use, nothing wrong with it. It at least syntax highlights so it's better than notepad, which a lot of people use especially early on.
Though I'd suggest at least trying micro out instead. It's similarly newbie-friendly, but has more features, its shortcuts are more like modern applications (ctrl-s to save, ctrl-f to find, etc.), and is extensible with Lua. Still not necessarily the endgame choice for programming but a good step up while having a low learning curve. Should be in basically every distro by now too, so apt install micro (or whatever your distro's equivalent is) and you're good to go.
Try out micro before moving to vim. Vim and Emacs are great text editor's to learn. But for some reason I'm still using micro.
​
https://micro-editor.github.io/
​
It's nano on steroids.
>Basically everyone tells me that vim is better then nano for some reason
Basically, the same two reasons are always given. Vim is installed everywhere. And vim offers more features than, for example, nano and therefore you can work more productively.
Yes, vim is installed in most cases. But not every user works on computers where he has no influence on the installed software. I suspect that many of the users of /r/linux4noobs even work only with their own machines and this reason is therefore unimportant.
Yes, vim has a very large feature set. But do you need it? In addition, nano, for example, also offers many more functions than those displayed at the bottom of the screen (for example, https://www.nano-editor.org/dist/latest/cheatsheet.html or https://www.nano-editor.org/dist/latest/nano.html#Nanorc-Files).
In short, one should not always listen to others. Just use the programs that suit you and not those that suit others. Which is not to say that you shouldn't use vim. But if you like another editor like nano or micro more, use it. For my part, after several attempts with vim over the last 20 years, I can say with a clear conscience that vim is not for me. Or I don't for vim. Therefore I also just use another editor. In my case micro and VSCode.
I like the idea of disconnecting from Google, but it's no priority for me. I want this device to code a bit while on the move and perhaps write some short blog posts.
So the setup I'm looking at is really the default Android, and then install Termux there and run Micro as a code editor. Any suggestions for good Android code editors are welcome (or a way to make VSCode work on Android :)
I'm curious about running another OS, especially a linux one, but I don't know which one to pick and how to test one before installing it. If I can't test I'll probably just wait a bit to see what others recommend.
Nice! Those first days in a strange new posixy OS definitely had a distinct feel to them - the feel of wonder and newness. Although that fades, there are always new things to learn and new cool tools to use :-)
Here are a few of my favorite linux tools:
ssh
neovim
tmsu
mpc
mpv with mpris.so so that I can control it with:
kdeconnect (doesn't require the KDE desktop)
You don't have to learn vim though; you can get by with nano and then switch to something like micro
I actually don't think this is a crouton-specific problem. I've seen the exact same issue you describe occur on a chromebrew pkg of nano (ie: natively installed and running on chromeos). It looks like a libncurses problem (thats the lib which terminal apps use for full screen addressing, and it maintains alternate screen buffers and switched between them). Upgrading libncurses and recompiling nano worked for a while, but then the problem came back sporadically and (as a 20+ year vim user) I haven't bothered to debug it ...
If you don't want to go down the tried and trusted (n)vim or emacs route, and something like acme (via plan9port) is too exotic for your tastes (it really replaces your entired terminal, not just your text editor), and you just want a simple, basically capable, non-gui text editor (otherwise, why use nano?), have a look at micro.
It fills all the above criteria, plus its a single, statically compiled binary. So you can just download and go ...
You can try micro. Its a very light weight text editor that works in a terminal emulator, has auto syntax detection, auto indentation, split screen and also great mouse support among other features. It has the same keyboard shortcuts as any regular text editor.
In a GUI setting, Kate.
On the terminal, micro. It has mouse support and works just like 99% of all Linux, Mac and Windows programs -- for example, 'save' is CTRL-S and not some utterly idiosyncratic holdover from the days of punchcards, like "change to command mode" + "select IO mode" + "key combo not used for saving in any other program in existance". With micro, you often forget you're even in a console program!
The wget instructions I see on their website are only for Arch Linux, which uses Arch Linux' ports system to build a package for Arch Linux. Instead, from the link I shared https://micro-editor.github.io/ just click on Download and download either the *linux64.tar.gz or *linux32.tar.gz file from the next page, depending on respectively whether you have a 64 bit or 32 bit installation.
After downloading the file first ensure you have created the bin directory (all in lower case letters) in your home directory, as by default Linux Mint adds that to your path as a place to search for programs. Then open the downloaded file with the archive manager by double-clicking it in your file manager. Extract the file micro you find in the directory in the archive to the bin directory in your home directory.
If you already had the bin directory you can now run micro. If you just created the bin directory either source your .profile file with . ~/.profile or open a new terminal, either of which will add the just created bin directory to your path. Then you can also run micro.
With that it works just fine on Linux Mint 17.3, 18 and LMDE 2.
I like (and use a lot) the Micro text editor. it is simple and reliable, with some plugins and support practical customization. An alternative to those who doesn't like vi or emacs.
https://micro-editor.github.io/
There is another one only for windows, that I never used myself, but looks even simpler but kinda cool. (distraction free, DOS/WPF look n feel)
https://www.pixelprophecy.com/stuff/index.php/downloads/download/5-tools/19-scully-windows
https://www.pixelprophecy.com/stuff/index.php/downloads/download/6-sources/20-scully-c-wpf-source
we've all been there, glad it worked out. which file browser did you end up using? once you get a feel for the bash command-line, the easiest way to do this is
touch filename.txt
which creates an empty file by the name filename.txt. then you edit its contents however you want (for a starter-friendly command-line text editor, I recommend micro.)
micro is the new nano.
Or at least has a potential to be.
Out of the box feature rich and usable while being comfy.
All the expected keybinds working, elevate to root on save, multicursor, mouse integration, syntax highlight,..
OP /u/DaymanTargaryen will be still struggling to get half of these in vim after a month of use, let alone the mess that will be to move plugins and config to some other machine.
Lately I've become a big fan of Micro. It's as portable as Nano. By default it uses the same shortcuts as typical desktop programs: Ctrl-S for save, Ctrl-Q for quit, Ctrl-C/Ctrl-V for copy/paste, etc. It integrates well with Linux desktops' clipboards by optionally using xclip. Just like Nano, it can have multiple files open for easy copy/pasting between files. But the best thing of all is that its scripting/plugin system is plain old Lua 5.1.
ctrl g for Help
by default help keys should be shown
check their web site https://micro-editor.github.io/index.html
I like the editor but many prefer vim or nano, just personal preference
I found this editor using Termux on my Android phone, now have in on my laptop
😼
I actually really suggest checking out micro. It's a lot like nano (get it?), but with some nice QoL improvements. You can use your mouse, it supports colors for a bunch of languages right out of the box, it's a static binary without no dependencies, there's a plugin system to extend its functionality if you wish.
But most importantly, the default keybindings match what literally every other text editor in existence uses. You can finally just hit ctrl-S to save. It's beautiful. Really all you want out of a minimal text editor, lets you poke in and write or edit some files as Windows users might do with regular 'ole Notepad without trying to replace your other text tools.
Command Line editor = nano is hugely common but I'd advise getting micro as it's far better than nano, IMO. https://micro-editor.github.io/
Single binary, no dependencies, easy to install.
Sane default keybindings especially for users used to Windows.
Like CTRL+C for Copy / CTRL+V for paste
The editor itself features a notable upgrade from nano, with syntax highlighting for most common file types. In addition, you’ll find a column for line numbers, in addition to two lines at the bottom for the UI. There's also support for colour themes
One thing you’ll quickly notice is that micro has proper mouse support. Unlike nano, you can scroll the whole window properly with the scroll wheel (rather than moving the cursor down a line), and you can click anywhere to move the cursor. You can drag to select text as well.
Full list of features - https://github.com/zyedidia/micro#features
This is possible, sure, but not easy or recommended. If you want to do things without leaving insert mode, then you probably would be better served using a different editor. While it is theoretically possible to configure the modes out of vim, it is difficult, and goes completely against the grain of how vim is supposed to work.
If you want a fairly powerful terminal based editor that will behave in a way that you are used to from other editors, try micro.
If you want to use vim, then I strongly recommend trying to learn to use it the way it is intended, and that means abandoning the idea of using insert mode for anything other than inserting text.
I like them all. I even broke down and learned vim and emacs. But I settle with micro, it's nano on steroids.
https://micro-editor.github.io/
You use what ever you're comfortable with and just does the job for you well enough. That can be from nano to vim/emacs or anything between.
>that are as powerful as VIM and as user friendly as Nano( for us newbs)
Nano should not be underestimated. Although the editor does not offer the range of functions of vim (which probably only a few people use completely anyway), nano offers considerably more functions than those displayed at the bottom of the screen (https://www.nano-editor.org/dist/latest/cheatsheet.html https://www.nano-editor.org/dist/latest/nano.html).
Personally, I prefer micro. This also offers many functions (although not as many as vim). A big advantage for me is that you can use the widely used shortcuts like Ctrl + s with this editor.
Nano has significantly more functions than many people think (https://www.nano-editor.org/docs.php). Among other things also syntax highlighting. From my point of view there is nothing to be said against using nano for programming. Nevertheless I would like to draw your attention to the alternative micro. This editor uses the widely used shortcuts like Ctrl+S and is located between vim and nano in terms of features.
Micro editor for writing code, gdb for debugging, plus a handful of shell scripts for projectwide find + replace. Gives me most of the features I care about in an IDE, without the bloat and sluggishness of actually using one.
But I think that's only a factor for me because I have to switch from project to project fairly often, and the startup times on IDEs drive me nuts.
quickest way to make notes while I'm in the terminal. I couldn't find one I like that other's made so I made my own call sn for simple note.
https://github.com/linuxllc/sn
My favorite text editor is micro
https://micro-editor.github.io/
I use tmux a lot. Try to learn tmux and see if it improves your workflow any.
I guess the best thing first is organization. Keep things in one area and label it, name it, date it or what ever so you can find it very easy, in a search.
I build from source a lot. So I keep all my work at ~/bin where it's in my $PATH and made it where anything in there can be easily executed with a short command as in my ~/bash_aliases folder.
Even the simplest things can be improve. Especially when you discover a script or a tool to just make if faster or accessible. Just think hard and have a least a little imagination. And you can have a quick workflow.
It sounds like you know how to use an IDE. Have you dug in and learned vim?
I personally find a full IDE like Visual Studio to be too much for my liking, too many things to work around, with the bit less in VSCode better. After VSCode though, my next choice is probably Vim.
If you haven't tried Vim, in a nutshell most text editors are more of a start to finish experience. You can do that with Vim, I know people that spend years going into insert mode and typing everything, but it's far more than that. Outside of that mode Vim drastically changes your movement within the text, and the movement of text around your cursor.
Also, since Vim is a CLI based editor, you can use it over SSH and edit files on a remote server. If you have tried micro (https://micro-editor.github.io) it brings that same benefit (if it's already there). In a full IDE, the same is usually not possible because it just doesn't run via SSH - XForwarding is not the same. With a full IDE, you usually go for a "next best" option like SSHFS or a remote editor server then your editor is in a browser.
Plus, I often find myself working on someone else's server. In that situation, I can't add whatever I want. If it's *nix, Vim's there, and the stock configuration is good enough.
Visual Studio is quite bloated. I've used it, can't say I liked it. Now VSCode on the other hand, although a much simpler IDE, is a fantastic tool. I write all my programs using VSCode. On Linux.
For simpler edits of config files and such, I use a little editor called Micro (https://micro-editor.github.io/) - this I also have installed on all the server VMs I'm running on Google Cloud.
Micro runs in the terminal, is mouse enabled and use common modern shortcuts rather than the ancient non-standard ones found in other terminal-editors. It have syntax highlighting for all the popular languages plus a hundred more. All in all, it's great.
imo micro is the best editor. It runs in the terminal, has mouse and X clipboard support, it does syntax highlighting, it's expandable, It has a built-in terminal emulator, it can have multiple cursors, and with a plugin it can format code
[link](https;//micro-editor.github.io)
I mainly use Sublime Text or micro. Why? Because they are two tools that suit me and therefore I can achieve what I want. And I think that's what matters. The tools you use have to suit you and not others.
However, I avoid the use of vim like the devil avoids holy water. The operation of vim is just too different from other programs I use. And I simply edit files too irregularly and rarely than I can remember all the shortcuts.
In the meantime I personally prefer mirco to nano. On the one hand because the shortcuts are more oriented on the widely used shortcuts like Ctrl + S. And on the other hand because the range of functions is more extensive.
I recently saw some i3 videos on Youtube. I'll give that a try. Sounds like a nice way to go without fully committing.
I suppose tmux is geared more towards Window Managers? I use Yakuake here on Manjoro KDE (and Guake before it on Ubuntu with Gnome; and iterm2 before that on Mac OS.)
In regards to text editors, I use nano on occasion when I want to edit a simple file while in the terminal. I also setup an alias subl and use the zsh/oh my zsh st sublime plugin but, it's going to be hard for me to give up ST3 and Code entirely. Micro looks nicer, though. Getting rid of the GUIs for editors and for things like git et al. would definitely force me to learn more, that's true.
Although, I wonder how long my workflow would suffer before I became proficient enough to warrant living in the terminal all the time; not to mention remembering all the commands and constantly having to look up stuff after forgetting it (and why in the past I usually just fall back to GUIs, 'cause, you know, #lazyweb.) I realize there are snippets and aliases manager and such, however.
I have some experience running cron jobs and writing bash scripts, being a web developer and all but, never have I needed cron locally. And lately I've been writing python for things that might as easily been done in bash.
Anyway, thanks for the tips, I appreciate it!
I recently saw some i3 videos on Youtube. I'll give that a try. Sounds like a nice way to go without fully committing.
I suppose tmux is geared more towards Window Managers? I use Yakuake here on Manjaro KDE (and Guake before it on Ubuntu with Gnome; and iterm2 before that on Mac OS.)
In regards to text editors, I use nano on occasion when I want to edit a simple file while in the terminal. I also setup an alias subl and use the zsh/oh my zsh st sublime plugin but, it's going to be hard for me to give up ST3 and Code entirely. Micro looks nicer, though. Getting rid of the GUIs for editors and for things like git et al. would definitely force me to learn more, that's true.
Although, I wonder how long my workflow would suffer before I became proficient enough to warrant living in the terminal all the time; not to mention remembering all the commands and constantly having to look up stuff after forgetting it (and why in the past I usually just fall back to GUIs, 'cause, you know, #lazyweb.) I realize there are snippets and aliases manager and such, however.
I have some experience running cron jobs and writing bash scripts, being a web developer and all but, never have I needed cron locally. And lately I've been writing python for things that might as easily been done in bash.
Anyway, thanks for the tips, I appreciate it!
Maybe not the right thread, sorry.
I'm a big fan of Micro text editor (https://micro-editor.github.io/), which provides great keybindings for coding.
Usually, many text editors embeds a default file-tree pane. Micro also features that, but in a limited way.
I'm wondering if some people here use a side-by-side panel view: left cmdline pane for nnn (used as "file tree pane") and right cmdline pane for their favorite text-editor (Micro in my context). nnn used as a file-tree browser (and more). When selecting a file in nnn, the right pane would be automatically updated.. I would like to use such a workflow, but..
With my current workflow, I use 1 cmdline pane: nnn to browse files and then edit (externally) the file with nnn ; I would like instead to always see the file tree while editing source-code.
Your thoughts/workflow proposals for that? Thank you
> But I still need to say that it’s probably not a good idea to have the full SDK running on your VPS.
SDK or IDE?
> you should check out VSCode Remote Development Extension Pack
> (https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack).
I was hoping there is something Text Based,
simple,
that can be used from the Terminal..
for C# .NET
That's why I asked this question..
I guess that micro Editor is the best option that I can find.
sublime-text. Da quando ho scoperto i cursori multipli, non riesco più a farne a meno. Prima che uscisse visual studio code era indiscutibilmente il meglio sul mercato, ora probabilmente ci sono menu plugin, ma mi trovo comunque meglio.
Da command line invece uso micro. Un editor abbastanza avanzato che usa comandi standard usati da ogni altro editor (selezionare testo tenendo premuto shift, copia/taglia/incolla con ctrl+c/x/v, muoversi di parola in parola tenendo premuto ctrl, cursori multipli con ctrl+d, salva/esci con ctrl+s/q...).
It doesn't need to be a web component based real-time collaborative text editor. You could use this micro editor or other editors as base and adding these real-time features. This would be very awesome if i could work with other people on my local machine without a browser involved. Every machine has a network stack and you can easily create a socket connection between multiple machines so nothing prevents you to do this.
​
Micro editor:
This editor is pretty nice. It has really a modern and intuitive interface and is a very good replacement for vim, sublime and vs code. What is missing a good set of plugins for this editor like for vim.
This editor is written in golang.
Homepage:
Details
OS: Manjaro
Kv/KDE/GTK Theme: Sweet
Terminal/Terminal Theme: Hyper Altair
Programs: jay, chkservice, micro, asciiquarium and htop
Browser/Browser Theme: Brave Slate
It's like nano with steroids. I like quick editing to and micro fits all my needs. Make sure you check out all it's plugins as well. There are many useful ones.
https://github.com/zyedidia/micro
I wouldn't call myself a programmer but someone who tinkers with Python or Go templates from time to time.
Personally I prefer Sublime Text for this. The editor is very powerful (especially since there are many plugins) but you can also use it without having to spend hours getting used to it.
Visual Studio Code goes in my opinion in the same direction. What bothers me about the editor is that it is a bit sluggish compared to Sublime Text. Especially when starting.
If you like it more puristic, you can also look at a micro.
Micro would be a good alternative in my opinion. The editor offers more functions than nano and you can use the shortcuts like Ctrl + S as you know them from other programs.
I would recommend micro as an upgrade for beginners after they are suitable with nano, especially if they consider writing code. Still super intuitive and uses common keybinds, but throws a lot more features like themes, multi-cursors, linting & c errors.
> much to the likes of notepad
You mean a literally featureless piece of junk that somehow still manages to use megabytes of RAM? ^(sarcasm off)
Of course it's a matter of preference, but Nano is.. far from great. It's extremely straightforward even for someone who doesn't know a lot about terminals, I'll absolutely give it that, but
It's pretty limited. The keys are awkward. Only a handful of languages are included (highlighting has to be enabled manually too), the built-in help is meager and gnu's info system sucks.
The comparison to notepad is fitting but.. If you're doing text editing on the terminal to begin with, you probably need or want a bit more than, well, notepad.
Of course, if people like using it, absolutely more power to them, in my opinion though, you'll get far more mileage out of learning basic-intermediate Vim. (Or Emacs, if you hate yourself)
And hey, if you like Nano, maybe check out the Micro project.
This might sound dumb coming from a Vim user but Nano feels archaic to me.
I sometimes use Micro if I'm gonna let someone else use my computer, though. I think it's a damn good middle ground between Nano and a good editor.
I'm going to recommend something I've been using for both local development and when I ssh into servers.
Try micro
It's a terminal based editor, like nano, but a single binary with no other dependencies, but more importantly it has mouse support! That's what makes it as great as something like Atom or VS code.
Depends on if you mean 'most' as in started to edit the most files, or logging the most 'time' editing files.
nano - for quick edits, but i know vi well enough i am faster in it.
So which is worth more points of 'mostness' - 100 beginners editing /etc/default/grub taking 2 min each.. , or one dev spending weeks a year in vim or emacs and typing in 100000x code.
nano is recommended for quick edits and simple tasks - it seems mainly because its fairly beginner friendly, however i find way TOO many beginners dont even know that ^O means to use the control key. So even nano could use some improvements in that area.
Just my Opinion. ;) if i had my way i would recommend another editor than nano. fte,mcedit, and it seems i hear about a new one almost every month. I just cant remember the names..
A new one - i just learned about is here - https://github.com/micro-editor/micro-editor.github.io
https://micro-editor.github.io/
'micro-editor' -> No wonder i cant remember any of the names of these things..
Edit: after testing out micro-editor for a bit, i would HIGHLY recommend it over nano.
You can try micro. Its a very light weight text editor that works in a terminal emulator, has auto syntax detection, auto indentation, split screen and also great mouse support among other features. It has the same keyboard shortcuts as any regular text editor.
I'm using micro these days; it has pretty much replaced nano and vim/neovim for me.
Easy to install and use, common shortcuts (ctrl+s, ctrl+c, ctrl+z and so on) & full mouse support work just like in a GUI text editor, splits and tabs, syntax highlighting, unlimited undo/redo, line numbers, Unicode support, softwrap, scriptable and easily configured...