From: James Thomas <jimjoe@gmx.net>
To: tpeplt <tpeplt@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: [ANN] org-tchanges.el: Collaborate with Office (docx) users using 'track changes'
Date: Wed, 15 May 2024 03:28:26 +0530 [thread overview]
Message-ID: <864jb0cayl.fsf@gmx.net> (raw)
In-Reply-To: <87cypow38p.fsf@gmail.com> (tpeplt@gmail.com's message of "Tue, 14 May 2024 16:24:54 -0400")
tpeplt wrote:
> A minor matter, but your source files ‘org-tchanges.el’ and
> ‘org-tchanges.lua’ contain tab characters in assorted places.
>
> 1. Consider replacing those tab characters with space characters so that
> your intended indentation is unambiguous.
Thanks! I'd intended to run 'untabify' but forgot about it. Pushed.
Regards,
James
prev parent reply other threads:[~2024-05-14 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 7:03 [ANN] org-tchanges.el James Thomas
2024-05-13 8:49 ` Eric S Fraga
2024-05-13 22:37 ` [ANN] org-tchanges.el: Collaborate with Office (docx) users using 'track changes' James Thomas
2024-05-14 8:07 ` Eric S Fraga
2024-05-14 20:24 ` tpeplt
2024-05-14 21:58 ` James Thomas [this message]
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864jb0cayl.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=help-gnu-emacs@gnu.org \
--cc=tpeplt@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.
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).