unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 9918@debbugs.gnu.org
Subject: bug#9918: 24.0.90; lazy-highlighting in Info mode
Date: Thu, 3 Nov 2011 20:24:13 +0100	[thread overview]
Message-ID: <CAH8Pv0gA38VLUJuExL3U5xz3Ld1ubzEee8kqwV3i43yOAHaDiw@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0jN_Grz60VGBdfQn2ZJ5Fq15qAms4VGTWS72HwXNoRnew@mail.gmail.com>

> I think that these two informative messages ("initial node", "end of
> the manual") fall into the same category as the messages that are
> added to the Isearch prompt ("Failing", "Wrapped", "Overwrapped",
> "Failing overwrapped", ...).  So I propose to present all these
> "Isearch flags" to the user using a common pattern. For example:
> * "Isearch:"
> * "Isearch [failing]:"
> * "Isearch [overwrapped]:"
> * "Isearch [failing, overwrapped]:"
> * "Isearch [failing, initial node]:"
>
> It would add consistency to the Isearch visual feedback.

... however a downside of this approach is that the position of the
search string varies each time a flag is added to or removed from the
prompt.  I really dislike that, and btw, this effect occurs currently
("I-search: foo" -> "Failing I-search: foo" ...).

So, I rather would write the flags at the right side of the search
string, like the error messages are showed right now:
* "Isearch: foo"
* "Isearch: foo [failing]"
* "Isearch: foo [failing, overwrapped]"
* "Isearch: foo [failing, initial node]"
...

This approach raises a question: how to show the _error_ flags to make
them distinguishable from the _informative_ flags?

One possibility is to show all the flags the same way.  After all, the
fact that the errors deactivate the Isearch should be enough for the
user to know what's going on, I think.

-- 
Dani Moncayo





  reply	other threads:[~2011-11-03 19:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 14:46 bug#9918: 24.0.90; lazy-highlighting in Info mode Dani Moncayo
2011-10-31 20:43 ` Eli Zaretskii
2011-10-31 21:00   ` Drew Adams
2011-10-31 21:08   ` Dani Moncayo
2011-10-31 21:13     ` Drew Adams
2011-10-31 21:30       ` Dani Moncayo
2011-10-31 21:39         ` Drew Adams
2011-10-31 23:15 ` Juri Linkov
2011-11-01  9:39   ` Dani Moncayo
2011-11-01 10:21     ` Dani Moncayo
2011-11-01 23:07     ` Juri Linkov
2011-11-02  7:54       ` Dani Moncayo
2011-11-03  9:07         ` Juri Linkov
2011-11-03  9:44           ` Dani Moncayo
2011-11-03 19:24             ` Dani Moncayo [this message]
2011-11-03 19:56               ` Juri Linkov
2011-11-03 20:43                 ` Dani Moncayo
2011-11-03 21:11                   ` Juri Linkov
2011-12-01  7:45                     ` Juri Linkov
2011-11-19 21:04                 ` Juri Linkov

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=CAH8Pv0gA38VLUJuExL3U5xz3Ld1ubzEee8kqwV3i43yOAHaDiw@mail.gmail.com \
    --to=dmoncayo@gmail.com \
    --cc=9918@debbugs.gnu.org \
    --cc=juri@jurta.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).