From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bug with vimtyping: no line numbers
Date: Tue, 12 Aug 2014 11:36:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1408121134060.16964@nqv-guvaxcnq> (raw)
In-Reply-To: <20140811173743.16f55a23@google.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 575 bytes --]
Hi,
On Mon, 11 Aug 2014, Günter Kolousek wrote:
>
> I think there is a bug in the (latest) beta that was not there earlier
> this year. In particular, it worked (and still works) in the version
>
> current version: 2014.03.19 23:11
>
> but it show *no* line numbers at all in the (latest) beta:
I do not have access to a computer that has the latest context right now.
I'll look into it when I get a chance.
In the meantime, can you check if
\starttext
\startlinenumbering
\input knuth
\stoplinenumbering
\stoptext
numbers the lines.
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2014-08-12 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 15:37 Günter Kolousek
2014-08-12 15:36 ` Aditya Mahajan [this message]
2014-08-12 20:07 ` Günter Kolousek
2014-08-13 14:39 ` Aditya Mahajan
2014-08-13 14:52 ` Wolfgang Schuster
2014-08-13 14:56 ` Aditya Mahajan
2014-08-14 8:19 ` Günter Kolousek
2014-08-14 16:16 ` Aditya Mahajan
-- strict thread matches above, loose matches on Subject: below --
2014-08-12 22:12 Akira Kakuto
2014-08-11 12:31 Günter Kolousek
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=alpine.DEB.2.02.1408121134060.16964@nqv-guvaxcnq \
--to=adityam@umich.edu \
--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).