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

From: Ihor Radchenko <yantar92@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: FR: support hard-newlines [9.5.5 (release_9.5.5 @ /home/viz/lib/ports/emacs/lisp/org/)]
Date: Tue, 20 Sep 2022 21:37:44 +0800	[thread overview]
Message-ID: <875yhiyxnb.fsf@localhost> (raw)
In-Reply-To: <87pmfqmd7m.fsf@gmail.com>

Visuwesh <visuweshm@gmail.com> writes:

>> All in all, I feel that fully respecting `use-hard-newlines' in Org is
>> not a good idea. We can do it partially (for filling), but I am afraid
>> that it may create some confusion.
>
> I am not sure what you mean by confusion here: those who have
> `use-hard-newlines' turned on are explicitly asking for it.  If
> anything, I was confused when I found org-mode did not recognise
> hard-newlines.

Let me clarify.

Current state of affairs is: Org ignores `use-hard-newlines'
Proposed: Org sometimes ignores `use-hard-newline' and sometimes not.

I do believe that what you suggest is a good idea (respecting
`use-hard-newlines' when filling). However, I notice that some people
may be more confused if we implement this FR compared to the existing
situation. So, I am asking for feedback from other users instead of
accepting the FR.

>>> -		   (fill-region-as-paragraph c end justify)
>>> +		   (fill-region c end justify)
>>
>> There are 3 calls to `fill-region-as-paragraph' inside
>> `org-fill-element'. If we decide to support `use-hard-newlines'
>> partially, all 3 calls should probably be replaced.
>
> AFAICT, the rest two are comments (though I cannot tell the difference
> between "comment" and "comment-block").  I replaced the one in paragraph
> since that was where lack of hard-newlines support bit me.

# This is
# a comment

#+begin_comment
This is a
comment block.
#+end_comment

See 13.6 Comment Lines section of the manual.

I do not see why `use-hard-newline' should affect normal paragraphs but
not comments.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92

next prev parent reply	other threads:[~2022-09-20 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-18  6:13 FR: support hard-newlines [9.5.5 (release_9.5.5 @ /home/viz/lib/ports/emacs/lisp/org/)] Visuwesh
2022-09-20 12:16 ` Ihor Radchenko
2022-09-20 12:39   ` Visuwesh
2022-09-20 13:37     ` Ihor Radchenko [this message]
2022-09-20 14:03       ` Visuwesh

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=875yhiyxnb.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=visuweshm@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

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