On Wed, Apr 21, 2021 at 8:19 PM carl harris <[email protected]> wrote:
> One thing to note about RST tables — there are two ways to do table > markup, and pandoc has selected the one that is most painful to maintain, > but looks most attractive in plaintext form. The “simple table” markup is > less attractive in plaintext form, but is definitely much less of a > nuisance to maintain, and has fewer options for exotic nesting/merging of > cells within columns/rows. > > +1 on the observation that RST relies on indentation, but (at least in my > experience) that reliance feels pretty natural and intuitive, and the > alternatives aren’t all that appealing. Quoting the RST specification, > "Indentation is used to indicate -- and is only significant in indicating > -- block quotes, definitions (in definition lists), and local[ly] nested > content”. To me, it feels acceptable (and sort of obligatory) to ident > consistently in the plaintext source in all of these situations anyway. But > I move pretty freely and easily between “bracey” languages like > Java/Javascript/XML and Python, so maybe I’m not too representative of > “typical” Guacamole contributors in that regard. > > I do this to some degree, too - I dabble in Python, and use Ansible (YAML) on a routine basis for automation, so I'm used to working between languages like those that rely on indentation and then back to Java, JavaScript, C, etc., that couldn't care less is you had whitespace anywhere in the code or not. So, while it may take some getting used to, I don't think that's a show-stopper for RST. -Nick
