From: Carsten Dominik <carsten.dominik@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-iswitchb documentation
Date: Tue, 29 Jun 2010 09:26:57 +0200 [thread overview]
Message-ID: <C50ED5EB-E603-4644-B4F6-DB2F33507639@gmail.com> (raw)
In-Reply-To: <3065.1277727993@maps>
On Jun 28, 2010, at 2:26 PM, Stephen Eglen wrote:
> Carsten Dominik <carsten.dominik@gmail.com> wrote:
>
>> I think this is actually a bug. Since the command is called ...-
>> iswitchb,
>> I am sure the intention was to use iswitchbe. Later, when we added
>> ido
>> support as well, the function was rewritten using
>> org-icompleting-read, and in this way the iswitchb support was lost.
>>
>>
>> How about the following solution:
>>
>> Check if either of org-completion-use-\(ido\|iswitchb\) is set. If
>> not,
>> bind org-completion-use-iswitchb around the call to org-icompleting-
>> read.
>
> Ok, now that makes a lot more sense! I wondered why the
> 'out-of-the-box' behaviour didn't show iswitchb like behaviour.
THe doc string now reads:
"Use `org-icompleting-read' to prompt for an Org buffer to switch to.
With a prefix argument, restrict available to files.
With two prefix arguments, restrict available buffers to agenda files.
This will either use ido or iswitchb for buffer name completion,
depending on the variables `org-completion-use-iswitchb' and
`org-completion-use-ido'. If both are nil, we will still use iswitchb
for this special application."
Agreed?
- Carsten
next prev parent reply other threads:[~2010-06-29 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 10:19 org-iswitchb documentation Stephen Eglen
2010-06-28 12:09 ` Livin Stephen Sharma
2010-06-28 12:22 ` Carsten Dominik
2010-06-28 12:26 ` Stephen Eglen
2010-06-29 7:26 ` Carsten Dominik [this message]
2010-06-29 8:14 ` Stephen Eglen
2010-06-29 8:43 ` Carsten Dominik
2010-06-29 9:44 ` Richard Riley
2010-06-29 9:51 ` Carsten Dominik
2010-07-02 7:14 ` Carsten Dominik
2010-06-29 22:46 ` Eric S Fraga
2010-06-28 13:00 ` Stephen Eglen
2010-06-28 15:14 ` Kim F. Storm
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=C50ED5EB-E603-4644-B4F6-DB2F33507639@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--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).