all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: 24721@debbugs.gnu.org
Subject: bug#24721: 25.1; Reverse the order of `isearch-message-prefix' prefixes from function advice property
Date: Tue, 18 Oct 2016 23:23:33 +0300	[thread overview]
Message-ID: <87y41ljtiy.fsf@mail.linkov.net> (raw)
In-Reply-To: <39fe0ad4-edb6-4364-b611-146e97097695@default> (Drew Adams's message of "Mon, 17 Oct 2016 15:16:50 -0700 (PDT)")

> When there is multiple advice (from `add-function') of
> `isearch-filter-predicate' that has property `isearch-message-prefix',
> these prefixes are currently shown left to right in the Isearch prompt,
> with the first added being on the left and the last added being on the
> right.
>
> I think this is backwards from what a user expects.  I've reversed the
> order in my own copy, and I think it is more helpful: The first one you
> see is the latest applied.  Entries are added and removed on the left,
> not the right.  The most important such prefix is typically the last
> one applied, and having it on the left makes it more noticeable (IMO).

"Adjectives in English absolutely have to be in this order:
opinion-size-age-shape-colour-origin-material-purpose Noun.
So you can have a lovely little old rectangular green French
silver whittling knife." - an excerpt from a book called
"The Elements of Eloquence" by Mark Forsyth.
http://languagelog.ldc.upenn.edu/nll/?p=27890

Does a similar natural order exist for Isearch, so prefixes
absolutely have to be in the order "overwrapped regexp I-search",
but not "regexp overwrapped I-search"?





  reply	other threads:[~2016-10-18 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-17 22:16 bug#24721: 25.1; Reverse the order of `isearch-message-prefix' prefixes from function advice property Drew Adams
2016-10-18 20:23 ` Juri Linkov [this message]
2016-10-18 20:49   ` Drew Adams
2016-10-18 23:01     ` Clément Pit--Claudel
2016-10-18 23:50       ` Drew Adams
2019-11-11  3:33 ` Stefan Kangas
2020-08-20 16:36   ` Lars Ingebrigtsen

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=87y41ljtiy.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=24721@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.