emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Morgan Willcock <mwillcock@precedence.co.uk>
To: Timothy <tecosaur@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] ox-ascii.el: Fix justify when `indent-tabs-mode' is non-nil
Date: Sun, 19 Sep 2021 16:30:48 +0100	[thread overview]
Message-ID: <87czp4y447.fsf@precedence.co.uk> (raw)
In-Reply-To: <87wnncd7sw.fsf@gmail.com> (Timothy's message of "Sun, 19 Sep 2021 21:13:54 +0800")

Timothy <tecosaur@gmail.com> writes:

> Hi  Morgan,
>
> I’ve just taken a look at your patch (it `git am's just fine), since nobody else
> seems to have had the time to look at your patch as of late. There’s one thing
> which I now realise completely slipped by me last time — why are tabs bad?
> Maybe I’m missing something obvious, but exporting with tabs and viewing/`cat'ing
> the file everything looks fine to me in terms of alignment.

Hi Timothy,

It seems to default to spaces everywhere else. If you export an actual
document through the ascii exporter instead of just a document header
you will get a mix of tabs and spaces. This is how it was brought to my
attention, I was distributing a file that was batch exported and someone
pointed out that the indentation was inconsistent.

If it is handled as an export preference or defaults to the global
indentation preference then that would be fine but I don't believe
either of those are the case.

Thanks for continuing to look,
Morgan


  reply	other threads:[~2021-09-19 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-17 23:07 [PATCH] ox-ascii.el: Fix justify when `indent-tabs-mode' is non-nil Morgan Willcock
2021-08-31 11:59 ` Timothy
2021-08-31 12:42   ` Morgan Willcock
2021-08-31 12:54     ` Timothy
2021-09-19 13:13 ` Timothy
2021-09-19 15:30   ` Morgan Willcock [this message]
2021-09-19 17:02     ` Timothy
  -- strict thread matches above, loose matches on Subject: below --
2021-08-17 22:28 Morgan Willcock

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=87czp4y447.fsf@precedence.co.uk \
    --to=mwillcock@precedence.co.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@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).