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: Complex paragraph filling - how?
Date: 30 May 2003 03:01:47 +0200	[thread overview]
Message-ID: <5xznl5tfgk.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <m19LAIy-000IeIC@rattlesnake.com>

"Robert J. Chassell" <bob@rattlesnake.com> writes:

>    In connection with the refilling of paragraphs in info due to the new
>    "node hiding", I need some way to fill things like the following in a
>    sensible manner:
> 
> Please post your Texinfo source code.  It does us no good to see a
> surface expression.  Also, how well does the source format for DVI and
> HTML?  (And shouldn't this question really go to the texinfo-bug list?
> That is where refilling issues like this are usually discussed.)

I probably expressed myself wrong...

I'm trying to solve a specific problem with Info-fontify-node in
info.el, so I'm talking about re-filling the output from makeinfo
after the links have been mangled...  

So I don't see why this is an issue for the Texinfo team!

In any case, I think I have found a working solution by using
the following settings:

	(let ((fill-nobreak-invisible t)
	      (fill-individual-varying-indent nil)
	      (paragraph-start "\f\\|[ \t]*[-*]\\|[ \t]*$")
	      (paragraph-separate "[ \t]*[-*]\\|[ \t\f]*$")
	      (adaptive-fill-mode nil))

and then use fill-individual-paragraphs to do the filling.

Seems to DWIM, but I need to test it some more.


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

      reply	other threads:[~2003-05-30  1:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-29  0:22 Complex paragraph filling - how? Kim F. Storm
2003-05-28 23:26 ` Robert J. Chassell
2003-05-30  1:01   ` Kim F. Storm [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=5xznl5tfgk.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).