From: Nicola <nvitacolonna@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: How to write readable source files?
Date: Sun, 25 Apr 2021 12:12:09 -0000 (UTC) [thread overview]
Message-ID: <s63map$419$1@ciao.gmane.io> (raw)
In-Reply-To: <20210425071335.GA8308@sokrates>
On 2021-04-25, juh <juh+ntg-context@mailbox.org> wrote:
> I am married to Emacs but have an affair with Vim. ;-)
Eventually, you will abandon the dark side of the Force ;-)
> 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.
If there is a way to automatically get a list of all ConTeXt commands
and options (and, ideally, MetaFun defs, types, and other keywords), I'd
be happy to improve omni-completion for ConTeXt in Vim.
Nicola
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-04-25 12:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 9:45 Jan U. Hasecke
2021-04-24 11:55 ` Henning Hraban Ramm
2021-04-24 13:25 ` Hans van der Meer
2021-04-24 13:45 ` juh
2021-04-24 19:25 ` Nicola
2021-04-25 7:13 ` juh
2021-04-25 12:12 ` Nicola [this message]
2021-04-25 12:24 ` Hans Hagen
2021-05-29 15:03 ` Nicola
2021-05-29 17:08 ` Hans Hagen
2021-05-29 18:29 ` Nicola
2021-05-29 23:04 ` Hans Hagen
2021-05-30 8:13 ` Nicola
2021-04-24 12:12 ` luigi scarso
2021-04-24 15:17 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='s63map$419$1@ciao.gmane.io' \
--to=nvitacolonna@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).