From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: another auto-fill bug
Date: Fri, 19 Oct 2012 10:04:01 -0700 [thread overview]
Message-ID: <CAJcAo8u=YD=+TJxcBSvoaQmTgMnQt_fxifFk1aR6DLjbYNKxKQ@mail.gmail.com> (raw)
If you press SPC after this with the appropriate fill-columun setup,
Org will incorrectly comment the next line.
===
# It's not as if bad guys always aim
# for the loss of life per se. They often just consider the
# loss of life less important than their real goal.
I won't go into the details, because I don't use the term.
===
Just out of curiosity, what would be the incorrect behavior that would
result if Org used Emacs standard filling and auto-filling instead of
its own?
Thanks.
Samuel
--
The Kafka Pandemic: http://thekafkapandemic.blogspot.com
next reply other threads:[~2012-10-19 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 17:04 Samuel Wales [this message]
2012-10-20 10:05 ` another auto-fill bug Nicolas Goaziou
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='CAJcAo8u=YD=+TJxcBSvoaQmTgMnQt_fxifFk1aR6DLjbYNKxKQ@mail.gmail.com' \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.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).