From: Sebastian Rose <sebastian_rose@gmx.de>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: information/feature request: org analog to latex \description environment
Date: Tue, 09 Sep 2008 23:04:54 +0200 [thread overview]
Message-ID: <87prndghe1.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <8763p5vz05.fsf@gmail.com> (Eric Schulte's message of "Tue, 09 Sep 2008 13:35:22 -0700")
Hi Eric,
"Eric Schulte" <schulte.eric@gmail.com> writes:
> Hi Sebastian,
>
> I was not clear enough in my original email. I did find the method you
> describe in the orgmode mailing list archives, however I feel that (to
> me at least) the biggest benefit would be in the ability to edit files
> in org-mode with `fill-paragraph', automated line endings, and even
> bolding of the term to be defined. Using a syntax like
>
> ,----
> | first term: and it's definition
> | second: and it's definition
> `----
How should Org distinguish those colons from other colons?
> would be much preferable to what I currently often find myself doing
> which is
>
> ,----
> | - *first term*: and it's definition
> | - *second*: and it's definition
> `----
This is what I did too :-) I even wrote a little little elisp function
to do this for me. But since a few weeks there is:
- Term1 :: description (try to press ALT-RET here)
- Term2 :: description (try to press ALT-RET here)
Are you aware of this syntax?
'Term' is displayed as bold text then.
Unfortunately this is currently only supported for XHTML-Export, where
this becomes a definition-list:
<dl>
<dt>Term1</dt>
<dd>description (try to press ALT-RET here)</dd>
<dt>Term2</dt>
<dd>description (try to press ALT-RET here)</dd>
</dl>
It does not work like this on LaTeX export though. But I guess this will
follow soon (it's quite a fresh feature).
> granted this is largely just synactic sugar, but small edit helpers like
> this are part of what make org so great!
>
> Do you think features like this would be generally useful and practical
> to implement?
Definetively, yes. All that's needed is some volunteer to implement the
feature in org-export-latex.el or where ever.
Regards,
--
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover
Tel.: +49 (0)511 - 36 58 472
Fax: +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose@emma-stil.de, sebastian_rose@gmx.de
Http: www.emma-stil.de
next prev parent reply other threads:[~2008-09-09 21:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 19:42 information/feature request: org analog to latex \description environment Eric Schulte
2008-09-09 21:04 ` Bernt Hansen
[not found] ` <87zlmhgjnv.fsf@kassiopeya.MSHEIMNETZ>
[not found] ` <8763p5vz05.fsf@gmail.com>
2008-09-09 21:04 ` Sebastian Rose [this message]
2008-09-09 22:19 ` Eric Schulte
2008-09-10 6:46 ` Carsten Dominik
2008-09-21 7:22 ` Carsten Dominik
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=87prndghe1.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@gmail.com \
/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).