public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mwhapples@aim.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: editors
Date: Thu, 01 Nov 2007 23:57:52 +0000	[thread overview]
Message-ID: <1193961472.3403.6.camel@localhost> (raw)
In-Reply-To: <001701c81c9e$fc83b680$6405a8c0@ALBERTLC7SN0ZA>

This thing about windows editors I think is partly why I chose nano as
it was very much along that sort of line and all important key presses
are shown at the bottom of the screen.

Al, you mentioning about starting editors by specifying the file name on
the command line, well you can do that in windows with notepad, go to
run and type in "notepad myfile.txt" and it should load myfile.txt. I
think a number of windows applications support this (possibly the way
that associating the filename works).

Thank you to everyone for the comments, I think I just need to try some.

From
Michael Whapples
On Thu, 2007-11-01 at 10:50 -0500, Albert E. Sten-Clanton wrote:
> > One thing bad about linux editorsYou have to learn them. I can switch from 
> > notepad to TextPad to UltraEdit without having to figure out what keystrokes 
> > to use with each program. Home puts you at the beginning of the line. 
> > Shift+cursordown marks the line. Shift+Del cuts the line. Shift+Ins pastes 
> > it. Control+f,s saves the file.
> > 
> > They all have their own keys for the fancy stuff but you can do the basics 
> > without learning anything about the editor.
> > 
> 
> That's a very fair point indeed.  Sometimes, I forget I'm editing with emacs or vim and hit one of those Windows editor keys.  Derrr!
> 
> One thing I like a lot about using one of the Linux editors is that I can just type its name and the file to bring up.  It reminds me of the old DOS days, when I did the same with WordPerfect.  If there's a way to do that in Windows, I don't know it.  With it, I have to be careful which directory it's looking in for a file, or which directory became the default if I had the temerity to put something in other than "my documents."
> 
> Al
> 
> 
> 



  parent reply	other threads:[~ UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 editors Michael Whapples
 ` editors Chuck Hallenbeck
 ` editors Albert E. Sten-Clanton
   ` editors John Heim
     ` editors Albert E. Sten-Clanton
       ` editors W. Nick Dotson
       ` Michael Whapples [this message]
         ` Editors? Hart Larry
         ` editors Albert E. Sten-Clanton
       ` editors dan Murphy
       ` editors Georgina Joyce
 ` editors John Heim
   ` editors C.M. Brannon
 ` editors Gaijin
 ` editors Tomas Cerha
   ` editors Tyler Spivey
     ` editors Lukas Loehrer
  -- strict thread matches above, loose matches on Subject: below --
 editors Jude DaShiell
 editors Kyrath. (AKA Rob)
 ` editors Kirk Reiser
   ` editors Steve Holmes
 ` editors Alex Snow
 Editors TJ McElroy
 ` Editors Charles Crawford
 ` Editors Alex Snow
 editors Saqib Shaikh
 ` editors frankiec
   ` editors Geoff Shang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1193961472.3403.6.camel@localhost \
    --to=mwhapples@aim.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).