unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 13552@debbugs.gnu.org
Subject: bug#13552: 24.3.50; glitch in Info formatting for cross reference
Date: Sat, 26 Jan 2013 07:45:22 -0800	[thread overview]
Message-ID: <A86C945B4EE746A1908A83D297C9DE78@us.oracle.com> (raw)
In-Reply-To: <83pq0sjjny.fsf@gnu.org>

> > (elisp) `The Mark' shows this to the user:
> >  
> >      If `shift-select-mode' is non-`nil' and the current command was
> >      invoked via shift translation (see shift-translation
> >      .), this function sets the mark and temporarily
> >      activates the region, unless the region was already temporarily
> >      activated in this way.  Otherwise, if the region has 
> >      been activated
> >      temporarily, it deactivates the mark and restores the variable
> >      `transient-mark-mode' to its earlier value.
> >  
> > The problem is the visual newline between `shift-translation' and
> > `.'.  This is a no-no.
> 
> That's because what info.el does is put an invisible text property on
> a part of the cross-reference that is deemed "unimportant".  You can
> turn off this behavior by customizing Info-hide-node-references.

Yes, I know.  That's the cause underlying the bug: incomplete implementation of
the prettying-up/hiding.

Pointing to the user option is a red herring wrt the bug, amounting to "if it
hurts don't do that".  But yes, workarounds for bugs, including turning off
bugged features are good to have.

I remind you of the proposal (with patch) to optionally let users highlight
`...' and "..." in Info.  It was rejected because there are a (very) few places
where a node has an extra " (e.g. ?"), which makes it not work perfectly for
those places.  Being able to turn off a feature that is not perfect is good, but
it does not mean that the feature works 100%.

That we have such hiding is a good thing.  I do not at all argue, as was decided
in the `...', "..." case, that the feature should not be in Emacs.

That we have a way to turn it off is also a good thing.  The bug is still there,
however.  I don't know how feasible/easy it is to fix.






      reply	other threads:[~2013-01-26 15:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-26  0:07 bug#13552: 24.3.50; glitch in Info formatting for cross reference Drew Adams
2013-01-26 10:57 ` Eli Zaretskii
2013-01-26 15:45   ` Drew Adams [this message]

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=A86C945B4EE746A1908A83D297C9DE78@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13552@debbugs.gnu.org \
    --cc=eliz@gnu.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).