Alan Schmitt <alan.schm...@polytechnique.org> writes: >> Maybe you could switch to the git-versions? > > OK, I gave it a try, and I'm now using them.
Thanks, that make things easier. > I can already report that the 'g' speed command does not work as > expected. It seems to work (it brings up a list of possible targets), > but there are two issues. > > 1. The target does not include the current file, although I have this > configuration: > > #+begin_src emacs-lisp > (setq org-refile-targets > '((my-todo-file :maxlevel . 10) > (nil :maxlevel . 10))) > #+end_src > > 2. The current entry is actually refiled (instead of simply having the > point move to the target). As you can see when you look in the tj-outshine branch, I did a kind of 'industrial mass production of user-commands', i.e. I produced the functions and the keybindings that port all Org commands to outshine (using 'outshine-use-outorg'), but I did not have the time to check them. Some might work out-of-the-box, others not, and other might not make sense at all in Outshine. So I have to look at them one by one, and the next one I will check is outshine-refile-targets, thx for your observations. > Maybe I should look into doing this the navi way. Assume you want to > reach an entry with "foobar" in its title, but you don't know at what > level this entry is. How would you do it? As I wrote in my last mail, I think outshine-imenu (using idomenu, you have to install that package for ido-style completion) does exacly what you want - offer all file headers with smart completion, so you only need to type 'foo' or so to get the "foobar" headline. Typing RET then moves point to the headline. -- cheers, Thorsten
