Gnus development mailing list
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: Gnorb and org-refile-use-outline-path
Date: Wed, 07 Nov 2018 00:45:09 +0100	[thread overview]
Message-ID: <87k1lpixdm.fsf@web.de> (raw)
In-Reply-To: <87o9b2wwvr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 05 Nov 2018 22:19:52 -0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> > would it make sense to provide an Gnorb version of the
> > org-refile-use-outline-path option (with a non-nil default value)?
> >
> > I find the current dialog to which heading to associate an article
> > confusing because it doesn't show me the full paths.  I thought things
> > are broken until I studied the code and found
> > org-refile-use-outline-path.  Maybe Org fans are not suprised, I dunno.
>
> Oh, inside `gnorb-gnus-outgoing-do-todo'?

I wanted it for `gnorb-gnus-incoming-do-todo', but yes.

> Sure, I'd be happy to add that. You think t would be a reasonable
> default? I'd never noticed since my org-refile seems to have been
> taken over by helm.

Helm is the better interface here, the vanilla completion doesn't show
all candidates unless you enter parts of the path.

Anyway, the only difference between org-refile-use-outline-path -> t and
org-refile-use-outline-path -> 'file seems to be that t uses paths of
the format

  x/y/z/ (todo.org)

while 'file uses

  todo.org/x/y/z/

'file behaves much better IMHO: it feels more logical, while t also has
some issues, for example in one case I got something illegal like

  x/y/z/ (todo.org) (todo.org)

Also when hitting tab, often the cursor lands after (todo.org), and you
have to move it after /z/ to add something to the path.

So I would suggest 'file as default, but note I only tried a couple of
times.  Dunno if this setting influences how Helm behaves - it would
hopefully just ignore it.


Michael.



  reply	other threads:[~2018-11-06 23:45 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 [this message]
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
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=87k1lpixdm.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).