On Mon, 30 Jun 2025 at 19:34, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> >> >> Also, since we now allow multiple languages to be listed in #+LANGUAGE,
> >> >> we may need to update the manual when talking about #+LANGUAGE keyword
> >> >> in other places as well; not just
Hi,
On Mon, 30 Jun 2025 at 19:51, Ihor Radchenko wrote:
>
> Pedro Andres Aranda Gutierrez writes:
>
> >> Even though you did split the paragraph, it is IMHO, not yet ideal.
> >> When I read the two paragraph one after another I feel confused.
> >> When I read the LaTeX section from the beginning
Hello,
For couple of years, I had a setup for invoices similar to the one
described here:
http://notes.secretsauce.net/notes/2014/10/01_org-mode-for-invoices.html
I had one modification: every month, I create a file with just some
macro data, e.g.:
<2025-06.org>
#+PROPERTY: header-args+ :va
pinmacs writes:
>> Could you elaborate about the use cases when such timer is useful?
>
> Use case 1: ...
>
> Use case 2: ...
Thanks for the explanation!
It does look reasonable.
Note that `org-timer-start' already allows starting the timer with an
offset (see the docstring). An additional DWIM
Pedro Andres Aranda Gutierrez writes:
>> Even though you did split the paragraph, it is IMHO, not yet ideal.
>> When I read the two paragraph one after another I feel confused.
>> When I read the LaTeX section from the beginning, I feel even more
>> confused - what do these paragraphs do in LaTeX
Vangelis E writes:
> Does this mean that you will implement my suggestion in my previous email?
>
>> On 30 Jun 2025, at 17:42, Pedro Andres Aranda Gutierrez
>> wrote:
>>
>> Thanks for trying! I'm just trying to find a flexible solution for
>> future requirements like this...
>> /PA
>> ...
Be
Does this mean that you will implement my suggestion in my previous email?
> On 30 Jun 2025, at 17:42, Pedro Andres Aranda Gutierrez
> wrote:
>
> Thanks for trying! I'm just trying to find a flexible solution for
> future requirements like this...
> /PA
>
>> On Mon, 30 Jun 2025 at 09:54, Vang
Pedro Andres Aranda Gutierrez writes:
>> >> Also, since we now allow multiple languages to be listed in #+LANGUAGE,
>> >> we may need to update the manual when talking about #+LANGUAGE keyword
>> >> in other places as well; not just in latex export section.
>> You seemingly did not address this c
Tor-björn Claesson writes:
> Please find attached a new version of the patch for review.
Since there will be a another update on the patch, I am just posting what
I've done so far with this version.
I simplified the code a bit and got rid of s.el functions.
See the attached patches on top of th
Thanks for trying! I'm just trying to find a flexible solution for
future requirements like this...
/PA
On Mon, 30 Jun 2025 at 09:54, Vangelis Evangelou wrote:
>
> Hi Perdo.
>
> No, that doesn't fix it. I can see that add-texparse-filter is added to the
> org-export-filter-final-output-functions
On 28/06/2025 03:26, Charles Choi wrote:
On Jun 27, 2025, at 7:56 AM, Max Nikulin wrote:
P.S. Has anybody tried org-protocol with Emacs installed as flatpak?
Interesting. I can imagine how sandboxed applications on both Linux and
Windows (UWP) would have restrictions on accessing emacsclient a
On 30/06/2025 05:19, Anush V wrote:
30461 18:02:57.315361 write(2, "MESA-INTEL: warning:
../mesa-25.1.3/src/intel/vulkan/anv_formats.c:905: FINISHME: support more multi-planar
formats with DRM mod"..., 135) = -1 EPIPE (Broken pipe)
30461 18:02:57.315406 --- SIGPIPE {si_signo=SIGPIPE, si_code=SI
On 20/06/2025 13:05, Christian Moe wrote:
Max Nikulin writes:
[Evaluated code:]
location.href='org-protocol://store-link:/'+encodeURIComponent(location.href)+'/'+encodeURIComponent(document.title);void(0);
[Log:]
Navigated to
org-protocol://store-link/file%3A%2F%2F%2Fhome%2Fcm%2Fworg%2Forg-cont
Hi Ihor, more commits and a doubt:
> >> Also, since we now allow multiple languages to be listed in #+LANGUAGE,
> >> we may need to update the manual when talking about #+LANGUAGE keyword
> >> in other places as well; not just in latex export section.
> You seemingly did not address this comment.
Hi Perdo.
No, that doesn't fix it. I can see that add-texparse-filter is added to
the org-export-filter-final-output-functions, but the text doesn't appear
in the exported *Org LATEX Export* buffer.
On Mon, 30 Jun 2025 at 07:49, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:
> PS: You
15 matches
Mail list logo
