LMAO, I appreciate your objectivity. For a WM user who lives in the terminal, I think vim/neovim makes more sense for you. But as a person with a DE (Plasma), I only use nano to edit config files, but do all my scripting and programming in kate or vscode.
Loved this video and I think you were as sincere as you could be. You were very objective for the most part and I'm proud of you! So go and have some alone time/snuggle time with Vim... 🤣 The look on your face when you said that was the best part of my day. So Thanks... 🤪 LLAP 🖖
Looking back, I think my biggest complaint with nano used to be that it was not always installed on a server I would be asked to look at, and you can't always go ahead and install everything you want on someone else's server. Vim would pretty much always be there, because it was a sysadmin favourite. Now I rarely if ever see a server without nano on it, which makes my life that much easier. I've seen people do amazing things with vim, but it really seems you need to spend time to make it behave exactly the way you want it.
Currently, i use MC with Nano as a means of working on my scripts or libraries. People say you can't open multiple files with nano, but you can and then alt-tab to move from one document to the next. I don't have to create and remember so many keybindings. I have big script files in it and move between between documents very easily. I think it comes down to choosing an application, learn the app, and become an expert. Nano, helps me get things done. Cheers Patrick
To me, Nano is like a plumber working out of his trunk vs Vim, which is like a plumber working out of a work truck. Both can get the job done but the plumber with the work truck will have the right tool for the job.
I use micro for my terminal editor needs and it's good enough. Maybe if you want to compare vim with something more modern I'd go with Kakoune or even Helix.
shift and arrow is a standard gui method of capturing text. For those like us, this is so super fast to delete, cut and paste and move there any where else.
I have been a (neo-)vim user for 10 years and I would never want to miss it. That being said: I would not recommend it to everyone. It takes a lot of learning and tinkering, which is perfectly fine if 90% of your work is getting paid for typing. But if you just sometimes write a couple of lines then I think the overhead is just too big. One for the laughs of the old "How to exit vim"-meme: whenever I am on a computer where EDITOR=nano I am seriously struggling :D (okay over time I am slowly getting it, but I am still "thinking in vim")
Will you do a nixos video soon? It has gotten a lot of atention lately and i was thinking of giving it a try even though i need to waste a lot of time to learn how to write the configuration file😅
That's one thing about being a Vim user, every time I find myself in another editor, like in this TH-cam comment, I find myself using jjjjjjkkkkjj! Or hitting escape 0 to get to the beginning of the line! LOL
thank you man you're the best you're really helpful for me learning linux i just installed i3 wm on my pc although i'm using a unixporn theme though do you think it's not good and i should start and configure my system from scratch
Kind of reminds me of Gimp is not Photoshop. The "dispute", my wife and I have. I've literally grown up using Gimp. My wife has grown up with Photoshop. Now her MBA broke, and she got a Lenovo with elementary OS and Gimp. Yeah, she can't get herself to learn Gimp. It's very frustrating...
@@anon_y_mousse I've tried many photo editing tools, starting with the Amiga 500 and DPaint/Brilliance up to Pixelmator, PS and Gimp and its variants. The UI of PS is made differently. Kind of like the ribbon UI of MS Word etc.. You can either love or hate it. But if you love it, you won't be able to love all other tools, which are made the usual way. This is how I feel. And yes, I've worked with PS for some time, but I always think that things are in the wrong places. I can get used to other apps much easier. But I try and at some time get along with it - even when I don't like it. Kind of like washing the dishes or cleaning up the kids room.
I really don't understand the need for either on a routine basis. I run Linux 100% of the time for over 3 years, and have opened a text editor maybe 5-6 times total in those 42 months and once was to build an rsync script for a chron job and 2nd time was to modify that script. so outside of that maybe 4 times in nearly 4 years. Nano, xed etc all work just fine for me
First of all, another excellent video. Keep them coming. So I'm not a programmer or coder or what ever. I'm just your average everyday user. I am looking for something for writing (books and what not) I don't like open/Libre office since it has so much stuff going on. I do like nano and have used nvim. What is a suggestion for writing prose that is keyboard and terminal based? I have heard that markdown is a good "language" with vim. Does nano have markdown support with live preview?
Markdown is great. I use it everyday. But nano isn't great with it. Neither is vim out of the box. But vim can be extended to be good with it. Nano cannot.
This was amusing. The very first thing I do with a freshly installed Linux distro is to open a terminal and type in "which vim". Nowadays, the second thing I do is to install vim (usually). I was absolutely shocked the first time I installed a Linux distro (Ithink it was Fedora) and typed vim and got the response "command not found". It felt like I had stepped on a step that wasn't there, a momentary panic. And the third thing I do is to remove the nano package, because I have no use whatsoever for it. Which is a little strange, because when I first came across something resembling nano it was way back in the day shortly after I got my very first computer equipped with a 5 1/4 inch floppy drive, a three 3 1/2 inch floppy drive a, whopping 64 meg HD AND....wait for it...a 1200 baud modem. I almost forgot to mention, I also had a whole meg of RAM! As soon as I felt I had the basics of running this machine with DOS 3.0 OS, I signed up for a dial-up internet account and found myself logging onto a Unix server. The editor that came with the Unix email program was something called Pico which is, I believe, the editor that inspired nano. I fumbled around with that for a while until I got used to it. I began browsing Usenet for info on computers and kept reading about different posters favorite text editor vi. I of course had access to that through my dialup and gave it a try and spent about a week fighting with vi and never got to the point where I could consistently use it at all. I'd end up with documents with sentences that abruptly ended mid-line, random blocks of text pasted into it that had nothing to do with what I wanted to say, etc. So I gave up and went back to Pico, wondering how anyone could possibly make use of an atrocity like vi. It was a few years before I finally heard about Linux around 1993 or 4 or thereabouts. I had already graduated to a better machine and was running Windows 3.1 and decided to give Linux a try. I bought a book, The Linux Bible, which came with a cd to install Caldera openLinux and dove in. I ran that for a while and then moved to Slackware, which is when I finally got around to using vim, and I thanked God for the vimtutor. Once I spent a little while with the vimtutor, I was able to use vim with no problem and have been using it ever since and I can't believe the difficulties I had with vi.
Cool, I used Caldera way back when, too. I hopped for a bit using all kinds of distros but settled on Slackware and haven't looked back but one time when I first got this computer I decided to try Debian because it was my first experience with UEFI, but two days later and I'm solidly Slackware. And yep, been using vim since before I made the move to Linux.
@@anon_y_mousse Slackware is my favorite distro to this day and I usually end up back on it after hopping around. Right now though, I'm on Linux Mint, which may seem a bit counter-intuitive, like I'm taking a step backwards, but I am enjoying it so far. I'll probably head back to Slackware after a while though.
It would be cool to see your experience getting back to vim it's hard for me to believe that you spent a month in nano without picking up any muscle memory for certain things maybe talk about anything that you change in your vim workflow now that you tried another editor for a relatively long time what I'm really trying to say is Is vim before nano the same as vim after nano? if that makes any sense
Some version on vi is almost always available on any Unix like system. In 1990 I was in college and the replaced a VAX running VMS with a HP 9000/850 running HPUX and we had to learn vi.
As a developer who uses Neovim for coding, I couldn't switch to nano for a single day. Nano is okay, but if I have a choice, out of all editors - I would only choose nano over... ed. If there's vi, I'd use vi. If there's vim, I'm at home. As a kind of challenge, I switched to Doom Emacs which honestly might stay with me... as my Neovim config was anyway very Doom Emacs-like. I didn't really liked it in GUI, so I just installed emacs-nox and use it in terminal. It's great so far.
@@exnihilonihilfit6316 I cannot put GUI Emacs in tmux. :) I also don't use Emacs daemon for projects, just for regular edits. I have it aliased (also set as $EDITOR). With software projects, I run full instances, otherwise LSP initializes in all project dirs and it's a mess.
Nano will never be good at syntax highlighting. Because you have to manually change the color in the file where the syntax is defined. Also the highlighter only applies a regular expression on each line, it can't read multiple lines.
for your next challenge i would propose an additional challenge. run whatever it is completly vanilla for the first week. sure you can configurate linux/apps like a madman but that doesn't really give the picture your avage user experience if you change nano into using vim bindings aren't you almost just using vim by another name?
Idk how you did it as it sounds absolutely painful. I hate Nano with a passion. I used it a couple times when I first switched to Linux but once I learned even the basic movement commands for vim I used that and now use Neovim as my main editor. The main issue with Nano is the same issue I have with Helix as well, those keybindings are not used anywhere else. Vim and EMacs keybinds can be found on most of if not all other IDEs and even online editors. Nano and Helix have no such widespread keybind adoption.
Gonna go spend some time in insert mode, are ya? Lol I think your experience is a lot like what people experience when they try out a new desktop environment, window manager, or just switch from Windows to Linux. There's a learning curve with anything new, and you're not going to vibe with every workflow. And if you're going to criticize, at least try to criticize from experience.
Used Vim for years when I was learning to code, and liked it just fine. But one downside of it is that if you stop using it for a while, it’s easy to forget all those keyboard shortcuts, and not really worth relearning them. These days I just use an IDE.
@@Little-bird-told-me You’re right man, it’s pretty much universal that you get rusty at things you don’t practice for a while. For me it’s a different question though which tool to use for a specific task, when one of them is clunky, difficult to use, and easy to forget, the other simple, cognitively “low maintenance,” and equally effective. Sometimes I feel that choosing the first option is kind of the theme of this channel though. Nearly everything Matt talks about is like a Linux version of a Ruth Goldberg machine.
@@sonofwotan Lol, well said. Horse for courses. Reminds me of a quote from Oliver Wendell Holmes “For the simplicity on this side of complexity, I wouldn't give you a fig. But for the simplicity on the other side of complexity, for that I would give you anything I have.”
I have no idea why someone in 2023 would waste, yes waste time using Vim at all, it was made for a specific machine's layout in mind at the time of its conception and is the reason why it has all weird keybindings just to do things, meaning, a new user is left perplexed for ages as to what to do because literally also a person made it to work on something very specific, very specifically. Nano is decent because it's intuitive to use because it was made to be used on a computer and intuitive controls. That's my two cents.
I know I should learn vim, but I'm too lazy, and nano just works. The few seconds I could save every time I edit a file with vim just have not been worth the steep learning curve.
I was trying to think of a joke but it just didn't "sound" right in text. However, it seems as though you agree with me that config files shouldn't be a programming language, or at the very least you're partly there. Maybe this is a weird opinion, especially given that I'm a programmer, but I feel like config files should just be straight lists of options to set with at most a depth of one if you need treeing. I've always kind of liked the standard Windows INI files, and TOML seems like a decent extension. Again, probably a weird opinion given how long I've been using Linux for, but there it is.
I think your first mistake is making it look just like VIM, if there was some visual differences more obvious then you might do less VIM commands in nano. I love nano but vim is cool just never learned it.
Vim is one of the pieces of software that I think is the most hostile to newcomers. The way it works is bizarre, the keys are bizarre and unintuitive, it's just awful. I would use some combination of cat and sed before using vim and be considerably more effective. But it does seem to be one of those things that is very efficient and powerful after you spend 5 years twisting your brain to fit the program. Sway is pretty much in that same category for me.
_Nano is quaint anachronism personified_ . _Micro_ is much a better platform than nano. *Vim* is at a different level and comparing it to *Nano* is unfair. You wouldn't expect a cat to wake up one day and to speak to you in english, will ya ?
@@TheLinuxCast oh dang, the man himself replied :o did you ever manage to work out your issues with the logs? I made a comment that I later edited on that video, suggesting journald for a gui frontend for syslog/journalctl, if "journalctl -p warning" didn't throw up anything useful in terminal
@@TheLinuxCast fairs, congrats on figuring it out at least! I feel lost without Windows Event Viewer for that kind of stuff (been using Windows since I was like 10, sue me lol), but with journalctl -p warning and/or journald that shouldn't be a problem anymore. but errors like that is what's pushing me towards going either Nix OS or immutable + flatpaks (waiting on Vanilla OS 2 Orchid for that one so I can compare it to fedora/arch, and looking forward to your review if you do it) to avoid dependency conflicts etc. as much as possible. anyway ramble over, good luck with your future endeavours
It is silly that you stooped so low as to use Nano, after using ViM. All it is doing for you is causing you to unlearn ViM habits and this is a huge negative, in terms of functionality that you perform automatically, without even thinking about it. Just my 2 cents on this experiment.
I don't understand the point of this video. Nano should only be used for one thing: change a setting in the system, save the file, exit. Nothing more. I've been using Linux since 1999, and I have not learned to use either emacs, nor vi/vim. I only learned 3-4 shortcuts for nano, because I only use it for one thing: change a config file. That's it. If I want to write anything else, be it programming or a document, I use a GUI app. If the distro doesn't have good GUI tools for that, I simply don't use that distro. And if a distro comes without nano, but requires editing files during installation, again, I simply doesn't use that distro. A distro that doesn't include nano, is not serious towards more desktop-oriented users like me, and as such, I want nothing to do with it. So from my own point of view, nano should not be compared to vi/vim/emacs. It's just a simple editor to get around config files. Nothing more. I don't give it credit for anything more. And yet, it's indispensable for what it does for me.
A bigger challenge would be to use vi for a month.
This fúckér really took the first letter of my name and thinks he'll get away with it
@@CrazyMineCuber I prefer ne; nice editor.
You noobs havent memorized a single codepage well enough just to use a hex editor for typing?
@@CrazyMineCuber butterflies is the real challenge.
( ;D xkcd, "real programmers" )
@@CrazyMineCuberlmao the current century/year card always makes me chuckle
LMAO, I appreciate your objectivity. For a WM user who lives in the terminal, I think vim/neovim makes more sense for you. But as a person with a DE (Plasma), I only use nano to edit config files, but do all my scripting and programming in kate or vscode.
Loved this video and I think you were as sincere as you could be. You were very objective for the most part and I'm proud of you! So go and have some alone time/snuggle time with Vim... 🤣
The look on your face when you said that was the best part of my day. So Thanks... 🤪
LLAP 🖖
Looking back, I think my biggest complaint with nano used to be that it was not always installed on a server I would be asked to look at, and you can't always go ahead and install everything you want on someone else's server. Vim would pretty much always be there, because it was a sysadmin favourite.
Now I rarely if ever see a server without nano on it, which makes my life that much easier. I've seen people do amazing things with vim, but it really seems you need to spend time to make it behave exactly the way you want it.
If you are hopping on servers, learning base vi/vim is far more important than worrying about plugins etc.
Currently, i use MC with Nano as a means of working on my scripts or libraries. People say you can't open multiple files with nano, but you can and then alt-tab to move from one document to the next. I don't have to create and remember so many keybindings. I have big script files in it and move between between documents very easily.
I think it comes down to choosing an application, learn the app, and become an expert. Nano, helps me get things done.
Cheers
Patrick
To me, Nano is like a plumber working out of his trunk vs Vim, which is like a plumber working out of a work truck. Both can get the job done but the plumber with the work truck will have the right tool for the job.
I started with vim but settled on nano. I'm no coder or writer, and never had a need for all of vim's features.
I use micro for my terminal editor needs and it's good enough. Maybe if you want to compare vim with something more modern I'd go with Kakoune or even Helix.
Micro is boss
Micro makes Nano look complicated.
shift and arrow is a standard gui method of capturing text. For those like us, this is so super fast to delete, cut and paste and move there any where else.
"Nano it is not Vim!"
- Cast, The Linux 2023
I have been a (neo-)vim user for 10 years and I would never want to miss it. That being said: I would not recommend it to everyone. It takes a lot of learning and tinkering, which is perfectly fine if 90% of your work is getting paid for typing. But if you just sometimes write a couple of lines then I think the overhead is just too big.
One for the laughs of the old "How to exit vim"-meme: whenever I am on a computer where EDITOR=nano I am seriously struggling :D (okay over time I am slowly getting it, but I am still "thinking in vim")
Will you do a nixos video soon? It has gotten a lot of atention lately and i was thinking of giving it a try even though i need to waste a lot of time to learn how to write the configuration file😅
That's one thing about being a Vim user, every time I find myself in another editor, like in this TH-cam comment, I find myself using jjjjjjkkkkjj! Or hitting escape 0 to get to the beginning of the line! LOL
:wq
thank you man you're the best you're really helpful for me learning linux i just installed i3 wm on my pc although i'm using a unixporn theme though do you think it's not good and i should start and configure my system from scratch
I started with someone else's config too. It's a good way to learn
@@TheLinuxCast oh nice it is a great experience to use tiling window manager thanks again
Kind of reminds me of Gimp is not Photoshop. The "dispute", my wife and I have. I've literally grown up using Gimp. My wife has grown up with Photoshop. Now her MBA broke, and she got a Lenovo with elementary OS and Gimp. Yeah, she can't get herself to learn Gimp. It's very frustrating...
Have you ever tried to use Photoshop and was it as difficult for you to use as GIMP was for your wife?
@@anon_y_mousse I've tried many photo editing tools, starting with the Amiga 500 and DPaint/Brilliance up to Pixelmator, PS and Gimp and its variants. The UI of PS is made differently. Kind of like the ribbon UI of MS Word etc.. You can either love or hate it. But if you love it, you won't be able to love all other tools, which are made the usual way. This is how I feel.
And yes, I've worked with PS for some time, but I always think that things are in the wrong places. I can get used to other apps much easier.
But I try and at some time get along with it - even when I don't like it. Kind of like washing the dishes or cleaning up the kids room.
I really don't understand the need for either on a routine basis. I run Linux 100% of the time for over 3 years, and have opened a text editor maybe 5-6 times total in those 42 months and once was to build an rsync script for a chron job and 2nd time was to modify that script. so outside of that maybe 4 times in nearly 4 years. Nano, xed etc all work just fine for me
Well, when you are a writer you get a tool to write. These 2 are easier to use than a Word Processor
Challenge: hold yourself to the no challenges thing for 3 months. Do what you enjoy. That's when you're at your best. Keep up the great work!
The sacrifice 🤣
Been using vi/vim/nvim since 1995, vim plugins in every IDE I use.
You survived!
First of all, another excellent video. Keep them coming.
So I'm not a programmer or coder or what ever. I'm just your average everyday user. I am looking for something for writing (books and what not) I don't like open/Libre office since it has so much stuff going on. I do like nano and have used nvim. What is a suggestion for writing prose that is keyboard and terminal based? I have heard that markdown is a good "language" with vim. Does nano have markdown support with live preview?
Markdown is great. I use it everyday. But nano isn't great with it. Neither is vim out of the box. But vim can be extended to be good with it. Nano cannot.
This was amusing. The very first thing I do with a freshly installed Linux distro is to open a terminal and type in "which vim". Nowadays, the second thing I do is to install vim (usually). I was absolutely shocked the first time I installed a Linux distro (Ithink it was Fedora) and typed vim and got the response "command not found". It felt like I had stepped on a step that wasn't there, a momentary panic. And the third thing I do is to remove the nano package, because I have no use whatsoever for it. Which is a little strange, because when I first came across something resembling nano it was way back in the day shortly after I got my very first computer equipped with a 5 1/4 inch floppy drive, a three 3 1/2 inch floppy drive a, whopping 64 meg HD AND....wait for it...a 1200 baud modem. I almost forgot to mention, I also had a whole meg of RAM! As soon as I felt I had the basics of running this machine with DOS 3.0 OS, I signed up for a dial-up internet account and found myself logging onto a Unix server. The editor that came with the Unix email program was something called Pico which is, I believe, the editor that inspired nano. I fumbled around with that for a while until I got used to it. I began browsing Usenet for info on computers and kept reading about different posters favorite text editor vi. I of course had access to that through my dialup and gave it a try and spent about a week fighting with vi and never got to the point where I could consistently use it at all. I'd end up with documents with sentences that abruptly ended mid-line, random blocks of text pasted into it that had nothing to do with what I wanted to say, etc. So I gave up and went back to Pico, wondering how anyone could possibly make use of an atrocity like vi. It was a few years before I finally heard about Linux around 1993 or 4 or thereabouts. I had already graduated to a better machine and was running Windows 3.1 and decided to give Linux a try. I bought a book, The Linux Bible, which came with a cd to install Caldera openLinux and dove in. I ran that for a while and then moved to Slackware, which is when I finally got around to using vim, and I thanked God for the vimtutor. Once I spent a little while with the vimtutor, I was able to use vim with no problem and have been using it ever since and I can't believe the difficulties I had with vi.
Cool, I used Caldera way back when, too. I hopped for a bit using all kinds of distros but settled on Slackware and haven't looked back but one time when I first got this computer I decided to try Debian because it was my first experience with UEFI, but two days later and I'm solidly Slackware. And yep, been using vim since before I made the move to Linux.
@@anon_y_mousse Slackware is my favorite distro to this day and I usually end up back on it after hopping around. Right now though, I'm on Linux Mint, which may seem a bit counter-intuitive, like I'm taking a step backwards, but I am enjoying it so far. I'll probably head back to Slackware after a while though.
It would be cool to see your experience getting back to vim
it's hard for me to believe that you spent a month in nano without picking up any muscle memory for certain things
maybe talk about anything that you change in your vim workflow now that you tried another editor for a relatively long time
what I'm really trying to say is
Is vim before nano the same as vim after nano?
if that makes any sense
Ctrl s to save. It's bit me many times today. Lol
@@TheLinuxCast You can just rebind it and double win.
I guess it's easier than using 'cat' or 'sed' for an editor. So, it's got that going for it.
Matt for a Vim user to try Nano like your self, when you need a text editor for your work is OUTSTANDING great try. GVM
Some version on vi is almost always available on any Unix like system. In 1990 I was in college and the replaced a VAX running VMS with a HP 9000/850 running HPUX and we had to learn vi.
As a developer who uses Neovim for coding, I couldn't switch to nano for a single day. Nano is okay, but if I have a choice, out of all editors - I would only choose nano over... ed. If there's vi, I'd use vi. If there's vim, I'm at home.
As a kind of challenge, I switched to Doom Emacs which honestly might stay with me... as my Neovim config was anyway very Doom Emacs-like. I didn't really liked it in GUI, so I just installed emacs-nox and use it in terminal. It's great so far.
@@exnihilonihilfit6316 I cannot put GUI Emacs in tmux. :) I also don't use Emacs daemon for projects, just for regular edits. I have it aliased (also set as $EDITOR). With software projects, I run full instances, otherwise LSP initializes in all project dirs and it's a mess.
have you tried using lunarvim?
Thanks sharing. How about neovim?
Nano will never be good at syntax highlighting. Because you have to manually change the color in the file where the syntax is defined. Also the highlighter only applies a regular expression on each line, it can't read multiple lines.
for your next challenge i would propose an additional challenge. run whatever it is completly vanilla for the first week.
sure you can configurate linux/apps like a madman but that doesn't really give the picture your avage user experience
if you change nano into using vim bindings aren't you almost just using vim by another name?
Idk how you did it as it sounds absolutely painful. I hate Nano with a passion. I used it a couple times when I first switched to Linux but once I learned even the basic movement commands for vim I used that and now use Neovim as my main editor. The main issue with Nano is the same issue I have with Helix as well, those keybindings are not used anywhere else. Vim and EMacs keybinds can be found on most of if not all other IDEs and even online editors. Nano and Helix have no such widespread keybind adoption.
Gonna go spend some time in insert mode, are ya? Lol
I think your experience is a lot like what people experience when they try out a new desktop environment, window manager, or just switch from Windows to Linux. There's a learning curve with anything new, and you're not going to vibe with every workflow. And if you're going to criticize, at least try to criticize from experience.
Used Vim for years when I was learning to code, and liked it just fine. But one downside of it is that if you stop using it for a while, it’s easy to forget all those keyboard shortcuts, and not really worth relearning them. These days I just use an IDE.
_Guess, that's true with everything in life. Trying programming after a break._
@@Little-bird-told-me You’re right man, it’s pretty much universal that you get rusty at things you don’t practice for a while. For me it’s a different question though which tool to use for a specific task, when one of them is clunky, difficult to use, and easy to forget, the other simple, cognitively “low maintenance,” and equally effective. Sometimes I feel that choosing the first option is kind of the theme of this channel though. Nearly everything Matt talks about is like a Linux version of a Ruth Goldberg machine.
@@sonofwotan Lol, well said. Horse for courses. Reminds me of a quote from Oliver Wendell Holmes “For the simplicity on this side of complexity, I wouldn't give you a fig. But for the simplicity on the other side of complexity, for that I would give you anything I have.”
Alternative title: Vim nerd tries to get along with GNU Nano (IMPOSSIBLE)
You have two Discord instances running
Yes, I was aware.
Can you do a month with Micro ? if not, thats okay. Just curious what you think about Micro.
I have a video on it
@@TheLinuxCast > Oops, didn't see it ! thank you Matt !
Next challenge, use as many snaps as possible for a month lol.
Nope. Absolutely not 🚫
Id rather try to package everything as a flatpak
I have no idea why someone in 2023 would waste, yes waste time using Vim at all, it was made for a specific machine's layout in mind at the time of its conception and is the reason why it has all weird keybindings just to do things, meaning, a new user is left perplexed for ages as to what to do because literally also a person made it to work on something very specific, very specifically.
Nano is decent because it's intuitive to use because it was made to be used on a computer and intuitive controls.
That's my two cents.
Obviously you have no idea what Vim is and how powerful it is
@@OmarIskandarone I am not denying its strengths just because it's not as practical for basic things.
I started with nano how using micro will try vim but that's a long way off.
I just made a config for nano, while micro is great i was lazy to install it
I'm with you though. Why would anyone ever make an editor where j doesn't go down a line? 🙂
It's not Nano's fault that you got so much muscle memory from Vim.
I know I should learn vim, but I'm too lazy, and nano just works. The few seconds I could save every time I edit a file with vim just have not been worth the steep learning curve.
I was trying to think of a joke but it just didn't "sound" right in text. However, it seems as though you agree with me that config files shouldn't be a programming language, or at the very least you're partly there. Maybe this is a weird opinion, especially given that I'm a programmer, but I feel like config files should just be straight lists of options to set with at most a depth of one if you need treeing. I've always kind of liked the standard Windows INI files, and TOML seems like a decent extension. Again, probably a weird opinion given how long I've been using Linux for, but there it is.
I think your first mistake is making it look just like VIM, if there was some visual differences more obvious then you might do less VIM commands in nano. I love nano but vim is cool just never learned it.
Wait a minute...are you trying to say that nano is not vim? 🤯 Haha
Indeed
Don't sleep on Helix.
I have always used and loved joe. Magnificent, easy to use macros, short learning curve. Vim is for masochists IMHO. 😅
Nah. Once you do Vim you can't go back. Everything will feel like a downgrade.
I think a real masochists would use ed.
Vim is one of the pieces of software that I think is the most hostile to newcomers. The way it works is bizarre, the keys are bizarre and unintuitive, it's just awful. I would use some combination of cat and sed before using vim and be considerably more effective. But it does seem to be one of those things that is very efficient and powerful after you spend 5 years twisting your brain to fit the program.
Sway is pretty much in that same category for me.
Nano is good when you don't get your hands on config files like me 😅
guarantee if you use nano and test vim for a whole two week you are not going back
I've been using vim for years
@@TheLinuxCast yea I know I'm talking about nano users
In all fairness, Ctrl+x being both how you cut text and how you exit nano is a big, big oversight
Cut in nano is ctrl k
Me who used both based on mood
Just go for vscode or helix. You don't need to go after only the painful ones
Vim is awesome 😎
I like kate and the more I use libre office i think that it's just the worst full featured editor.
You should have instead tried helix.
Imo it's what vim should've been.
pico is easier to type than nano…that’s my only preference:)
micro >>>>>>>>>>>>>>>
BBEdit doesen't suck
Try to live in rocky for a week I challenge you
Hell no, oh hell no
_Nano is quaint anachronism personified_ . _Micro_ is much a better platform than nano. *Vim* is at a different level and comparing it to *Nano* is unfair. You wouldn't expect a cat to wake up one day and to speak to you in english, will ya ?
I challenge you to not do a challenge!
Challenge Accepted
@@TheLinuxCast oh dang, the man himself replied :o did you ever manage to work out your issues with the logs? I made a comment that I later edited on that video, suggesting journald for a gui frontend for syslog/journalctl, if "journalctl -p warning" didn't throw up anything useful in terminal
@@glebglub I know what's causing it. Not how to fix it yet. But the bug has been reported
@@TheLinuxCast fairs, congrats on figuring it out at least! I feel lost without Windows Event Viewer for that kind of stuff (been using Windows since I was like 10, sue me lol), but with journalctl -p warning and/or journald that shouldn't be a problem anymore. but errors like that is what's pushing me towards going either Nix OS or immutable + flatpaks (waiting on Vanilla OS 2 Orchid for that one so I can compare it to fedora/arch, and looking forward to your review if you do it) to avoid dependency conflicts etc. as much as possible.
anyway ramble over, good luck with your future endeavours
It is silly that you stooped so low as to use Nano, after using ViM. All it is doing for you is causing you to unlearn ViM habits and this is a huge negative, in terms of functionality that you perform automatically, without even thinking about it. Just my 2 cents on this experiment.
Very uninformative half an hour. Nano has definitely a substantially lower acquaintance threshold. Its color scheme is documented.
You talk too much than acting or showing what you are talking about.
I don't understand the point of this video. Nano should only be used for one thing: change a setting in the system, save the file, exit. Nothing more. I've been using Linux since 1999, and I have not learned to use either emacs, nor vi/vim. I only learned 3-4 shortcuts for nano, because I only use it for one thing: change a config file. That's it. If I want to write anything else, be it programming or a document, I use a GUI app. If the distro doesn't have good GUI tools for that, I simply don't use that distro. And if a distro comes without nano, but requires editing files during installation, again, I simply doesn't use that distro. A distro that doesn't include nano, is not serious towards more desktop-oriented users like me, and as such, I want nothing to do with it. So from my own point of view, nano should not be compared to vi/vim/emacs. It's just a simple editor to get around config files. Nothing more. I don't give it credit for anything more. And yet, it's indispensable for what it does for me.
Some people use nano for more. Just because you've been using something forever doesn't mean everyone uses the same thing.
I just use LibreOffice Writer.