all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 9432@debbugs.gnu.org
Subject: bug#9432: 24.0.50; doc string of `next-error-highlight'
Date: Mon, 5 Sep 2011 06:55:12 -0700	[thread overview]
Message-ID: <B855417113FA4B6ABE76480E8175E998@us.oracle.com> (raw)
In-Reply-To: <874o0rwf5p.fsf@mail.jurta.org>

> > The doc string should say that the fringe indication is 
> > moved when some other locus replaces it - just as it says
> > this for a value of `t'.
> 
> Is this better?
> 
> +If `fringe-arrow', indicate the locus by the fringe arrow
> +indefinitely until some other locus replaces it."

Yes, thanks.

(And FWIW I still think we should also have a value `until-move' that does the
same thing - stay until some other locus replaces it - but using highlighting
instead of fringe.  I've been using that for years myself, so I obviously prefer
it - I generally don't show the fringe.)






  reply	other threads:[~2011-09-05 13:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-04  1:16 bug#9432: 24.0.50; doc string of `next-error-highlight' Drew Adams
2011-09-05  8:45 ` Juri Linkov
2011-09-05 13:55   ` Drew Adams [this message]
2011-09-06  9:42     ` Juri Linkov
2011-09-06 13:47       ` Drew Adams
2011-09-07 11:48         ` Juri Linkov
2011-09-07 14:05           ` Drew Adams
2011-09-07 23:52             ` Juri Linkov
2011-09-08  1:42               ` Stefan Monnier
2011-09-08 13:17                 ` Drew Adams
2011-09-08 20:09                 ` Juri Linkov
2011-09-09  2:17                   ` Stefan Monnier
2016-04-28 11:20                     ` Lars Ingebrigtsen
2011-09-08 13:15               ` Drew Adams
2011-09-07 13:34         ` Stefan Monnier
2019-06-13 11:26 ` Stefan Kangas
2019-06-13 12:44   ` Eli Zaretskii
2019-06-13 13:07     ` Stefan Kangas

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=B855417113FA4B6ABE76480E8175E998@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=9432@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 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.