unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Fleischer <danflscr@gmail.com>
Cc: 63438@debbugs.gnu.org
Subject: bug#63438: 30.0.50; abbrev mode wrongly capitalizes with mixed capitalized words
Date: Thu, 11 May 2023 16:09:27 +0300	[thread overview]
Message-ID: <83a5yb581k.fsf@gnu.org> (raw)
In-Reply-To: <m2lehvyunn.fsf@gmail.com> (message from Daniel Fleischer on Thu,  11 May 2023 14:28:12 +0300)

> From: Daniel Fleischer <danflscr@gmail.com>
> Date: Thu, 11 May 2023 14:28:12 +0300
> 
> Maybe some context: I think some people, at least me, use abbrev mode to
> properly capitalize words with unique casing, needs not met by regular
> capitalization rules. It means abbrev keys and values sometimes contain
> the same word but with different casing. That's why I want nothing to
> happen when the user writes a word with the right casing, making an
> abbrev expansion unnecessary. 

I agree that your use pattern has a place, and have nothing against
implementing it.  I just don't think we can change to it
unconditionally.  So a new user option is in order, or perhaps a new
value of abbrev-all-caps.





  reply	other threads:[~2023-05-11 13:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  7:10 bug#63438: 30.0.50; abbrev mode wrongly capitalizes with mixed capitalized words Daniel Fleischer
2023-05-11  8:29 ` Eli Zaretskii
2023-05-11  9:00   ` Daniel Fleischer
2023-05-11 10:39     ` Eli Zaretskii
2023-05-11 11:03       ` Daniel Fleischer
2023-05-11 11:28         ` Daniel Fleischer
2023-05-11 13:09           ` Eli Zaretskii [this message]
2023-05-11 13:07         ` Eli Zaretskii
2023-05-11 11:45 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-11 14:18   ` Daniel Fleischer
2023-05-11 15:49     ` Eli Zaretskii

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=83a5yb581k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63438@debbugs.gnu.org \
    --cc=danflscr@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.
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).