ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: ConTeXt users <ntg-context@ntg.nl>
Subject: [NTG-context] Re: (feature proposal) link to attachments: /GoToE
Date: Sun, 3 Sep 2023 19:23:18 +0200	[thread overview]
Message-ID: <c418a99d-661c-3572-f561-778877d1d5e5@gmx.es> (raw)
In-Reply-To: <83b1d3cf-4972-06df-e61f-31b007a96d21@fiee.net>

On 9/3/23 16:02, Henning Hraban Ramm wrote:
> Am 03.09.23 um 13:03 schrieb Pablo Rodriguez:
> [...]
> While I don’t know what’s missing under the hood, I think there’s just a
> “reference” key missing in \attachment or \setupattachment:

Many thanks for your reply, Hraban.

I’m afraid that \in{attachment}[foobar] doesn‘t generate a link in your
sample.

Or do you get a link border from the following source?

  \setupinteraction[state=start]
  \enabledirectives[references.border=green]
  \starttext
  \startTEXpage[offset=1em]

  \attachment[
     file={hacker.jpg},
     method=hidden,
     reference=foobar,
  ]
  \goto{Link to attachment}[foobar]
  \stopTEXpage
  \stoptext

Many thanks for your help,

Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2023-09-03 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03 10:17 [NTG-context] " Pablo Rodriguez
2023-09-03 10:46 ` [NTG-context] " Hans Hagen
2023-09-03 11:03   ` Pablo Rodriguez
2023-09-03 14:02     ` Henning Hraban Ramm
2023-09-03 17:23       ` Pablo Rodriguez [this message]

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=c418a99d-661c-3572-f561-778877d1d5e5@gmx.es \
    --to=oinos@gmx.es \
    --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).