From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ASCII mode within \footnote
Date: Thu, 7 Nov 2019 18:11:21 -0500 (EST) [thread overview]
Message-ID: <nycvar.YAK.7.76.1911071809310.22593@nqv-guvaxcnq> (raw)
In-Reply-To: <16d90cbf-b8c1-5381-a23e-46198b5a32fd@gmail.com>
On Thu, 7 Nov 2019, Wolfgang Schuster wrote:
> A way to avoid this problem is to use a slash a path separator
> instead of the backslash. Another way to get rid of it is to save
> the path a buffer and print the content of the buffer with the
> \typeinlinebuffer command.
>
>
> \starttext
>
> \startbuffer
> %APPDATA%\file.txt
> \stopbuffer
>
> \footnote{\typeinlinebuffer}
>
> \stoptext
Another option, if you have many such files is to define a macro:
\define[1]\APPDATA{\mono{\letterpercent APPDATA\letterpercent\letterbackslash#1}}
And then use:
\footnote{\APPDATA{file.txt}}
Aditya
___________________________________________________________________________________
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:[~2019-11-07 23:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 13:23 context
2019-11-01 13:36 ` Hans Hagen
[not found] ` <0e3fc588e96d00f1f235e1f3b9499335@vivaldi.net>
2019-11-02 9:45 ` context
2019-11-02 15:35 ` Aditya Mahajan
2019-11-04 11:36 ` context
2019-11-04 13:36 ` Aditya Mahajan
2019-11-04 14:05 ` Aditya Mahajan
2019-11-04 16:34 ` Wolfgang Schuster
2019-11-07 22:04 ` Wolfgang Schuster
2019-11-07 23:11 ` Aditya Mahajan [this message]
2019-11-08 8:52 ` Hans Hagen
2019-11-08 9:45 ` context
2019-11-05 13:43 ` context
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=nycvar.YAK.7.76.1911071809310.22593@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).