emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Philip Blagoveschensky <philip@crabman.me>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: When auto-fill breaks a link into multiple lines, the link is no longer displayed as a link
Date: Sun, 6 Sep 2020 17:14:42 +0000 (UTC)	[thread overview]
Message-ID: <45ff237d-23f3-4e5d-89d1-1a658c8d962d@crabman.me> (raw)
In-Reply-To: <877dt9iky9.fsf@gnu.org>

Do you mean that I can probably fix it by changing what fonts I use? If so, I'd rather do that than tinker with emacs trying to make a reproducible recipe.

Philip Blagoveschensky

4 сент. 2020 г. 19:08:19 Bastien <bzg@gnu.org>:

> Hi Philipp,
> Philip Blagoveschensky <philip@crabman.me> writes:
>> Sometimes org-mode breaks links into multiple lines: sometimes
>> Auto-Fill   does this, sometimes me invoking org-fill-paragraph does
>> this. When it happens, org-mode displays them incorrectly, but only
>> after I reload the file (see the attached screenshot, there's a
>> newline symbol before the word "field"). How do I either
>> - Make it stop breaking links?
>> - Make it display them correctly even if they are broken?
> I think I see what you mean, because I sometimes have broken links
> too, but would you care to provide a reproducible recipe, so that we
> can see what goes wrong when?  This is probably more due to an Emacs
> fontification limitation than an Org issue.
> Thanks,
> -- 
> Bastien

  reply	other threads:[~2020-09-06 17:16 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 [this message]
2020-09-06 17:22     ` Bastien
2021-04-16  4:51       ` Yukio Siraichi

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45ff237d-23f3-4e5d-89d1-1a658c8d962d@crabman.me \
    --to=philip@crabman.me \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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).