unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs <help-gnu-emacs@gnu.org>,
	Hongyi Zhao <hongyi.zhao@gmail.com>
Subject: Re: Why use CTL-x CTL-c to quit instead of CTL-x CTL-q?
Date: Wed, 7 Apr 2021 00:00:37 +0300	[thread overview]
Message-ID: <YGzL9YOvRIM71i+Z@protected.localdomain> (raw)
In-Reply-To: <YGzKDvaz9wrFnaa7@protected.localdomain>

* Jean Louis <bugs@gnu.support> [2021-04-06 23:58]:
> * Philip Kaludercic <philipk@posteo.net> [2021-04-06 18:16]:
> > Skip Montanaro <skip.montanaro@gmail.com> writes:
> > 
> > > P.S. Do vi/vim users wonder why its key bindings don't correspond more
> > > strongly to common Windows, Mac or Unix/Linux interface standards? I
> > > rarely need to use vim, but if they changed the quit command (:q or
> > > :q!) I'd be completely lost. How would I ever get back to the shell
> > > prompt? Oh, right, C-z followed by kill(1).
> > 
> > I don't think so, as vi(m) is culturally more about the keys than the
> > software. People use vi(m) for vi(m), while many use Emacs for {org, magit,
> > whatever} and find Emacs to be an obstacle. Or that is at least how I
> 
> I expect on every system to have vi available just because Emacs is
> not available. That is where trouble starts. Sometimes use to edit
> remote files within M-x shell.

Correction: Sometimes I use ed to edit remote files witin M-x shell
especially when there are just few lines to be changed.



  reply	other threads:[~2021-04-06 21:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-06  2:49 Why use CTL-x CTL-c to quit instead of CTL-x CTL-q? Hongyi Zhao
2021-04-06  7:59 ` Jean Louis
2021-04-06 12:34 ` Skip Montanaro
2021-04-06 14:53   ` Skip Montanaro
2021-04-06 15:40     ` Stefan Monnier
2021-04-06 16:17     ` Gregory Heytings
2021-04-06 15:15   ` Philip Kaludercic
2021-04-06 20:52     ` Jean Louis
2021-04-06 21:00       ` Jean Louis [this message]
2021-04-06 23:03         ` Stefan Monnier
2021-04-06 23:16           ` Skip Montanaro
2021-04-07 21:02       ` Francis Belliveau
2021-04-07 23:00         ` Philip Kaludercic

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=YGzL9YOvRIM71i+Z@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    --cc=hongyi.zhao@gmail.com \
    /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).