Visuwesh writes:
> I wonder if we should set compile-command to "make test" in dir-locals.el.
> This would make it easier to use project-compile for quick checks. (I should
> use this command more, thanks for the pointer.)
I think the default "make -k" is also useful. It will run compilation
Thanks for the cleanup!
I noticed the complete-file typo and fixed it after attaching the patch. I
regenerated the patch but I suppose it was created in a different directory,
and the filename in the mail pointed to the earlier incorrect patch instead.
I wonder if we should set compile-comma
Visuwesh writes:
> I went with a slightly different approach in the attached where an
> optional argument is accepted by the function, defaulting to the value
> of org-link-file-path-type.
Thanks!
Applied, onto main, with minor amendments.
I renamed the function, as suggested by Rudolf. I also f
Visuwesh writes:
> * lisp/ol.el (org-link--normalise-filename): New function...
This should be `org-link--normalize-filename', i.e. use the US spelling,
to match the Emacs/Org code base, e.g. `org-link--normalize-string'.
Rudy
--
"Logic is a science of the necessary laws of thought, without wh
[ஞாயிறு பிப்ரவரி 23, 2025] Ihor Radchenko wrote:
> Visuwesh writes:
>
>>> Visuwesh, do you want to proceed with this part?
>>
>> Do we only want this for images, or for everything? Everything entails
>> images, all dropped files, dropped image files only, and XDND.
>
> Everything, I think.
>
>>
Visuwesh writes:
>> Visuwesh, do you want to proceed with this part?
>
> Do we only want this for images, or for everything? Everything entails
> images, all dropped files, dropped image files only, and XDND.
Everything, I think.
> This would warrant a NEWS entry too, right?
Indeed.
> +(defu
[சனி பிப்ரவரி 22, 2025] Ihor Radchenko wrote:
>>> Visuwesh writes:
> 1. do a variable for selecting absolute path: to be able to have a file
> link that works with absolute path; and the reason is that being
> relative, this, does not combine good when you move your latex export
>>
Visuwesh writes:
>> That's one option - we can ask Emacs devs to provide a customization for
>> `yank-media' to auto-select specific type once it is available.
> ...
> I am leaning towards doing it in the Emacs side since it would get rid
> of similar annoyance(s) in other yank-media handlers, no
On 2024-09-22 10:01, Visuwesh wrote:
I am leaning towards doing it in the Emacs side since it would get rid
of similar annoyance(s) in other yank-media handlers, not just Org.
If no one beats me to it before the end of this week, I will propose a
patch to take care of (1). It would be preferabl
e can reuse this everywhere we
insert the link in yank-media+DND code (which IIRC uses the same
function at the very end).
>>> 2. do a variable that allow a list that would filter and reduce the type
>>> candidates of yank-media. In org-download, everything was png so I was
k-file-path-type'.
Probably, simply by factoring out the cond from `org-insert-link' and
then reusing it in yank handler.
>> 2. do a variable that allow a list that would filter and reduce the type
>> candidates of yank-media. In org-download, everything was png so I was
>
o go? I don't see how it is possible to make
org-yank-image-save-method accept another option.
> 2. do a variable that allow a list that would filter and reduce the type
> candidates of yank-media. In org-download, everything was png so I was
> not having the "Several types avai
/clipboard-20240916T013308.png]]= vs
=[[file:../../../tmp/clipboard-20240916T011913.png]]=
2. do a variable that allow a list that would filter and reduce the type
candidates of yank-media. In org-download, everything was png so I was
not having the "Several types available, choose one&qu
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
> docum
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
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
i have not been able to track this down further. has anybody taken a
look at it?
On 8/27/13, Samuel Wales 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 l
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-c
18 matches
Mail list logo
