emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [bug] org-do-emphasis-faces breaks with incomplete emphasis
Date: Tue, 16 Feb 2021 18:01:32 -0700	[thread overview]
Message-ID: <CAJcAo8vE1gUz5Mty3Zqq7FcOjW6Oq8b7tbPcgagioiOPhSnuzg@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8ts9D0B1fhNX8ALBX_amxX5-dC0+fs+kEM8x8cWw7prbw@mail.gmail.com>

to understant, perahsp try to look at the op and remove the line that says *hi*?

On 2/16/21, Samuel Wales <samologist@gmail.com> wrote:
> hi tim,
> tanks for your replies.
> 1.  the same problem occurs without any * in the buffer.
> 2.  the emphasis regexps are supposed to be limited to a few lines.
> 3.  they are also supposed to not try to match dissimilar delimiiters.
> the problem is that
> hi =something
> stops all emphasis of all types in the entire rest of hte bguffer even
> if the buyffer contains many lines.  this sems unusual to me.
> it does not break anything befofre it.
> so i think your hypothesis of what i am talking about might possibly
> not match what i am talking about at all.
> i am limited in coputer ue and will have to stop.
> tahnks for your replies.
> On 2/16/21, Tim Cross <theophilusx@gmail.com> wrote:
>> Samuel Wales <samologist@gmail.com> writes:
>>> to answer your question: i expected it to just skip the non-emphasis.
>>> not emphasizing the rest of the buffer seemed quite unusual.
>> I guess the problem is the same - how does org know when it is just a *
>> and when it is the beginning of some emphasis text? We could make it
>> that such markup only works on words, allowing the code to only consider
>> two * as emphasis if there are no spaces, otherwise treat as just a *,
>> but that would be inconvenient when you want to emphasis a phrase or a
>> couple of words. We could change the regexp to only consider it an
>> emphasis block if both markers are on the same line, but again,
>> potentially inconvenient and it would fail for those who use visual-line
>> mode where there paragraphs are just 1 long line.
>> In short, can understand what your saying, but not sure there is a
>> viable fix which doesn't have a heap of other consequences. Basically,
>> if you want to use the 'markup' characters as normal characters, you
>> need to either escape them or put them inside a verbatim directive.
>> --
>> Tim Cross
> --
> The Kafka Pandemic
> Please learn what misopathy is.
> https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html

The Kafka Pandemic

Please learn what misopathy is.

  reply	other threads:[~2021-02-17  1:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 22:47 [bug] org-do-emphasis-faces breaks with incomplete emphasis Samuel Wales
2021-02-16 22:59 ` Tim Cross
2021-02-16 23:53   ` Samuel Wales
2021-02-16 23:57     ` Samuel Wales
2021-02-17  0:09       ` Tim Cross
2021-02-17  0:59         ` Samuel Wales
2021-02-17  1:01           ` Samuel Wales [this message]
2021-02-17  1:06           ` Tim Cross
2021-02-17  2:42             ` Samuel Wales
2021-02-16 23:57     ` Tim Cross

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=CAJcAo8vE1gUz5Mty3Zqq7FcOjW6Oq8b7tbPcgagioiOPhSnuzg@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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).