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 <theophil...@gmail.com> wrote: > > Samuel Wales <samolog...@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
