emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [bug] org-refile makes ido think that some candidates are directories
Date: Wed, 13 Nov 2013 12:11:54 -0700	[thread overview]
Message-ID: <CAJcAo8uUvusL7_qZnnVSUpJ82SQMAOX1-zUYnGOgf+m-f1gDhQ@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8tAeb45q9YdkjjDA+3si7ukKcZPymALgZwr0efAFTtFeA@mail.gmail.com>

i have not been able to track this down further.  has anybody taken a
look at it?

On 8/27/13, Samuel Wales <samologist@gmail.com> wrote:
> org-refile makes ido think that every entry that is in the
> current buffer is a directory, while every entry that is
> in another buffer is a file.
>
> ===
>
> You can confirm by loading ido and doing this:
>
>   (setq org-refile-use-outline-path t)
>   (setq org-outline-path-complete-in-steps nil)
>   (setq org-completion-use-ido t)
>
> Now do org-refile and look at the candidate list.  Please
> note the addition of the filename at the end of the entries
> that are not in the current buffer, and probably a different
> font.  You can use the ido keys for navigating directories,
> and they will only go to the entries in the current buffer.
>
> ===
>
> The relevant part of org.el seems to be this, but I do not
> understand it:
>
>     (setq answ (funcall cfunc prompt tbl nil (not new-nodes)
> 			nil 'org-refile-history (or cdef (car org-refile-history))))
>
> This is FAR beyond my ability to debug, but I suspect
> that the artificial distinction between the current buffer
> and other buffers, treating one as a directory and the other
> as a file, might be related to several long-standing, subtle
> but extremely annoying bugs involving the default and
> history.  But I could be wrong about that.
>
> For example, if you previously refiled, there is always an
> extra entry that has no marker and errors if you select it,
> and it is often the default candidate :(.  And it is
> impossible to narrow to a subtree of the default subtree :(.
> I have previously reported at least one of these bugs.
>
> ===
>
> In any case, IMO, ido should treat all olpaths as if they
> were files.  Can anybody help track this down?
>
> Thanks.
>
> Samuel
>
> --
> The Kafka Pandemic: http://thekafkapandemic.blogspot.com
>
> The disease DOES progress.  MANY people have died from it.  ANYBODY can get
> it.
>
> Denmark: free Karina Hansen NOW.
>


-- 
The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.

Denmark: free Karina Hansen NOW.

      reply	other threads:[~2013-11-13 19:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-28  1:16 [bug] org-refile makes ido think that some candidates are directories Samuel Wales
2013-11-13 19:11 ` Samuel Wales [this message]

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=CAJcAo8uUvusL7_qZnnVSUpJ82SQMAOX1-zUYnGOgf+m-f1gDhQ@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.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.
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).