unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
	emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: info invisible changes
Date: 06 Nov 2002 13:46:28 +0100	[thread overview]
Message-ID: <5x7kfqoogr.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <buo1y5zc9gs.fsf@mcspd15.ucom.lsi.nec.co.jp>

Miles Bader <miles@lsi.nec.co.jp> writes:

> storm@cua.dk (Kim F. Storm) writes:
> > >   (1) The dir file (and presumably other info menus) I have was
> > >       formatted assuming that no text would be hidden, so in some cases,
> > >       the invisible text results in a very wierd looking display.
> > 
> > > * CVS client/server     Describes the
> > > 						     client/server protocol
> > > 						     used by CVS.
> > 
> > I have added code to properly align (+2 spaces) the following description
> > lines.  Please try it out.
> 
> Hmmm, well it looks _less_ bad: now the text is all in a properly-
> indented, but absurdly narrow column.

Weren't they in an absurdly narrow column already ?  ;-)


> 
> I agree with Stefan that the text should be refilled in the top-level
> dir node -- it's special because it contains much more hidden text than
> a normal node, and looks especially bad without refilling, and also it's
> not connected with a file (it's generated), so it's safe to modify.

Yes, I'll see what I can do to improve this.

> 
> Morever, the format of the menu entries seems regular enough that
> finding the bounds required to fill/reindent; something like
> 
>   (goto-char START-OF-MENU-ENTRY-TEXT)
>   (forward-sentence)
>   (while (looking-at ".*\n[ \t]+[^ \t]")
>     (forward-sentence))
>   ;; point is now at END-OF-MENU-ENTRY-TEXT
> 
> seems to work alright.
> 
Maybe.  If you send me some misc dir files which have particular problems,
I can probably do a better job at getting this right.
> 
> BTW, another wierd case I found is that sometimes footnotes are
> followed by a newline and a then period (when obviously there should be
> just a period).  For instance, in `(emacs)Glossary', I see:
> 
> --- begin quote ---
> Aborting
>      Aborting means getting out of a recursive edit (q.v.).  The
>      commands `C-]' and `M-x top-level' are used for this.  See Quitting
> .
> ---  end quote  ---

So I need to massage the *note regexp even further it seems...

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

  reply	other threads:[~2002-11-06 12:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  8:04 info invisible changes Miles Bader
     [not found] ` <200211011623.gA1GNAL03601@rum.cs.yale.edu>
2002-11-05  4:08   ` Miles Bader
2002-11-05 18:49     ` Stefan Monnier
2002-11-07  4:49       ` Richard Stallman
2002-11-05 23:57     ` Kim F. Storm
2002-11-06  9:51       ` Miles Bader
2002-11-06 12:46         ` Kim F. Storm [this message]
2002-11-06 12:30           ` Miles Bader
2002-11-06 15:11         ` Stefan Monnier
2002-11-06 16:32           ` Miles Bader
2002-11-07 15:08           ` Richard Stallman
2002-11-12 10:11             ` Kim F. Storm
2002-11-12  9:22               ` Miles Bader
2002-11-12 10:59                 ` Kim F. Storm
2002-11-12 17:28                   ` Robert J. Chassell
2002-11-13 14:37                     ` Kim F. Storm
2002-11-13 18:20                       ` Robert J. Chassell
2002-11-14 12:17                         ` Richard Stallman
2002-11-14 21:38                           ` Kim F. Storm
2002-11-12 18:49               ` Stefan Monnier
2002-11-13 23:31                 ` Kim F. Storm
2002-11-14  0:39                 ` Kim F. Storm
2002-11-14  4:09               ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2002-11-14 13:57 Karl Berry

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=5x7kfqoogr.fsf@kfs2.cua.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).