Changes

<cd:shortdesc><!-- a short command summary goes here -->The command <tt>\goto</tt> is used for ...clickable links

You should not normally have to use this commandfor reference links inside your document. Links Internal links are better made using {{cmd|in}}, {{cmd|at}} or {{cmd|atabout}}, which are more conceptual (and lookup the section or page number as well).

If But if you want to implement some custom command for building links, this command is useful. You might also want to use the {{cmd|ref}} command for getting the raw page number, section number, section title, etc.

Or if you want to create a clickable link to something outside of the current document. {{todo|there are examples below of various possible arguments in #2, but not a proper list of options}}</cd:description>

(of course the wiki cannot really make a workable link)</cd:example><cd:example title="Link Links to an URLURLs"><texcode>

</texcode></cd:example><cd:example title="Link to a page"><texcode>\goto{Other page}[page(3)]</texcode></cd:example><cd:example title="Open a file or program"><texcode>\goto{Start}[program(test.tex)]</texcode> By enclosing {{cmd|goto}}’s destination in <tt>program(#1)</tt> youhave some means of launching files or programs. Of course, this is a security issue. However, PDF readers seem to handle this inconsistently. The following ''test.tex'' will attempt to open itself.Notice that per default PDF readers stay in the current workingdirectory.<texcode>\setupinteraction[state=start]\starttext\goto{A file}[program(test.tex)]\par % case 1: destination specified\goto{A command}[program(/usr/bin/kwrite test.tex)]\par % case 2: program and destination specified\stoptext</texcode> ==== Behavioural study of PDF viewers ==== This comparison was made on Linux/x86 and OSX 10.9.5 (replacing <tt>/usr/bin/kwrite test.tex</tt> with <tt>/Applications/Preview.app test.pdf</tt>). YMMV. {|cellpadding="10" style="border:2px solid #eeeeee"! reader! version! behaviour|-| acroread| 9.2, Linux/x86| ''Case 1'' succeeds. Runs the associated mime type application on the argument.''Case 2'' results in a file error.|-| Acrobat Reader DC| 2017.009, OSX| ''Case 1'' succeeds after asking back. Runs the default application for .tex files.''Case 2'' fails with a file not found message.|-| Acrobat Pro| 9.5.5, OSX| ''Case 1'' succeeds after asking back. Runs the default application for .tex files.''Case 2'' fails with a file not found message.|-| okular| 0.11.2, Linux/x86| ''Case 1'' succeeds. Runs the associated mime type application on the argument.''Case 2'' fails.Note that calling an executable (without the file argument)will be prevented by Okular for safety reasons.|-| xpdf| 3.02, Linux/x86| ''Case 1'' fails.''Case 2'' succeeds: Xpdf allows execution of arbitrary commands in a shell with user privileges.|-| Google Docs| as of 2010-10-24| ''Case 1'' fails.''Case 2'' fails.|-| mupdf| 7.2, Linux/x86| ''Case 1'' fails.''Case 2'' fails.|-| Preview.app| 7.0, OSX| ''Case 1'' fails (nothing happens).''Case 2'' fails with a file not found message.|-| File Viewer.app| 1.4, OSX| ''Case 1'' succeeds. Runs the default application for .tex files.''Case 2'' fails with a file not found message.|-| PDF.js| Opera 49, Firefox 61, OSX| Links are not active, nothing happens.|}</cd:example></cd:examples>

<cd:commandref name="about"></cd:commandref><cd:wikipage page="URL"></cd:wikipage><cd:commandref name="ref"></cd:commandref></cd:seealso>