unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 71172@debbugs.gnu.org
Subject: bug#71172: Info: Fixing Case: mention both ways
Date: Fri, 24 May 2024 15:45:13 +0300	[thread overview]
Message-ID: <865xv32xba.fsf@gnu.org> (raw)
In-Reply-To: <87bk4w55xy.3.fsf@jidanni.org> (message from Dan Jacobson on Fri,  24 May 2024 09:55:53 +0800)

tags 71172 notabug wontfix
close 71172
thanks

> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Fri, 24 May 2024 09:55:53 +0800
> 
> On (info "(emacs) Fixing Case") be sure to mention the other way too!:
> < ‘M-- M-l’
> > ‘M-- M-l’ (or 'M-b M-l')
> < ‘M-- M-u’
> > ‘M-- M-u’ (or 'M-b M-u')
> < ‘M-- M-c’
> > ‘M-- M-c’ (or 'M-b M-c')

Why?  The point of M-- is that you do NOT need to go backwards, as
with other editors.  With the above logic, we'd also need to document
that

    C-M-r \b M-c
and
    C-M-r \< M-c
and
    C-M-r \Sw M-c

and gazillion other ways, are _also_ the way of fixing the case of
word before point.  To say nothing of the fact that "M-- M-c"
guarantees that point will remain where it was (so you can safely keep
typing afterwards), whereas all the other methods above do not.  E.g.,
try your M-b method when there's one or more SPC characters between
point and the end of the previous word.

The Emacs manual shows the recommended most convenient and correct
practices.  It doesn't (and should NOT) show all of the possible ways,
let alone complex and inconvenient onces.

So I don't think we should do what you suggest, and I'm therefore
closing this bug.





  reply	other threads:[~2024-05-24 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  1:55 bug#71172: Info: Fixing Case: mention both ways Dan Jacobson
2024-05-24 12:45 ` Eli Zaretskii [this message]
2024-05-24 15:09   ` Dan Jacobson

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=865xv32xba.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71172@debbugs.gnu.org \
    --cc=jidanni@jidanni.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).