ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: copy & paste source code from documents
Date: Sat, 26 Nov 2016 11:40:03 +0100	[thread overview]
Message-ID: <c5d160ce-89f1-d518-d143-0e0caf86dcf4@wxs.nl> (raw)
In-Reply-To: <04A251BD-CBF5-4B76-8C7F-5290C0A655B3@arcor.de>

[-- Attachment #1: Type: text/plain, Size: 1961 bytes --]

On 11/26/2016 7:52 AM, Tobias Berndt wrote:
>
> Dear List,
>
> currently, I have to compose technical documents with a lot of source code in it. There're readers demands for a way to copy&paste this source code directly from those documents into their terminals. I tried ConTeXt’s attachment functionality, it is … ok. But most people don’t like files attatched to PDFs. Moreover, they must open it in an editor before getting contents in terminals. So,

normally a viewer is quite restricted out of security reasons

> is there any possibility in ConTeXt/Lua a document reader can click on a source code statement and the content of an external file (the plain code, without any typesetting) will be loaded into the clipboard, so that they can paste this plain source code into their terminal programs to use it directly?

here is an option (the last examples need an upcoming beta as i added 
better space support for verbatim comments)

\setupinteraction[state=start]

\starttext

\startbuffer[a]
for i=1,10 do
     print(i)
end
\stopbuffer

\typebuffer[a]

currently: \comment{\cldcontext{buffers.getcontent("a")}}

\blank

hacked: \comment{\cldcontext{string.gsub(buffers.getcontent("a"),
     "\string\r","\string\n")}}

\blank

new, space honored, still hack: 
\comment[space=yes]{\cldcontext{string.gsub(buffers.getcontent("a"),
     "\string\r","\string\n")}}

\blank

new, buffer honored: \comment[buffer=a]{}

\blank

idem: \comment[space=yes,buffer=a]{}

\stoptext

\definefallbackfamily[mainface][serif][texgyrepagella]
\definefontfamily[mainface][sans][texgyrepagella]
\setupbodyfont[mainface]

\starttext


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------

[-- Attachment #2: oeps.pdf --]
[-- Type: application/pdf, Size: 9802 bytes --]

[-- Attachment #3: Type: text/plain, Size: 492 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-11-26 10:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  6:52 Tobias Berndt
2016-11-26 10:40 ` Hans Hagen [this message]
2016-11-26 12:38   ` Tobias Berndt

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=c5d160ce-89f1-d518-d143-0e0caf86dcf4@wxs.nl \
    --to=pragma@wxs.nl \
    --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).