Hi Nicolas,
> Rasmus writes:
>> Nicolas Goaziou writes:
>>
>>> I introduced \nbsp at some point, but there were complaints from users
>>> not prettifying entities. So I guess \star is not an option either.
>>
>> Don't worry I use \nbsp sometimes!
>> For what reason do people not want to use enti
Rasmus writes:
> Nicolas Goaziou writes:
>
>> I introduced \nbsp at some point, but there were complaints from users
>> not prettifying entities. So I guess \star is not an option either.
>
> Don't worry I use \nbsp sometimes!
> For what reason do people not want to use entities? Speed?
Becaus
Nicolas Goaziou writes:
> I introduced \nbsp at some point, but there were complaints from users
> not prettifying entities. So I guess \star is not an option either.
Don't worry I use \nbsp sometimes!
For what reason do people not want to use entities? Speed?
Perhaps we could make it easier t
Rasmus writes:
> Maybe ~***~. But it has side-effects of course. Using \star in place
> of * is another easy possibility.
I introduced \nbsp at some point, but there were complaints from users
not prettifying entities. So I guess \star is not an option either.
I have no opinion about ~***~.
Lele Gaifax writes:
> What about having an option to use alternative chars, maybe some fancy
> Unicode glyph? "→", "⇒", "⦿", or even some kind of non-breakable-space come to
> mind.
Alternative chars doesn't solve the problem with the default one. Also,
we try to keep Org syntax ASCII compatible
Nicolas Goaziou writes:
> Maybe "* * *" instead of "***"? Any better idea?
Maybe ~***~. But it has side-effects of course. Using \star in place
of * is another easy possibility.
—Rasmus
--
I almost cut my hair, it happened just the other day
Nicolas Goaziou writes:
> This is a silly bug actually: *...* is for bold markup, so *** is
> exported as a bold star.
Oh, I see, thank you!
> I'd rather not make an exception and modify bold parsing, so other
> characters should be inserted to represent headline's level. I find
> numbers too v
Hello,
Lele Gaifax writes:
> I use Org (Emacs 24.4.90, with Org mode 8.2.10) to analyze and plan the
> development of new projects/features, with a persistent columnview containing
> a summary, something like the following:
>
> #+TITLE: Test
> #+PROPERTY: Effort_ALL 1:00 2:00 3:00 4:00 5
Hi all,
I use Org (Emacs 24.4.90, with Org mode 8.2.10) to analyze and plan the
development of new projects/features, with a persistent columnview containing
a summary, something like the following:
#+TITLE: Test
#+PROPERTY: Effort_ALL 1:00 2:00 3:00 4:00 5:00 6:00 7:00 8:00
#+COLUMNS
