Re: #+ candidates
Perry Smith writes: > The manual says I can type #+ and then hit M-tab to get the list of > completions. In my case, flyspell-mode had stolen that key binding so I > disabled flyspell-mode. > > There are 100 #+ candidates. Is there a nice place that lists them and > documents each one? So far, I’ve yet to find one. It is sometimes nice to > browse through such a list just to become familiar with what is possible. See [[info:org#Main Index][org#Main Index]] (search for "keyword"). -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
#+ candidates
The manual says I can type #+ and then hit M-tab to get the list of completions. In my case, flyspell-mode had stolen that key binding so I disabled flyspell-mode. There are 100 #+ candidates. Is there a nice place that lists them and documents each one? So far, I’ve yet to find one. It is sometimes nice to browse through such a list just to become familiar with what is possible. Thank you, Perry signature.asc Description: Message signed with OpenPGP
[O] [Feature Request / Bug] Remove statistic cookies from refile candidates
I set up my refile targets and this is what I get when I'm trying to refile something from notes.org. ``` Refile subtre Test to (default devel.org/Project): devel.org/[0\0][0%] Project ``` Is this possible to remove automatically these statistics cookies from completion candidates list? I know that I could write some custom function to list refile targets but this option could be available by default. Regards, Marcin
Re: [O] [bug] org-refile makes ido think that some candidates are directories
i have not been able to track this down further. has anybody taken a look at it? On 8/27/13, Samuel Wales samolog...@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.
[O] [bug] org-refile makes ido think that some candidates are directories
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.
