From: Glenn Morris <rgm@gnu.org>
To: herring@lanl.gov
Cc: "Andreas Röhler" <andreas.roehler@online.de>, emacs-devel@gnu.org
Subject: Re: Abbrev should preserve case
Date: Thu, 21 Jun 2007 03:00:25 -0400 [thread overview]
Message-ID: <x9y7id4ws6.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <29696.128.165.0.81.1182397659.squirrel@webmail.lanl.gov> (Davis Herring's message of "Wed, 20 Jun 2007 20:47:39 -0700 (PDT)")
"Davis Herring" wrote:
> Surely you mean do a case-sensitive search first and then
> insensitive? Obviously the sensitive one can't work if the
> insensitive one fails. Then you go on to say that "FOO" could only
> be -different- if there is nothing than which to be different;
> instead we want to say "`FOO' can only expand as upcased `foo' if
> `FOO' is not its own abbrev", right?
It doesn't really matter what I meant if Stefan's already invented
this particular wheel.
I was using "case-insensitive" in a confusing (ie wrong) way. What I
meant was:
You have a word (FOO) in the buffer. Downcase it, and compare with the
abbrev table. If you find a match (foo), return the expansion, with
the existing abbrev case-fiddling applied. This is the same as happens
as present.
If you don't find a match (and if the word is not all lower-case), go
on to try the un-downcased version (FOO) against the abbrev table. If
you find a match, return the expansion.
This would enable existing abbrevs to function as they always have,
and allow for new mixed-case abbrevs so long as they don't conflict
with old-style abbrevs.
If you do it the other way round, you would break backwards
compatibility.
next prev parent reply other threads:[~2007-06-21 7:00 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 17:48 Abbrev should preserve case Andreas Röhler
2007-06-20 22:18 ` Glenn Morris
2007-06-21 3:47 ` Davis Herring
2007-06-21 4:14 ` Stefan Monnier
2007-06-21 7:10 ` Andreas Röhler
2007-06-21 8:01 ` Stefan Monnier
2007-06-21 9:00 ` Andreas Röhler
2007-06-21 7:00 ` Glenn Morris [this message]
2007-06-21 17:32 ` Richard Stallman
2007-06-21 19:02 ` Stefan Monnier
2007-06-22 16:25 ` Richard Stallman
2007-06-22 17:51 ` Stefan Monnier
2007-06-22 21:53 ` Richard Stallman
2007-10-10 21:14 ` Abbrev tables in elisp with some extra stuff (was: Abbrev should preserve case) Stefan Monnier
2007-10-11 19:57 ` Andreas Röhler
2007-10-12 15:59 ` Richard Stallman
2007-10-12 21:26 ` Abbrev tables in elisp with some extra stuff Stefan Monnier
2007-10-13 6:41 ` Richard Stallman
2007-10-14 17:45 ` Andreas Röhler
2007-10-15 16:04 ` Richard Stallman
2007-10-15 18:04 ` Andreas Röhler
2007-10-16 4:10 ` Richard Stallman
2007-10-16 20:26 ` Stefan Monnier
2007-10-17 5:03 ` Richard Stallman
2007-10-17 14:10 ` Richard Stallman
2007-10-17 20:48 ` Richard Stallman
2007-10-24 2:21 ` Stefan Monnier
2007-10-25 2:10 ` Richard Stallman
2007-10-26 5:44 ` Testing new abbrev tables in elisp Stefan Monnier
2007-10-26 19:13 ` Andreas Röhler
2007-10-26 21:38 ` Stefan Monnier
2007-10-28 14:13 ` Andreas Röhler
2007-10-28 21:03 ` Stefan Monnier
2007-10-30 15:10 ` Andreas Röhler
2007-10-31 7:47 ` Richard Stallman
2007-11-03 20:29 ` Stephen J. Turnbull
2007-11-04 0:11 ` Richard Stallman
2007-11-04 2:42 ` Stephen J. Turnbull
2007-11-04 21:06 ` Andreas Röhler
2007-11-05 8:47 ` Richard Stallman
2007-10-31 16:09 ` Juri Linkov
2007-10-31 17:44 ` Stefan Monnier
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=x9y7id4ws6.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=andreas.roehler@online.de \
--cc=emacs-devel@gnu.org \
--cc=herring@lanl.gov \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.