emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: Ulf Stegemann <ulf-news@zeitform.de>,
	Eric Schulte <schulte.eric@gmail.com>
Cc: Emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Re: [IDEA] HTML-export literal examples to textarea
Date: Mon, 19 Jan 2009 10:01:08 +0100	[thread overview]
Message-ID: <3440483C-0236-41B7-88B6-984D25A3EF7F@uva.nl> (raw)
In-Reply-To: <zf.upnljt7wu72.fsf@zeitform.de>

So it remains a kind-of specialistic thing.

Maybe Eric would like to add a textarea block to org-export-blocks.el?

- Carsten

On Jan 19, 2009, at 9:56 AM, Ulf Stegemann wrote:

> Carsten Dominik <dominik@science.uva.nl> wrote:
>
>> On Jan 19, 2009, at 8:25 AM, Ulf Stegemann wrote:
>>
>>> Hi Carsten,
>>>
>>> Carsten Dominik <dominik@science.uva.nl> wrote:
>>>
>>>> On Jan 16, 2009, at 10:51 AM, Ulf Stegemann wrote:
>>>>
>>>>> Is it worth thinking about an example block that will be  
>>>>> exported to a
>>>>> "<p><textarea ...>...</textarea></p>" structure in HTML export?
>>>>>
>>>>> I was recently playing around with org for online documentation.  
>>>>> The
>>>>> documents contained lots of literal examples that can be  
>>>>> directly copied
>>>>> and pasted e.g. into a terminal emu. While example- and src  
>>>>> blocks work
>>>>> fine, I think that putting this kind of information into a  
>>>>> textarea
>>>>> would be even better.
>>>>
>>>> Hi Ulf, so far I fail to see what the big advantage would be.  Can
>>>> you try again to explain?
>>>
>>> of course. Generally, selecting text is a bit easier inside an  
>>> input box
>>> but the very real advantage is that you can edit inside inputs. This
>>> allows to give literal examples with "variables" that can be changed
>>> directly inside the page before being copied and pasted.
>>
>> Hmmm, but why would you want to edit them in the text window, if you
>> will paste them into an editor anyway, where you probably can edit
>> them a lot easier?  Or are you talking about pasting examples
>> directly into an interpreter input stream?
>
> yes, in the concrete case the documentation was about a rather complex
> system and software setup and the "examples" were mainly meant to be
> copied and pasted directly into an terminal emu ... with variable  
> things
> like host-, path-, user names an so on. Of course, one could paste  
> this
> in an editor first to change something but as the changes would be
> rather minimal this would prove to be a bit clumsy.
>
> Actually nobody seems to do it like this. I asked the target group how
> they handle this and they told me, they just selected the text up to  
> the
> first variable, pasted it into the terminal, typed their variable  
> value
> into the terminal and then selected the rest of the example to  
> complete
> their command line(s).
>
> Ulf
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-01-19  9:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-16  9:51 [IDEA] HTML-export literal examples to textarea Ulf Stegemann
2009-01-17  8:01 ` Carsten Dominik
2009-01-19  7:25   ` Ulf Stegemann
2009-01-19  8:31     ` Carsten Dominik
2009-01-19  8:56       ` Ulf Stegemann
2009-01-19  9:01         ` Carsten Dominik [this message]
2009-01-19 11:14           ` Ulf Stegemann
2009-01-19 17:16             ` Carsten Dominik
2009-01-19 22:16               ` Carsten Dominik
2009-01-19 22:32                 ` Sebastian Rose
2009-01-20 11:34                 ` Ulf Stegemann
2009-01-19 10:57         ` Manish
2009-01-19 11:59           ` Sebastian Rose
2009-01-19 12:04             ` Manish
2009-01-19  9:02       ` Tassilo Horn

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3440483C-0236-41B7-88B6-984D25A3EF7F@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@gmail.com \
    --cc=ulf-news@zeitform.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).