Hi Ihor,
sorry for being so silent, but I'm currently at 300% occupation. And
statistical mux doesn't work well on human beings...
Marking this as TODO...
thx,/pa
Enviado desde mi iPad
> El 2 may 2023, a las 14:51, Ihor Radchenko escribió:
>
> Ihor Radchenko writes:
>
>> One reasonable
Mehmet Tekman writes:
> Hello again, sorry for the delay - I had some holiday time off
> that couldn't wait ;-)
>
> I've modified the ob-tangle.el file for the main tangling and
> detangling functions. Most importantly, both functions can now
> exchange information from the source Org mode
On Tue, 2 May 2023 at 17:54, Ihor Radchenko wrote:
> I think `recentf-save-file' for example is no different. And
> org-id-locations-file. And custom-file, if you happen to save safe
> buffer-local variables by answering "!" in Emacs prompt. And many many
> other places.
Those two are easy to
On Sat, Apr 22, 2023 at 8:38 AM Ihor Radchenko wrote:
> Jim Wisniewski writes:
>
> > On Thu, Apr 20, 2023 at 4:46 AM Ihor Radchenko wrote:
> >
> >> Thanks! Let us know when FSF replies with a countersignature.
> >
> > Just got it back today.
>
> Thanks for the update!
> Bastien, may you
Gustavo Barros writes:
> For the record, even ".org.gpg" files generate an entry in the cache
> index. (True, not the `:persist-file' itself though).
>
> My ~/.cache/org-persist/index contains:
>
> (:container
> ((elisp org-element--headline-cache)
> (elisp org-element--cache))
>
Hello again, sorry for the delay - I had some holiday time off
that couldn't wait ;-)
I've modified the ob-tangle.el file for the main tangling and
detangling functions. Most importantly, both functions can now
exchange information from the source Org mode file to the target
remote tangle file
On Tue, 25 Apr 2023 at 07:52, Gustavo Barros wrote:
> My view is that there really should be a way of doing it. Because this
> has relevant security implications. And because users should be able
> to have control of their data in the first place. And then if one such
> a feature, necessarily
On Tue, 02 May 2023 00:17:51 -0400 Christopher M. Miles wrote ---
> Indeed, this option solved the problem real neat.
> I'm surprised by your knowledge and digging problem skill.
> I have to say a big TANKS to you. THANKS, THANKS, THANKS. Hahaha
My thanks as well to everyone who
"Christopher M. Miles" writes:
>> Do you have any issues decrypting and encrypting files from command
>> line? If no, what about from M-x shell? If yet no, what if you call gpg
>> via `start-process'?
>>
>
> - [X] test decrypt & encrypt in terminal with gpg command. -> works fine.
>
> - [X] test
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> I downgrade gnupg, then the problem solved. But the downgrade version is
>> very old (gnupg@2.4.1 -> gnupg@2.2.41). I suspend problem is somewhere
>> else, like Emacs interaction with GnuPG process.
>
> Do you have any issues
Carlo Tambuatco writes:
> And are there any plans to incorporate more?
I am wondering why you are asking on Org mode mailing list...
Emacs has 0% rust code and has no plans to incorporate any, AFAIK.
See https://yhetil.org/emacs-devel/b972c046-8c29-42eb-92c9-0d5b5fe03551@Spark
--
Ihor
And are there any plans to incorporate more?
Ihor Radchenko writes:
> One reasonable option could be keeping relative paths relative iff the
> #+BIBLIOGRAPHY is derived from a file inside the same directory with the
> exported file.
>
> Tentative patch attached.
I applied an alternative patch that uses the approach from
Ihor Radchenko writes:
>> The patch is against main only because it overlaps a region where bugfix
>> and main diverged. I am willing to provide a similar patch against
>> main.
>
> I do not think that we in a hurry to put this onto bugfix.
> Bugfix is just for trivial and critical fixes.
>
"Christopher M. Miles" writes:
> I downgrade gnupg, then the problem solved. But the downgrade version is
> very old (gnupg@2.4.1 -> gnupg@2.2.41). I suspend problem is somewhere
> else, like Emacs interaction with GnuPG process.
Do you have any issues decrypting and encrypting files from
Max Nikulin writes:
>> And we do not need to do anything about it, right?
>
> I posted the links as a reminder that shell commands should be avoided
> when possible (and it does not break TRAMP) and arguments should be
> escaped otherwise.
But this patch literally fixed the problem. What else
On 01/05/2023 18:18, Ihor Radchenko wrote:
Max Nikulin writes:
I just have noticed that it is tracked as a CVE record:
https://www.cve.org/CVERecord?id=CVE-2023-28617
https://nvd.nist.gov/vuln/detail/CVE-2023-28617
And we do not need to do anything about it, right?
I posted the links as a
On 02.05.2023 08:18, Nathan Van Ymeren wrote:
When I specify double width floats, they appear with slashes embedded
in the RESULTS blocks, like so:
#+begin_src lisp
(+ 1 0.0002d0)
#+end_src
#+RESULTS:
: 1\.0002d0
[...]
Is this a bug? If not, how do I suppress this behaviour?
Do you
Hi all,
For my studies I’ve been using org as a superior form of jupyter notebook, and
I do my assignments and whatnot using code blocks for computation. My
preferred language these days is Common Lisp, using the SBCL implementation.
Whereas languages like python default to using IEEE
19 matches
Mail list logo
