emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Alignment in `org-list-dt'
Date: Wed, 13 Mar 2013 17:06:00 +0100	[thread overview]
Message-ID: <86a9q7nv2v.fsf@somewhere.org> (raw)

Hello,

I'm surprised by the way the alignment occurs for DT lists in Org buffers.

Here is an ECM:

--8<---------------cut here---------------start------------->8---
- Alt text :: Text description of a graphic that appears before the graphic is
              loaded into the browser. After an image has been downloaded on
              the browser, the alt text may briefly appear over the graphic as
              you rollover the mouse over the graphic.

- Anchor <a> :: The anchor tag is used to define a hypertext link.The anchor
                tag is used to define a hypertext link.

- Angle brackets ::
                   less than (<) and greater than (>) symbols used to surround
                   an element to create a tag.
--8<---------------cut here---------------end--------------->8---

After "Angle brackets", I added a newline and TAB'bed. What special is that
the cursor is positioned 1 char too much to the left IMO.

On an esthaetic POV, I don't find the above paragraphs (obtained thru `M-q',
bound to the command `fill-paragraph') as nice to read as they could or
should. Once you have a longer term, the definition must stay within a very
narrow column...

I prefer what the standard TAB'ing or M-q'ing does (_I don't understand_ why
it's that different) on the following ECM:

--8<---------------cut here---------------start------------->8---
- =:results replace= ::
     (default option) Insert results after the source block, replacing any
     previously inserted results.

- =:results silent= :: (default for Org results) Just send the commands, still
     echo the results in the minibuffer (to see code block output) and go.
     This option was originally added in the case where one *does not want to
     change the Org-mode buffer* (*no results are inserted* into the Org mode
     buffer -- even during export).

- =:results none= :: silent even for the minibuffer. Such a code block is run
                   for its side effects (by definition).
--8<---------------cut here---------------end--------------->8---

Only that last list item is not indented as nicely as the others (2 chars to
the right). Dunno why?

For info, if the "for" (first word on the second line) is not directly under
the "silent" (first word on the first line), that's not the case in my Org
file, because I use to hide the markup characters.

Best regards,
  Seb

-- 
Sebastien Vauban

             reply	other threads:[~2013-03-13 16:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13 16:06 Sebastien Vauban [this message]
2013-03-13 16:28 ` Alignment in `org-list-dt' Bastien
2013-03-13 19:49   ` Sebastien Vauban

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=86a9q7nv2v.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /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).