Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
GUI access to Linux from Windows is also an option
littlebigman -
One other option worth considering is using vncserver (or equivalent) to allow remote GUI logon to your Linux host.
This is actually pretty straightforward. It can work even if your Linux server is otherwise command-line only (even if it doesn't HAVE a desktop by default!), it can work over your ssh port (if that's all you have open across the firewall), and it can even work over a cell phone client.
It's not difficult - and it can be very effective.
Update: After logging on directly to the Linux host, I notice that the Home/End and PageUp/Down do work.
So the issue is getting those to work over a terminal application from Windows.
What terminal application are you using? I notice none of these issues with putty. However putty I find does cause some issues with copy and pasting tabs/indentation, it copies a tab as the equivalent space in spaces, else wise I have no issues myself with putty, there are many GUI text editors as mentioned previously as well.
That seems to be a terminal emulation issue again or, in any case, this pasting is not handled correctly by joe. The problem is that joe doesn't know anything about pasting like this. You paste in a terminal, and the terminal sends the characters to joe. It is simply not well interfaced.
I'll see if I can find more information. Otherwise, Joe is pretty much what I was looking for. Thanks all.
Which version are you using? Mine (2.0.6-4) supports Home, End, Page Up, and Page Down, whether with a terminal emulator or virtual terminal.
It was the terminal emulator that didn't handle those keys properly. I didn't think of trying with Putty to see if that made a difference.
I find Joe much better than vi and pretty what I was looking for. If I need something more 2010ish, I'll just grab files with Samba or WinSCP and update files with a Windows editor.
Out of curiosity, why would I choose Nano over Joe?
I won't get into the argument. I'll just say that vi was invented in 1976, and just like everything else in computers, we made a bit of progress in 35 years. There's no valid reason why newbies should only be told about this arcane tool when they just need to perform some simple editing.
Joe/nano are fine for local editing, and when I need to use Windows tools to edit files, I'll just use Samba/WinSCP.
There's no valid reason why newbies should only be told about this arcane tool when they just need to perform some simple editing.
So not to enter the argument either, but this statement depends on your definition of a 'newbie' as someone who has never used a computer or editor
before would actually pick up vi(m) quicker than almost any other editor as the commands make sense (unless of course you can explain what ctrl-v has to
do with the concept of pasting????).
Distribution: Xubuntu 16.04.1 / Linux Mint 18 XFCE / Linux Mint 18 Mate / Ubuntu Server 16.04.1 / Lubuntu 16.04.1
Posts: 146
Rep:
I was pleasantly surprised when I tried the text editor (mcedit) that comes with the 'midnight commander' file manager. It's a terminal application, and it has menus rather than relying on memorising a vast array of key combinations. If you're using it in a terminal window in a gui desktop you can also use the mouse on the menus.
I don't know if it's what you need, but it's in the repos (as "mc") and it's a small download, so it won't hurt to give it a try.
I won't get into the argument. I'll just say that vi was invented in 1976, and just like everything else in computers, we made a bit of progress in 35 years. There's no valid reason why newbies should only be told about this arcane tool when they just need to perform some simple editing.
Joe/nano are fine for local editing, and when I need to use Windows tools to edit files, I'll just use Samba/WinSCP.
Of course I'd never recommend vi(m) to a newbie. But I don't see what's so bad about it, in fact I sometimes use Vim because to a degree it makes some things easier!
Yes, it has two modes, but the advantage of this is that it frees up all the letters as commands, instead of having to have a few difficult-to-use commands with modifier keys.
For example, in a normal text editor, how would you copy a line and paste it elsewhere?
You'd either use the mouse, or go to the beginning of the line, hold Shift, go to the end of the line using the arrow keys, hit Ctrl+C, move to the end of the line above where you want to paste, press Enter, and press Ctrl+V.
In vi, press "yy", move to the line above where you want to paste, and press "p".
vi has been part of the std install on all versions of *nix (eg Linux/Solaris/HP-UX/AIX/*BSD) for many years. Most commercial servers don't have a gui and you wouldn't be allowed to add your own personal editor unless you're the sysadmin: sometimes not even then.
It's definitely worth knowing the basics.
That's odd - I have no problem viewing file names on remote computers on my network, either in a terminal window or booting into a console. Could it be a character set encoding issue? Each pane in midnight commander can be set to a particular codepage with the 'Encoding' menu item - maybe you've got the wrong codepage set.
Edit: I just noticed that you're running mc inside putty - maybe that's the problem. I run it in a console or a terminal window and ssh to my remote computer inside midnight commander with the 'Shell link' command.
Last edited by genogebot; 08-06-2010 at 07:14 PM.
Reason: added a bit
vi has been part of the std install on all versions of *nix (eg Linux/Solaris/HP-UX/AIX/*BSD) for many years. Most commercial servers don't have a gui and you wouldn't be allowed to add your own personal editor unless you're the sysadmin: sometimes not even then.
It's definitely worth knowing the basics.
I would point out that some functions of vi have lead to some interesting problems with server security before too. I have heard of people being able to create root shells if they are given sudo to vi. I am not aware of anything like that with nano. If you example you wanted people to be able to edit say a certain root file and set-up a sudo entry, Nano suits this use security wise much better then vi which as I have mentioned can be used to create root shells. Vi in my opinion is an arcanic tool too. There should be little need to use control for anything in a text editor thus using it for things like saving, finding, exiting I believe is a superior method all round.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.