From: Axel Kielhorn <tex@axelkielhorn.de>
To: "ntg-context@ntg.nl" <ntg-context@ntg.nl>
Subject: Re: Projects and URLs
Date: Sat, 3 Nov 2018 10:25:23 +0100 [thread overview]
Message-ID: <1FF01FE1-CE3A-4C80-B598-50B992464406@axelkielhorn.de> (raw)
In-Reply-To: <639a7213-24df-5a74-3932-b1b0bd104624@gmail.com>
> Am 02.11.2018 um 13:08 schrieb Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>:
>
> Axel Kielhorn schrieb am 02.11.18 um 10:10:
>> Hello!
>>
>> Where is the best way to define URLs in a project?
>>
>> I currently define them when I need them, but wouldn’t it be better to keep them in a project file and have only one location to edit when they change?
>
> When you use \useurl in combination with \url or \from you can define them in a environment file. To make themeasier to handle you can use a separate environment file only for the urls.
>
>
> \setupinteraction[state=start]
>
> \useurl [garden] [https://wiki.contextgarden.net/] [ConTeXt garden]
>
> \starttext
>
> \url [garden]
>
> \from[garden]
>
> \stoptext
Is there a way to loop over all defined urls to generate a link list (like a bibliography)?
Axel
___________________________________________________________________________________
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:[~2018-11-03 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:10 Axel Kielhorn
2018-11-02 12:08 ` Wolfgang Schuster
2018-11-03 9:25 ` Axel Kielhorn [this message]
2018-11-03 16:25 ` Alan Braslau
2018-11-02 13:30 ` Henning Hraban Ramm
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=1FF01FE1-CE3A-4C80-B598-50B992464406@axelkielhorn.de \
--to=tex@axelkielhorn.de \
--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).