From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnorb and org-refile-use-outline-path
Date: Fri, 16 Nov 2018 13:39:16 -0800 [thread overview]
Message-ID: <874lcg3dob.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87tvkk6vqp.fsf@web.de>
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Oh, I see. But... I think it would be less surprising to just have Gnorb
>> behave the same way Org does. You never know what people think about
>> the defaults, and it seems likely that users who are annoyed by Org's
>> default behavior would have already changed it.
>
> I can't estimate. However, I would expect that there are also some
> Gnorb users that don't use Org that much (or at all) to know about
> org-refile-use-outline-path. If you think that most people using Gnorb
> also know Org and that option, is it really a win to provide an extra
> Gnorb option at all? I guess most people would at least want the same
> behavior for both Org and Gnorb.
Gnorb is almost completely useless without Org, so yes, I'm assuming
that Gnorb users would have already run into this issue and, if it
annoyed them, changed the Org default. I guess now that I think about
it, you're probably right that this just isn't a very useful option to
have in Gnorb. The Gnorb version of refile targets I still think is
useful, because users might want to confine their Gnorb activity to a
smaller range of Org files/headings. But I wouldn't want to provide this
option just because users might be annoyed by the Org defaults. I'll
think about this a bit, but might revert the addition.
> So, while I'm a bit Org agnostic, in my opinion the best thing to do
> would be to change the default of the Org option.
I think that's the right solution, and it's worth bringing up on the Org list!
next prev parent reply other threads:[~2018-11-16 21:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 5:02 Michael Heerdegen
2018-11-06 6:19 ` Eric Abrahamsen
2018-11-06 23:45 ` Michael Heerdegen
2018-11-07 4:45 ` Eric Abrahamsen
2018-11-07 5:39 ` Michael Heerdegen
2018-11-07 6:32 ` Eric Abrahamsen
2018-11-07 6:57 ` Michael Heerdegen
2018-11-08 17:35 ` Eric Abrahamsen
2018-11-08 17:43 ` Eric Abrahamsen
2018-11-09 2:43 ` Michael Heerdegen
2018-11-09 19:24 ` Eric Abrahamsen
2018-11-10 6:15 ` Michael Heerdegen
2018-11-12 19:46 ` Eric Abrahamsen
2018-11-13 5:57 ` Michael Heerdegen
2018-11-13 19:22 ` Eric Abrahamsen
2018-11-14 6:03 ` Michael Heerdegen
2018-11-16 21:39 ` Eric Abrahamsen [this message]
2018-11-17 14:43 ` Michael Heerdegen
2018-11-17 18:50 ` Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874lcg3dob.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).