From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Prevent auto-fill-mode from filling Property values in drawers
Date: Sun, 04 Feb 2018 23:16:47 +0100 [thread overview]
Message-ID: <87y3k8h034.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAFyQvY2b5MMB_osbBVdstzrX6eFiysJL1KAA4V8MBK7TRJw=-A@mail.gmail.com> (Kaushal Modi's message of "Sun, 04 Feb 2018 15:52:36 +0000")
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Of course. But "the right thing" would be to prevent call to auto filling
> within `org-return` (somehow? I haven't yet dug deeper into that) if point
> is in a property drawer.
`org-return' doesn't call any auto fill function.
> If you want to add a new property, use C-c C-x p, or, if you insist on
>> typing it manually, use C-q <RET> instead.
>>
>
> C-c C-x p is a bit unnatural and also longer to type than RET,
Yet, it doesn't break properties drawers.
> especially
> if the point is already inside the property drawer. Yes, if my point is
> inside the subtree, and I think of adding a property, C-c C-x p is great!
>
> C-q RET is a good tip, but again, RET would be better.
Actually, that would be C-q C-j, not C-q <RET>
> I'll try hacking something around this, tweaking org-return should work
> using a simple advice. Would a patch be welcome for this?
I don't think tweaking `org-return' is a good solution. This is not the
only way to break a line (e.g. "C-q C-j", or "C-M-o"), so it would not
be a panacea.
You may want to use fill-nobreak-predicate variable instead, e.g. with
`org-at-property-p'.
next prev parent reply other threads:[~2018-02-04 22:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 16:50 Prevent auto-fill-mode from filling Property values in drawers Kaushal Modi
2018-02-03 14:16 ` Kaushal Modi
2018-02-03 14:29 ` Nicolas Goaziou
2018-02-03 14:33 ` Kaushal Modi
2018-02-03 14:40 ` Nicolas Goaziou
2018-02-03 14:55 ` Kaushal Modi
2018-02-03 16:16 ` Nicolas Goaziou
2018-02-03 16:20 ` Nick Dokos
2018-02-03 17:41 ` Kaushal Modi
2018-02-03 18:11 ` Nick Dokos
2018-02-03 22:16 ` Nicolas Goaziou
2018-02-04 15:52 ` Kaushal Modi
2018-02-04 22:16 ` Nicolas Goaziou [this message]
2018-02-05 21:59 ` Kaushal Modi
2018-02-11 13:12 ` Nicolas Goaziou
2018-02-11 13:24 ` Kaushal Modi
2018-02-11 15:54 ` Nicolas Goaziou
2018-02-11 20:13 ` Kaushal Modi
2018-02-11 20:22 ` Nicolas Goaziou
2018-02-11 20:29 ` Kaushal Modi
2018-02-11 20:33 ` Nicolas Goaziou
2018-02-11 20:23 ` Kaushal Modi
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=87y3k8h034.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=ndokos@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).