GNU bug report logs - #10542
24.0.92; `Search' field in Customize

Previous Next

Package: emacs;

Reported by: "Drew Adams" <drew.adams <at> oracle.com>

Date: Wed, 18 Jan 2012 17:38:01 UTC

Severity: normal

Found in version 24.0.92

Done: Chong Yidong <cyd <at> gnu.org>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 10542 in the body.
You can then email your comments to 10542 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#10542; Package emacs. (Wed, 18 Jan 2012 17:38:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to "Drew Adams" <drew.adams <at> oracle.com>:
New bug report received and forwarded. Copy sent to bug-gnu-emacs <at> gnu.org. (Wed, 18 Jan 2012 17:38:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: <bug-gnu-emacs <at> gnu.org>
Subject: 24.0.92; `Search' field in Customize
Date: Wed, 18 Jan 2012 09:35:41 -0800
This search field is unlike any search field a user has seen before (at
least this user): whitespace, particularly whitespace at the field
beginning and end, is significant (searched for).
 
While this is no doubt a feature (this is not indexed, full-text search,
after all), it is not obvious to users.
 
At the very least, the :help mouseover text should make this very clear.
 
It might also help to display double quotes around the field - quotes
that are not searched for.  Dunno though - that too could be confusing
if a user searches for a string that starts with a double-quote etc.
 
But something definitely needs to be done.  It is all to easy to click
the mouse somewhere in the middle or at the end of the search field,
type a word/symbol, and click `Search', only to see "No matches".
 
The only way a user is likely to figure out what's happening is to (a)
figure out what function is invoked by the `Search' button and (b) debug
that function, to see what's going on.
 

In GNU Emacs 24.0.92.1 (i386-mingw-nt5.1.2600) of 2012-01-16 on MARVIN
 Windowing system distributor `Microsoft Corp.', version 5.1.2600
 configured using `configure --with-gcc (4.6) --no-opt --cflags
 -ID:/devel/emacs/libs/libXpm-3.5.8/include
 -ID:/devel/emacs/libs/libXpm-3.5.8/src
 -ID:/devel/emacs/libs/libpng-dev_1.4.3-1/include
 -ID:/devel/emacs/libs/zlib-dev_1.2.5-2/include
 -ID:/devel/emacs/libs/giflib-4.1.4-1/include
 -ID:/devel/emacs/libs/jpeg-6b-4/include
 -ID:/devel/emacs/libs/tiff-3.8.2-1/include
 -ID:/devel/emacs/libs/gnutls-3.0.9/include --ldflags
 -LD:/devel/emacs/libs/gnutls-3.0.9/lib'
 





Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#10542; Package emacs. (Fri, 27 Jan 2012 07:38:01 GMT) Full text and rfc822 format available.

Message #8 received at 10542 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> gnu.org>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 10542 <at> debbugs.gnu.org
Subject: Re: bug#10542: 24.0.92; `Search' field in Customize
Date: Fri, 27 Jan 2012 15:36:46 +0800
"Drew Adams" <drew.adams <at> oracle.com> writes:

> This search field is unlike any search field a user has seen before
> (at least this user): whitespace, particularly whitespace at the field
> beginning and end, is significant (searched for).

Please provide a precise step-by-step recipe for reproducing the problem
you have in mind, starting from emacs -Q.




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#10542; Package emacs. (Fri, 27 Jan 2012 16:38:01 GMT) Full text and rfc822 format available.

Message #11 received at 10542 <at> debbugs.gnu.org (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Chong Yidong'" <cyd <at> gnu.org>
Cc: 10542 <at> debbugs.gnu.org
Subject: RE: bug#10542: 24.0.92; `Search' field in Customize
Date: Fri, 27 Jan 2012 08:36:32 -0800
> > This search field is unlike any search field a user has seen before
> > (at least this user): whitespace, particularly whitespace 
> > at the field beginning and end, is significant (searched for).
> 
> Please provide a precise step-by-step recipe for reproducing 
> the problem you have in mind, starting from emacs -Q.

I did that:

> click the mouse somewhere in the middle or at the end of
> the search field, type a word/symbol, and click `Search',
> only to see "No matches".

Since that and the other descriptions I gave of the problem are apparently not
enough, let me try again.

1. emacs -Q

2. M-x customize-option <ANY OPTION YOU LIKE>

3. Click mouse-1 somewhere past the beginning of the Search field.

4. Type `link' or some other substring of an option name.

Resulting message:
"No customizable items matching    link"

This is clearly unusual and unexpected behavior - and unexplained.

As I said, this is clearly a feature - good, not bad.  But it needs to be made
clear to the user.  I proposed some ways in which that could be done.

Most users are not used to whitespace, particularly leading and trailing
whitespace, being significant in a search field, without the use of delimiters
such as quotes.

Additionally, any no-hit message should clearly delimit the search string: wrap
it in `...' or highlight it or something, to set it off from the message text
that refers to it.  The search string is, in fact, being quoted without any
quote indication.







Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#10542; Package emacs. (Sat, 28 Jan 2012 01:17:01 GMT) Full text and rfc822 format available.

Message #14 received at 10542 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> gnu.org>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: 10542 <at> debbugs.gnu.org
Subject: Re: bug#10542: 24.0.92; `Search' field in Customize
Date: Sat, 28 Jan 2012 09:15:46 +0800
"Drew Adams" <drew.adams <at> oracle.com> writes:

> 1. emacs -Q
> 2. M-x customize-option <ANY OPTION YOU LIKE>
> 3. Click mouse-1 somewhere past the beginning of the Search field.
> 4. Type `link' or some other substring of an option name.
>
> Resulting message:
> "No customizable items matching    link"

The missing step, not in this recipe, is that you click on "Search"
button, rather than typing RET.  The "Search" button was bugged.  Fixed
in trunk; thanks.




bug closed, send any further explanations to 10542 <at> debbugs.gnu.org and "Drew Adams" <drew.adams <at> oracle.com> Request was from Chong Yidong <cyd <at> gnu.org> to control <at> debbugs.gnu.org. (Sat, 28 Jan 2012 01:19:02 GMT) Full text and rfc822 format available.

Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#10542; Package emacs. (Sat, 28 Jan 2012 03:08:01 GMT) Full text and rfc822 format available.

Message #19 received at 10542 <at> debbugs.gnu.org (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Chong Yidong'" <cyd <at> gnu.org>
Cc: 10542 <at> debbugs.gnu.org
Subject: RE: bug#10542: 24.0.92; `Search' field in Customize
Date: Fri, 27 Jan 2012 19:06:32 -0800
> > 1. emacs -Q
> > 2. M-x customize-option <ANY OPTION YOU LIKE>
> > 3. Click mouse-1 somewhere past the beginning of the Search field.
> > 4. Type `link' or some other substring of an option name.
> >
> > Resulting message:
> > "No customizable items matching    link"
> 
> The missing step, not in this recipe, is that you click on "Search"
> button, rather than typing RET.  The "Search" button was 
> bugged.  Fixed in trunk; thanks.

Sorry about that.  I did, however, mention the Search button in the original
report.  Thanks for fixing it.





bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 25 Feb 2012 12:24:03 GMT) Full text and rfc822 format available.

This bug report was last modified 12 years and 89 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.