unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-pretest-bug@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: completing-read case problem
Date: Mon, 15 Nov 2004 17:07:29 -0600 (CST)	[thread overview]
Message-ID: <200411152307.iAFN7TB06089@raven.dms.auburn.edu> (raw)
In-Reply-To: <200411151943.iAFJhYL6009036@haifa.math.ias.edu> (message from Markus Rost on Mon, 15 Nov 2004 14:43:34 -0500)

Markus Rost wrote (in response to Stefan Monnier):

   > > With input "ABC" it returns "ABC", which I think is incorrect -- at
   > > least it may lead to surprises in programs which assume that the
   > > output of completing-read is always an exact member of TABLE,
   > > restricted by PREDICATE.
   > 
   > Yes, we pretty much agreed to that in an earlier discussion this year.
   > Nobody has stepped forward with a patch for it, tho.
   > 

   I guess you mean the discussion started with
   <URL:http://lists.gnu.org/archive/html/emacs-devel/2003-12/msg00459.html>.

I do not know whether that was what Stefan was referring to, but if I
remember correctly, that thread was concerned with certain bugs
concerning case that occurred for hash tables and obarrays, but not
for lists.

The bug there was that completion-ignore-case was ignored for hash
tables and obarrays.  It concerned finding a match when there was
none and not finding one when there was one.  I did install a fix for
that problem.

I did not follow this thread in detail, but I believe that what you
are complaining about is the _case of the returned result_ if there is
a match and the search is case insensitive.  I do not believe that
there still are problems with finding out correctly whether or not
there is a match.  (Unless I misunderstood.)

Sincerely,

Luc.

  reply	other threads:[~2004-11-15 23:07 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
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 [this message]
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=200411152307.iAFN7TB06089@raven.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).