unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Hiding  *Note:: "tags" in info files
Date: 01 Nov 2002 01:10:09 +0100	[thread overview]
Message-ID: <5xiszi176m.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <E187J6H-00040l-00@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

>     The following improved patch does that for *Note but not for *note.
> 
>     BTW, should it handle *note Item: Section. differently from *note Item:: 
>     (e.g. by hiding the Section part)?
> 
>     In any case, there are many incorrect uses of *Note: in the info files,
>     so you will still see a some "see See ..." occurrences.
> 
> How about checking for the presence of "see" in the buffer,
> and putting in "See" only if there is no "see"?

There are also other contexts where it doesn't make sense to add "see"
instead of the *note or *Note.  

I have now committed a change which looks for preceeding punctuation
to determine whether it should add "See ", "see ", or nothing before
the note text.  This only happens when font-lock-mode is enabled.

It also hides the "Section" part of the *note:... links to further improve
readability.

Furthermore, it hides the Section part of menu items, and replaces it by
a suitable number of spaces to properly align (previously mis-aligned)
menus and sub-menus.

I used the intangible property to make moving around in the info
buffer with normal cursor motion act sensible; consequently, I had to
bind inhibit-point-motion-hooks to t in the functions which parses the
various cross references.

IMHO, the result looks quite good.  WDYT?

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2002-11-01  0:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-29 12:03 Hiding *Note:: "tags" in info files Kim F. Storm
2002-10-29 17:11 ` Francesco Potorti`
2002-10-29 19:42 ` Eli Zaretskii
2002-10-30 17:17 ` Richard Stallman
2002-10-30 23:51   ` Kim F. Storm
2002-10-31  4:07     ` Karl Eichwalder
2002-10-31  4:24       ` Miles Bader
2002-10-31  6:00     ` Eli Zaretskii
2002-10-31 17:27     ` Richard Stallman
2002-11-01  0:10       ` Kim F. Storm [this message]
2002-11-01  2:24         ` Karl Eichwalder
2002-11-01  8:01           ` Eli Zaretskii
2002-11-01 15:30         ` Stefan Monnier
2002-11-01 23:22           ` Kim F. Storm
2002-11-02  8:08             ` Eli Zaretskii
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 11:49 Kim F. Storm
2002-10-30 13:20 ` Andreas Schwab
2002-10-30 14:14   ` Eli Zaretskii
2002-10-30 19:14     ` Andreas Schwab
2002-10-31 17:26     ` Richard Stallman
2002-11-01  8:57 Kim F. Storm
2002-11-01  9:34 ` Karl Eichwalder

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=5xiszi176m.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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).