emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: "Valentin Wüstholz" <wuestholz@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [PATCH] org.el: Preserve indentation of manually indented lines in example blocks.
Date: Tue, 09 Aug 2011 15:21:05 +0200	[thread overview]
Message-ID: <87vcu6lnzy.fsf@gmail.com> (raw)
In-Reply-To: <CAPVO5rw_NkGpyDfEfTW6VNmQaz2XKH9XPHONNChaPGkfhYkTMQ@mail.gmail.com> ("Valentin Wüstholz"'s message of "Tue, 9 Aug 2011 14:10:51 +0200")

Valentin Wüstholz <wuestholz@gmail.com> writes:

> At least that's my understanding of what /literal/ examples should
> give you. Besides, you don't need to fix each line separately: simply
> removing the indentation and auto-indenting the block will get you the
> desired results.

Ah, true. I hadn't thought about that. I guess it's not that bad then.

> I would love to hear how other people feel about this.

Same here. I don't use such blocks very often after all.

Meanwhile, could you please reformat a bit your patch (no more than 80
columns, no parents on their own line), add a commit message followed
by TINYCHANGE (unless you have signed FSF papers already) and use git
format-patch for the output?

>> To sum it up, in the first case, you only loose the ability to indent
>> the whole buffer in one go (which isn't as bad as it sounds, since you
>> can achieve that differently).
>
> How else would you be able to achieve that?

You may still indent regions without examples blocks, you can also
indent automatically each line you're writing.

I rarely indent globally buffers I wrote.

> I might be wrong, but I believe that at least in LaTeX indentation in
> verse blocks is not taken into account. This seems reasonable since
> they are not typeset in a monospaced font.

Actually indentation is partially taken into account. Some \hspace*{1cm}
are added. On the other hand, HTML enforces indentation with the help of
&nbsp;.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2011-08-09 13:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 19:48 [PATCH] org.el: Preserve indentation of manually indented lines in example blocks Valentin Wüstholz
2011-08-08 20:40 ` Nicolas Goaziou
2011-08-08 21:04   ` Valentin Wüstholz
2011-08-08 22:33     ` Nicolas Goaziou
2011-08-09  5:42       ` Valentin Wüstholz
2011-08-09  9:18         ` Nicolas Goaziou
2011-08-09 12:10           ` Valentin Wüstholz
2011-08-09 13:21             ` Nicolas Goaziou [this message]
2011-08-09 19:37               ` Valentin Wüstholz
2011-08-10  9:00                 ` Nicolas Goaziou
2011-08-16 17:21                   ` Bastien
2011-08-16 19:18                 ` Bastien
2011-08-16 21:33                   ` Valentin Wüstholz
2011-08-17  9:40                     ` Bastien
2011-08-17 18:32                       ` Valentin Wüstholz
2011-08-18 16:44                         ` Bastien
2011-08-26  6:45                           ` Valentin Wüstholz

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=87vcu6lnzy.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=wuestholz@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).