Hi Nicola,

Am Sat, Apr 24, 2021 at 07:25:27PM -0000 schrieb Nicola:
> I maintain the ConTeXt plugin for Vim. Currently, there are no
> indentation rules (except for embedded MetaPost code), and that is
> intentional: as the examples above show, there is no commonly accepted
> indentation style, so forcing one on the user is not a good idea.

I am married to Emacs but have an affair with Vim. ;-)

I use it from time to time including your plugin.

I don't have a strong opinion about indentation. So I won't mind if a
tool would just do it for me. But I understand your point. And I tend to
say that not indenting text between start-stop-commands is the way I
want my text.

I don't like to reflow paragraphs as I want to have one line for
each sentence. This is my only opinion about formatting text. Not
indenting is a good idea because sometimes I have really long lines and
identation would make them even longer.

I real IDE-like support for ConTeXt would be nice: setup-en.pdf is
always open when I write environments as I cannot remember all commands
and options. If my editor would give me a list of possible commands when
I just type some letters and then give possible options when I edit
inside a command – that would be great. 

Thanks a lot for your help
Jan Ulrich Hasecke
-- 
Autoren-Homepage: ......... http://literatur.hasecke.com
Satiren & Essays: ......... http://www.sudelbuch.de
Privater Blog: ............ http://www.hasecke.eu
Netzliteratur-Projekt: .... http://www.generationenprojekt.de


Attachment: signature.asc
Description: PGP signature

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Reply via email to