emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Lucas Viana <lucasvianareis@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Fill-paragraph issue with hidden emphasis markers and composed characters
Date: Wed, 26 Oct 2022 06:58:52 +0000	[thread overview]
Message-ID: <87tu3roytv.fsf@localhost> (raw)
In-Reply-To: <CAC9BvE5sXk5pB6kZL72wsC-nMBbZbr=Hr8biwUXKR3U0vgqMUg@mail.gmail.com>

Lucas Viana <lucasvianareis@gmail.com> writes:

> Steps to reproduce:
> 1. Start emacs -Q (no configuration)
> 2. Set some variables:
> (setq org-pretty-entities t
>       org-hide-emphasis-markers t
>       fill-column 80)
> 3. Create an empty org-mode buffer with the following paragraph:
> ""
> This is a /italic sentence for a buggy/ \alpha\beta\gamma\delta\nu\epsilon
> paragraph in terms of filling, see, it's not filled yet and still the line
> above
> ends early.
> ""
> So far so good, and with the previous config the emphasis markers are now
> hidden and the greek letters appear as unicode characters.
> 4. Hit M-q (either fill-paragraph or org-fill-paragraph, both have the same
> issue)
> The first line wrongly wraps after "buggy" and leaves a big empty space
> after that, as if the greek letters were not composed.

This appears to be Emacs bug though.
I reported it in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=58791
Let's see what Emacs devs reply.

Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

  parent reply	other threads:[~2022-10-26  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 17:07 [BUG] Fill-paragraph issue with hidden emphasis markers and composed characters Lucas Viana
2021-08-10  1:34 ` Tim Cross
2021-08-10 22:57 ` Rudolf Adamkovič
2022-10-26  6:58 ` Ihor Radchenko [this message]
2022-10-27 10:39   ` Ihor Radchenko

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=87tu3roytv.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=lucasvianareis@gmail.com \


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