From: Bastien <email@example.com>
To: Philip Blagoveschensky <firstname.lastname@example.org>
Subject: Re: When auto-fill breaks a link into multiple lines, the link is no longer displayed as a link
Date: Sun, 06 Sep 2020 19:22:52 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Philip Blagoveschensky's message of "Sun, 6 Sep 2020 17:14:42 +0000 (UTC)")
Philip Blagoveschensky <email@example.com> writes:
> Do you mean that I can probably fix it by changing what fonts I use?
Nope, I mean the issue might come from the way Emacs add faces like
bold, etc (aka "fontification".)
> If so, I'd rather do that than tinker with emacs trying to make a
> reproducible recipe.
A reproducible recipe is like immutable gold to this community: it
means that everyone can reproduce your problem and that everyone can
try fixing it: otherwise Linus's law "given enough eyeballs..." does
not really hold anymore.
Just saying :)
next prev parent reply other threads:[~2020-09-06 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 9:32 When auto-fill breaks a link into multiple lines, the link is no longer displayed as a link Philip Blagoveschensky
2020-09-04 16:08 ` Bastien
2020-09-06 17:14 ` Philip Blagoveschensky
2020-09-06 17:22 ` Bastien [this message]
2021-04-16 4:51 ` Yukio Siraichi
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).