emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: bugs in commenting and filling
Date: Mon, 27 Aug 2012 09:44:42 -0700	[thread overview]
Message-ID: <CAJcAo8sxZCC7-v9RasM3h79sf0F0kjY_x2oG_FOEZbb+Fc-ctg@mail.gmail.com> (raw)

Here are 6 bugs (or at least changes that might need to be
documented) in Org commenting and filling.

Context: commenting and filling used to use generic Emacs
facilities, but now use Org-specific ones.

original:

===
x

bug 1: the line above now does not get commented even if
comment-empty-lines is t.

  bug 2: this line now does not indent consistently with the
rest of emacs.
===

comment-dwim:

===
# x

# bug 1: the line above now does not get commented even if
# comment-empty-lines is t.

  # bug 2: this line now does not indent consistently with the
# rest of emacs.
===

  bug 3: outside of org with filladapt turned OFF, filling this
paragraph does not
indent it.  also auto-fill
indents unlike the rest of emacs.  ret tab is ok.

#bug 4: this paragraph now gets exported in HTML subtree
#export, which will likely surprise many people who formerly
#used "#" comments instead of "# " comments and don't
#carefully check all output.  they might
#even publish private information automatically without
#realizing it using old files that they forgot or did not
#know to convert.

#bug 5: filling this paragraph with "===" on the following
#line will fill the ===, unlike the rest of emacs with
#filladapt turned ON.  we are supposed to not use filladapt
#with org.  therefore, how do you emulate the filladapt
#behavior so that there is consistency between emacs and
#org?

Bug 6: what does the Org-specific commenting do?  i was not
able to determine that from the docstring to
org-comment-or-uncomment-region.  maybe update docstring
would help others trying to find out why commenting works
differently in org from the rest of emacs?

Hope it helps.

Thanks.

Samuel

-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

next             reply	other threads:[~2012-08-27 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 16:44 Samuel Wales [this message]
2012-08-28 11:44 ` bugs in commenting and filling Nicolas Goaziou
2012-08-31  2:01   ` Samuel Wales
2012-08-31  6:10     ` Nicolas Goaziou
2012-08-31  7:20       ` Samuel Wales
2012-08-31  7:32       ` Samuel Wales
2012-08-31  7:34         ` 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=CAJcAo8sxZCC7-v9RasM3h79sf0F0kjY_x2oG_FOEZbb+Fc-ctg@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

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).