Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Gnorb and org-refile-use-outline-path
Date: Thu, 08 Nov 2018 09:43:35 -0800	[thread overview]
Message-ID: <874lcrsbw8.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87bm6zscab.fsf@ericabrahamsen.net>

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> I was sort of thinking that if the Gnorb option were set to the value
>>> of the Org option, then users would just end up with the same behavior
>>> in Gnorb that they'd customized in Org. Sometimes I get confused about
>>> the order of evaluation of custom options, though -- maybe they would
>>> get the pre-customization, default Org value?
>>
>> Yes, the result would simply depend on whether they set the Org option
>> before loading Gnorb.  There is no good solution to that problem I
>> guess.  You could make it so that the default value of the Gnorb option
>> would make Gnorb check the value of the Org option dynamically at run
>> time.  If it is non-nil, we would use that value, if it is nil, we could
>> use 'file instead.
>
> So like this?
>
> (eval-after-load 'org
>   (unless gnorb-gnus-refile-use-outline-path
>     (setq gnorb-gnus-refile-use-outline-path
> 	  org-refile-use-outline-path)))

Quoted, of course....




  reply	other threads:[~2018-11-08 17:43 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 [this message]
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
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=874lcrsbw8.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).