From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Left margin of vim module output
Date: Wed, 1 Aug 2012 21:17:01 +0200 [thread overview]
Message-ID: <20120801211701.6d72a5c8@homerow> (raw)
In-Reply-To: <alpine.LNX.2.02.1208011414120.21530@ybpnyubfg.ybpnyqbznva>
On 2012-08-01 Aditya Mahajan <adityam@umich.edu> wrote:
> > I'll add a margin key to vim module (but not the oddmargin and
> > evenmargin keys; they would require a complete low-level rewrite
> > of the module).
Thanks a million. That was fast :)
> The dev version on github now includes a margin key,
Does it? I just can see a new test file in the recent commit history
(without margin key, however). Did you already push the changes to
the public repo?
> I haven't tested it too much
That's my part, I guess
> hence no new release at the moment).
No problem, I'm totally fine with the git repo.
> Note that this works differently from \definetyping. The typing
> environment honors the leftskip set by its parent environment (for
> example, if typing is inside startbackground); vimtyping
> environment resets all the settings of its parent environment.
That's why the hacks that I tried before all miserably failed.
Thanks again!
Marco
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-08-01 19:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 7:56 Marco Patzer
2012-08-01 17:46 ` Aditya Mahajan
2012-08-01 18:01 ` Aditya Mahajan
2012-08-01 18:18 ` Aditya Mahajan
2012-08-01 19:17 ` Marco Patzer [this message]
2012-08-01 19:26 ` Aditya Mahajan
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=20120801211701.6d72a5c8@homerow \
--to=homerow@lavabit.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).