emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Carsten Dominik <dominik@uva.nl>
Cc: emacs-orgmode@gnu.org, Ulf Stegemann <ulf-news@zeitform.de>
Subject: Re: Re: [IDEA] HTML-export literal examples to textarea
Date: Mon, 19 Jan 2009 23:16:09 +0100	[thread overview]
Message-ID: <E6310223-5906-46F7-802C-777E8BC34B0E@gmail.com> (raw)
In-Reply-To: <5B6BEE5C-A129-4C2B-9FB0-FA1E731D6442@uva.nl>


On Jan 19, 2009, at 6:16 PM, Carsten Dominik wrote:

>
> On Jan 19, 2009, at 12:14 PM, Ulf Stegemann wrote:
>
>> Hi Carsten,
>>
>> Carsten Dominik <dominik@science.uva.nl> wrote:
>>
>>> So it remains a kind-of specialistic thing.
>>
>> no, I wouldn't say so. textarea seems to have become quite popular in
>> HTML online documentation. Apart from all the copy and paste stuff,
>> textarea can do a virtual wrap or give you a horizontal scroll bar.  
>> This
>> is nice if you have literal text with long lines that can or should  
>> not
>> be wrapped but should also not exceed you layout's horizontal limits.
>> I'd guess this is the main reason, why textarea is widely used to  
>> give
>> literal examples.
>
> OK, so maybe this is more main-stream than I thought.  And, as  
> Sebastian
> just reminded us, we do have switch processing in examples already
> in place.
>
> So I will put it in, just using a "-t" option at the example (or src)
> block, and -h and -w options for width and height (cannot use -r for  
> rows,
> because -r is already taken.....)

OK, it is in:

#+begin_example -t -w 80 -h 20
...
#+end_example

HTH, thanks for the idea.

- Carsten

>
>
> Eric, no action for org-blocks necessary.
>
> - Carsten
>
>
>>
>>
>> Nevertheless, the textarea block is certainly just a nice-to-have and
>> not an absolutely necessary killer-feature.
>>
>>
>> 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 22:16 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
2009-01-19 11:14           ` Ulf Stegemann
2009-01-19 17:16             ` Carsten Dominik
2009-01-19 22:16               ` Carsten Dominik [this message]
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=E6310223-5906-46F7-802C-777E8BC34B0E@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --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).