Kill RST
Mads Kiilerich
mads at kiilerich.com
Fri Mar 6 09:40:54 EST 2015
On 03/02/2015 07:59 PM, Sean Farley wrote:
> Thomas De Schampheleire writes:
>
>> On March 2, 2015 7:35:36 PM CET, Sean Farley <sean.michael.farley at gmail.com> wrote:
>>> Thomas De Schampheleire writes:
>>>
>>>> Hi,
>>>>
>>>> The subject should be non-ambiguous but let me add a little more body
>>>> to it: currently comments and pull request descriptions are parsed as
>>>> RST (restructured text). From my perspective (and that of several
>>>> others) this is counterproductive and not necessary:
>>>>
>>>> - when typing a comment or PR description, the fact that newlines are
>>>> not preserved because deemed unimportant by RST is counter-intuitive
>>>> and above all annoying
>>>>
>>>> - having to remember how your plain text would be parsed by RST and
>>>> having to work around this explicitly is counterproductive.
>>> Yeah, I definitely agree with this.
>>>
>>>> - the average user does not need the features RST provides.
>>>>
>>>> So as far as I'm concerned, RST can be removed entirely.
>>>> The same has been done in Unity's tree with commit
>>>>
>>> https://bitbucket.org/Unity-Technologies/kallithea/commits/09286e5ca064de6930d5bdefb9df6708eda19976
>>>> However, I assume that some other people will find this too harsh, so
>>>> we can think of compromises, for example:
>>> Why not make RST 'just work'? i.e. if a user types plain text the
>>> output
>>> is plain text.
>> How do you distinguish plain text from RST?
> How do other projects do this? Trac, Redmine, etc. all have some fancy
> formatting that seems to work-ish?
I remember Trac being annoying too. It might be work-ish but I think it
would work better without markup.
/Mads
More information about the kallithea-general
mailing list