From: "Stefan Monnier" <monnier+gnu/emacs/pretest@rum.cs.yale.edu>
Cc: storm@cua.dk (Kim F. Storm),
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>,
emacs-devel@gnu.org, emacs-pretest-bug@gnu.org
Subject: Re: info invisible changes
Date: Wed, 06 Nov 2002 10:11:41 -0500 [thread overview]
Message-ID: <200211061511.gA6FBfL02691@rum.cs.yale.edu> (raw)
In-Reply-To: buo1y5zc9gs.fsf@mcspd15.ucom.lsi.nec.co.jp
> Hmmm, well it looks _less_ bad: now the text is all in a properly-
> indented, but absurdly narrow column.
>
> 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.
It's also special because it tends to itself not be properly
aligned/filled because each entry can come from a different dir
file (and also from different .texi files (via their .info
and install-info)) so the alignment of text is often strange.
to start with, unless all the dir files have been manually
edited.
In most other menus, the entries are of the form '* blabla::' and
there is thus nothing to hide, really.
> 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
I'd use (re-search-forward "^[^ \t]"). I believe that's what I use
in Info-remove-duplicates.
> BTW, on the issue of whether it's OK to modify the buffer contents, I think
> it should be OK; (buffer-file-name) is always nil in the *info* buffer, after
It now indeed is nil. It used to be the case that it sometimes was
nil sometimes not.
> all. I think a lot of this stuff would become _much_ simpler if you could
> must munge the buffer instead of using invisible/display properties (with all
> their associated oddities), perhaps using text properties to store the
> necessary non-displayed info instead of parsing the buffer for it -- of
> course this would perhaps be a bigger change, since you'd have to modify the
> various info-getting functions too, but I don't see why it would be _that_
> big a job (presumably the modified code would support both text-property
> stored info and buffer-parsing, for backward compatibility).
I disagree. Especially since it's all customizable, it's easier and
safer to keep only one buffer-format and change the appearance
via properties.
Stefan
next prev parent reply other threads:[~2002-11-06 15:11 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
2002-11-06 12:30 ` Miles Bader
2002-11-06 15:11 ` Stefan Monnier [this message]
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=200211061511.gA6FBfL02691@rum.cs.yale.edu \
--to=monnier+gnu/emacs/pretest@rum.cs.yale.edu \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=storm@cua.dk \
/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).