emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "Eric Schulte" <schulte.eric@gmail.com>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: information/feature request: org analog to latex \description environment
Date: Tue, 09 Sep 2008 15:19:57 -0700	[thread overview]
Message-ID: <877i9l0xo2.fsf@gmail.com> (raw)
In-Reply-To: <87prndghe1.fsf@kassiopeya.MSHEIMNETZ> (Sebastian Rose's message of "Tue, 09 Sep 2008 23:04:54 +0200")

Sebastian Rose <sebastian_rose@gmx.de> writes:

>> ,----
>> | first term: and it's definition
>> | second: and it's definition
>> `----
>
>
> How should Org distinguish those colons from other colons?

yes, I suppose the double colons you show below would be required

>> 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?

No, I was not aware of that, it is exactly what I was after.

Thanks -- Eric

next prev parent reply	other threads:[~2008-09-09 22:20 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
2008-09-09 22:19       ` Eric Schulte [this message]
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=877i9l0xo2.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sebastian_rose@gmx.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

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).