From: Diego Zamboni <firstname.lastname@example.org>
To: Greg Minshall <email@example.com>
Cc: org-mode-email <firstname.lastname@example.org>
Subject: Re: tabs turned into space when going into Org Src...?
Date: Wed, 23 Dec 2020 12:28:19 +0100 [thread overview]
Message-ID: <CAGY83EdwHx6+49oFtV-hkdT7Uu-i5_zFkRCKE3PL=4jF6yE+8A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
I just did a quick test and I cannot reproduce this, the tabs remain on
entering, modifying and exiting block-edit mode.
One question: do you see "Makefile" as the mode when you are editing the
source block? Otherwise I imagine tab-to-space conversion might be taking
On Wed, Dec 23, 2020 at 8:05 AM Greg Minshall <email@example.com> wrote:
> hi. it seems going into Org Src, at least from a "makefile" source
> block, changes the tabs (the the base org mode added for me) into
> spaces, and leaves them as spaces when i merge back into the main .org
> file (and, so, make(1) complains, "missing separator").
> is this intentional?
> #+begin_src makefile
> echo all done
> note that the first character of the "echo" line is a <TAB> (or, was,
> when i composed this message, sigh). do a C-', and note that in the Org
> Src buffer, the "echo" line will start with a string of spaces.
> cheers, Greg
> ps -- is there some way i should escape/mime'ify such source blocks in
> e-mail (to this list, at least)?
[-- Attachment #2: Type: text/html, Size: 1581 bytes --]
next prev parent reply other threads:[~2020-12-23 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 7:05 tabs turned into space when going into Org Src...? Greg Minshall
2020-12-23 11:28 ` Diego Zamboni [this message]
2020-12-23 12:34 ` Greg Minshall
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).