From: Michael Ash <mash@econs.umass.edu>
To: ntg-context@ntg.nl
Subject: Re: Updating modules with a ppa:reviczky/context-daily installation
Date: Sat, 3 Aug 2013 12:11:49 -0400 [thread overview]
Message-ID: <CAKTWfUMmXify=CJrcxtqxnaOCkYWkEDM+fK6AQFHrDMG9LszkA@mail.gmail.com> (raw)
In-Reply-To: <CAKTWfUO8S-rDgP3HMfBKm6taFjWevkwtbSKCOtBa--ucL6MGfQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1888 bytes --]
I would like to bump my question back into the queue. Thank you for your
consideration.
I would also like to add: where can I put files that I would like context
to "see". For example if I have a file "env_letter.tex" which I include
with \environment env_letter that includes a bunch of boilerplate, what is
a good directory to put it in?
Thanks.
Michael
On Wed, Jul 31, 2013 at 9:57 AM, Michael Ash <mash@econs.umass.edu> wrote:
> I have a question about how to update context modules.
>
> In earlier correspondence
> Question: I am still having a problem with...[the letter module]
> Answer: This is now fixed...
>
> I use a context installation managed by ubuntu/apt-get from the Personal
> Package Archive *ppa:reviczky/context-daily* (
> https://launchpad.net/~reviczky/+archive/context-daily). The current
> version is:
> ConTeXt ver: 2013.07.24 14:11 MKIV beta fmt: 2013.7.31 int:
> english/english
>
> How is it possible to (1) tell which version of a module is installed? (2)
> update a module to the latest version?
>
> Because I use the PPA version, I have not used first-setup.sh. I have
> only a limited understanding of where the context supporting material is
> maintained.
>
> Thank you very much for your guidance.
>
> Best,
> Michael
>
> PS Thank you very much for the guidance on the correspondence
> documentation and the reference line alternatives in the letter module
> > BTW are the values for the "alternative" key ("example", "e", "c", etc.)
> documented somewhere?
> You can look at the predefined arguments in the old manual which is
> available online: https://bitbucket.org/wolfs/correspondence/downloads.
>
--
Michael Ash, Chair, Department of Economics
Professor of Economics and Public Policy
University of Massachusetts Amherst
Amherst, MA 01003
Email mash@econs.umass.edu
Tel +1-413-545-2590 Twitter https://twitter.com/michaelaoash
[-- Attachment #1.2: Type: text/html, Size: 3127 bytes --]
[-- 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:[~2013-08-03 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 13:57 Michael Ash
2013-08-03 16:11 ` Michael Ash [this message]
2013-08-03 16:40 ` Marco Patzer
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='CAKTWfUMmXify=CJrcxtqxnaOCkYWkEDM+fK6AQFHrDMG9LszkA@mail.gmail.com' \
--to=mash@econs.umass.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).