From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: texinfo-fill-workaround.el -- no break after @: when filling
Date: Thu, 01 Sep 2005 00:00:54 -0400 [thread overview]
Message-ID: <87d5ntfnh5.fsf-monnier+gnu.emacs.sources__36481.9313319915$1125547638$gmane$org@gnu.org> (raw)
In-Reply-To: mailman.5657.1125538235.20277.gnu-emacs-sources@gnu.org
> and a similarly tiny function for no break after <a in html "<a href",
> which I think much improves human readability
> http://www.emacswiki.org/cgi-bin/wiki/HtmlMode
In Emacs-22, this is already done for all tags:
(defun sgml-fill-nobreak ()
;; Don't break between a tag name and its first argument.
(save-excursion
(skip-chars-backward " \t")
(and (not (zerop (skip-syntax-backward "w_")))
(skip-chars-backward "/?!")
(eq (char-before) ?<))))
Only problem is that with <a href="..." the URL is often so long that the
space between <a and href is the only space on the line so fill.el ignores
fill-nobreak-predicate.
Stefan
parent reply other threads:[~2005-09-01 4:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.5657.1125538235.20277.gnu-emacs-sources@gnu.org>]
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='87d5ntfnh5.fsf-monnier+gnu.emacs.sources__36481.9313319915$1125547638$gmane$org@gnu.org' \
--to=monnier@iro.umontreal.ca \
/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.
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).