Re: Gnorb and org-refile-use-outline-path

[Eric Abrahamsen <eric@ericabrahamsen.net>]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> I fooled with it, and it looks like Helm ignores the value of
>> org-refile-use-outline-path. I'm running a patch version that sets
>> gnorb-gnus-refile-use-outline-path to the value of
>> org-refile-use-outline-path, which I expect will be the best way to not
>> surprise users.
>
> Hmm, the default value of `org-refile-use-outline-path' is in my
> experience not really usable with Gnorb.  Maybe the default of
> gnorb-gnus-refile-use-outline-path would better be
>
>   (or org-refile-use-outline-path 'file)
>
> ?
>
> I hate to change such defaults, too, but what I got when I tried to
> associate a message with Gnorb looked not only surprising but broken.
> It gets even problematic if you have different equal headlines in
> different positions, then it's not possible to select one of them AFAICT
> (you get only one completion candidate with that name).  I didn't try
> what happens if multiple files get into play.  I guess it gets even
> worse.
>
> What I'm probably actually saying is that org-refile-use-outline-path ->
> nil gives you a confusing behavior, no matter if using Org or Gnorb.

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?