emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Ido org-refile results in misfiling
Date: Thu, 31 May 2012 19:51:36 -0700	[thread overview]
Message-ID: <CAJcAo8u2pQcA3GLO8wFE6j0FYcqt+FEyYrOfHYvmUCdoFi6HSg@mail.gmail.com> (raw)

Ido and org-refile are a superb combination that enhances
Org significantly.  It is a killer feature IMO.

However, in my usage there is a substantial risk of
misfiling:

  1) If I start from a fresh Emacs, "myorg" is sufficient to
     select "computer/emacs/org/myorg/".  This is good.

  2) If I refile something to
     "computer/emacs/org/myorg/strategy and examples/various
     todo kw and maybe some tags/", "various" is enough to
     select it.  Note that this is below "myorg".  Also good.

  3) (Just as an aside, if I then refile something else to
     the same entry, I don't even need to enter "various".
     It is the default.  A nice feature.)

  4) Now suppose I want to refile something to "myorg".  I
     enter "myorg" but I get "various".

Detail on this subtle issue is below:

===

My expectation is that if "myorg" selects "myorg" once, it
should always do so no matter what my refile history is.
This expectation is violated.

It violates a sort of referential transparency.  The same
narrowing inputs should produce the same narrowed outputs
(in my expectation at least).

I suspect that the reason for the unexpected behavior is related (in
some way) to
the defaulting in 3, which is useful.  However, the false defaulting in 4 is
NOT useful in any obvious way.

===

Proposed solution:

I think that as soon as the user starts selecting something,
the default should be discarded.

===

With my expectation, it is never necessary to check the
offered olpaths except as a confirmation.

With the current behavior, checking is always necessary
because in edge cases, there will be a guaranteed misfile.

Here is why: the only reason that default showed up at all
is that the narrowing input /happened/ to match both
headlines.  Otherwise the default would have been discarded.
So it is an edge case that allowed the offer to misfile.  In
other cases, the correct default would be provided.  If I
wanted "various", RET would be sufficient.

User checking is significantly more error-prone because one
olpath is a substring of the other.

Likewise, the requirement to navigate in the list is
burdensome as 4 is never useful as far as I can tell.

===

Is there any way to fix this?  I tried looking at ido
customizations and got lost.

If you can't reproduce witn your ido settings, I'll try to
provide an MCE at some point.  Might take a while though.

Thanks.

Samuel

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

next             reply	other threads:[~2012-06-01  2:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-01  2:51 Samuel Wales [this message]
2012-06-01 21:45 ` Ido org-refile results in misfiling Darlan Cavalcante Moreira
2012-06-01 22:13   ` Samuel Wales
2013-07-17 23:31 ` Samuel Wales

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=CAJcAo8u2pQcA3GLO8wFE6j0FYcqt+FEyYrOfHYvmUCdoFi6HSg@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

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).