unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: completing-read case problem
Date: Mon, 15 Nov 2004 16:35:48 +0100	[thread overview]
Message-ID: <005e01c4cb29$c7b8ef20$0200a8c0@sedrcw11488> (raw)
In-Reply-To: E1CThP2-0003U1-E4@fencepost.gnu.org

Case insensitive please! (I am using ms windows so I am biased by my habits
in this case, but I would believe that a lot of users like case insensitive
handling. Compare with mail-addresses for example, they are since long not
case sensitive.)

- Lennart


----- Original Message ----- 
From: "Richard Stallman" <rms@gnu.org>
To: "Markus Rost" <rost@ias.edu>
Cc: <emacs-devel@gnu.org>
Sent: Monday, November 15, 2004 3:00 PM
Subject: Re: completing-read case problem


>     > It is unreasonable to use a case-sensitive predicate with
>     > completion-ignore-case non-nil.
>
>     But it can be inconvenient if one has to avoid using a case-sensitive
>     predicate.
>
> Not very much.  You just have to downcase the string first.
>
> It would be inconvenient to change Emacs to remove this requirement,
> and I don't have time to even think about it.
>
>     You get a buffer "*Customize Group: Mouse*" showing no members of the
>     (non-empty) group 'mouse -- which is not what is intended.  This
>     problem appears because of completing-read with non-nil
>     completion-ignore-case in customize-group.  completing-read returns
>     "Mouse", which is not the symbol-name of group 'mouse.
>
> There are two ways to fix this:
>
> 1. Decide that case is significant in custom group names,
> and read them case-sensitively.
>
> 2. Decide that case is not significant in custom group names,
> and that they should all be lower case.
>
> Either one seems ok to me.
> What do others think?
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
>

  reply	other threads:[~2004-11-15 15:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200411101929.iAAJThfq007309@haifa.math.ias.edu>
     [not found] ` <E1CTDRk-00077r-Fr@fencepost.gnu.org>
     [not found]   ` <200411140703.iAE73Gd1019094@haifa.math.ias.edu>
2004-11-15 14:00     ` completing-read case problem Richard Stallman
2004-11-15 15:35       ` Lennart Borgman [this message]
2004-11-15 18:49         ` Kevin Rodgers
2004-11-15 20:19           ` Simon Josefsson
2004-11-15 22:06           ` Stefan Monnier
     [not found]     ` <jwvu0rrgm27.fsf-monnier+emacs@gnu.org>
2004-11-15 19:43       ` Markus Rost
2004-11-15 23:07         ` Luc Teirlinck
2004-11-16  2:52           ` Markus Rost
2004-11-21  1:10             ` Richard Stallman
2004-11-21  5:18               ` Markus Rost
2004-11-21 19:02                 ` Luc Teirlinck
2004-11-22 14:07                 ` Richard Stallman
2004-11-16  4:00 Markus Rost

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='005e01c4cb29$c7b8ef20$0200a8c0@sedrcw11488' \
    --to=lennart.borgman.073@student.lu.se \
    --cc=emacs-devel@gnu.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).