Matthieu Caneill writes:
> I'm hit by the following bug in `org-element-cache-map'. When I use
> `tags' or `tags-todo' in an agenda, with the option
> `(org-tags-match-list-sublevels nil)', all sub-elements of a matching
> item are correctly skipped except the last one.
>
> It can be reproduced w
Tom,
> The only generalized solution is to record the full location (see
> intro to http://naggum.no/lugm-time.html which I'm surprised hasn't
> been linked in this thread yet, ...
very nice -- thanks for the pointer!
cheers, Greg
Ihor, Sterling, et al.,
just a thought/reminder. there are "semantics" and "encoding". a spec
like ISO-8601 specifies both. the important thing for org-mode is to
use an encoding that
1. is easily parsable/understandable by the mere mortal
2. allows expression of all the semantics of the unde
Ihor,
> Cons:
>
> 1. If compat.el happens to lack support of some function, we will need
>to contribute to compat.el directly and synchronize Org releases with
>compat.el releases.
would a separate "org-compat.el" (in addition to compat.el) somehow
solve this? (i worry about the synch'i
Sterling Hooten writes:
> This is an initial glossary compiled from various standards and sources;
> it's incomplete, probably incorrect, and open to critique, but is useful
> in articulating a possible road map forward.
Do I understand correctly that the terms are simply taken from ISO
(https:
Tom Gillespie writes:
> Oh boy. In short, I think we can only hope they come up with
> LTC and we already have a syntactic space to say whether
> our reference seconds are TAI/UTC/LTC/MTC/JTC etc. And
> being the privileged squats that we are if the time system is
> left out then it means UTC. Th
Sterling Hooten writes:
>> And we need to deviate from ISO 8601 anyway. At least, because it does
>> not define time zones, only absolute UTC offsets. So, the ability to
>> conform with the existing formats remains questionable.
>
> This is correct for the 2019 version of the ISO 8601.
>
> From m
Dear all,
I have gone through the maintainers of individual Org files and,
especially after Nicolas went missing from the list, the situation is
rather dire.
The following libraries have no maintainer or author active on the list:
ob-comint, ob-core, ob-css, ob-ditaa, ob.el, ob-emacs-lisp,
ob-ev
Renato Pontefice writes:
> I try to perform this simple line of emacs manual (this is the perfect page
> of the manual where I took this: where I took this: "31.13.10 Sexp Entries
> and the Fancy Diary Display”). Because trying to learn emacs I would try as
> many entry possibile as I could (I
Karl Voit writes:
>> What is the return value of
>>
>> (epg-list-keys (epg-make-context nil t t) org-crypt-key)
>>
>> ?
>>
>> Does it show the right key?
>
> It shows:
>
> (#s(epg-key ultimate
> (#s(epg-sub-key ultimate ... nil 1 4096 "ABC12345" 1515327255 nil
> "...ABC12345"
Matt writes:
> On Thu, 26 Jan 2023 04:51:19 -0500 Ihor Radchenko wrote ---
>
> > This will add a newline to "cmdproxy.exe" command -> "cmdproxy.exe\n".
> > You should instead look into `org-babel--write-temp-buffer-input-file'.
>
> I made the change in `org-babel--shell-command-on-regi
Hi all,
I got a patch for
https://orgmode.org/worg/org-tools/index.html
Does someone with access wants to apply it?
- Jakob
diff --git a/org-tools/index.org b/org-tools/index.org
index eec65e77..44c2fe3c 100644
--- a/org-tools/index.org
+++ b/org-tools/index.org
@@ -19,6 +19,7 @@ This page l
Richard Stallman writes:
> > However, I gues the point remains, sql.el and ob-sql.el support a number
> > of non-free RDMS
>
> Can someone post a verified list of which of them are non-free?
> Someone posted a list of a few, which I cannot find now in my saved
> inboxes, but I think it includ
writes:
> The point is myself I'm able to identify code or verbatim with regex
> including three catch groups for the content before, between and
> after the inline markers.
>
> for verbatim: "(^|[ .,;:\-?!({\"'])=(.*?)=([ .,;:\-?!)}\"']|$)"
> for code: "(^|[ .,;:\-?!({\"'])~(.*?)~([
* Anniversaries
%%(diary-anniversary 1948 01 30) Arthur's birthday (%d years old)
%%(diary-anniversary 2023-01-30) Arthur's birthday (%d years old)
<2023-01-30 Mon 15:53>
Just this. The last line is made by C-u-c .
To display the way my date are setted
If I press C a a
Emacs compose the agenda
Max Nikulin writes:
To summarize, I believe that a browser extension is a safer way to use
> org-protocol. With a native messaging helper application it is even
> possible to avoid desktop-wide org-protocol configuration and to call
> emacsclient directly by the add-on but not through links o
Hello Renato,
Renato Pontefice :
> * Anniversaries
> %%(diary-anniversary 1948 01 30) Arthur's birthday (%d years old)
>
> %%(diary-anniversary 2023-01-30) Arthur's birthday (%d years old)
>
> <2023-01-30 Mon 15:53>
> Just this. The last line is made by C-u-c .
> To display the way my date are s
Ihor,
> That's all nice but what a headache will it be to implement. What will
> 2004-06~ mean for agenda, for example?
i don't know the specific "2004-06~", but i do think that for the agenda
(i assume), being able to express ambiguity to the user will be
important. as people have pointed out (
Greg Minshall writes:
> i guess the third is what "2004-06~" might mean (i visualize, in
> amusement, a very light pink background over all of June, with some
> decay function coming earlier into May, later into July :).
Maybe. But my point states - it is not trivial thing to implement.
For cont
Ihor, makes sense. that we probably need to *display* imprecision
doesn't mean we need to accept/parse it.
Hi!
Andreas Gerler writes:
> I added the missing changelog entry.
Thanks.
I installed the patch.
(I'll also answer to your dbconnection engine mail soon.
Just very busy atm)
Thanks,
Daniel
Pushed the change to `org-babel-eval'.
Renato Pontefice writes:
> * Anniversaries
> %%(diary-anniversary 1948 01 30) Arthur's birthday (%d years old)
>
> %%(diary-anniversary 2023-01-30) Arthur's birthday (%d years old)
>
> <2023-01-30 Mon 15:53>
> Just this. The last line is made by C-u-c .
> To display the way my date are setted
>
Jakob Schöttl writes:
> I got a patch for
>
> https://orgmode.org/worg/org-tools/index.html
>
> Does someone with access wants to apply it?
Thanks for the patch, but I am unable to apply it.
May you follow https://orgmode.org/worg/org-contribute.html#org045e318 ?
--
Ihor Radchenko // yantar92,
Greg Minshall writes:
>> 1. If compat.el happens to lack support of some function, we will need
>>to contribute to compat.el directly and synchronize Org releases with
>>compat.el releases.
>
> would a separate "org-compat.el" (in addition to compat.el) somehow
> solve this? (i worry abo
Ihor,
> >> 1. If compat.el happens to lack support of some function, we will need
> >>to contribute to compat.el directly and synchronize Org releases with
> >>compat.el releases.
> >
> > would a separate "org-compat.el" (in addition to compat.el) somehow
> > solve this? (i worry about th
* Max Nikulin [2023-01-29 09:33]:
> On 29/01/2023 11:09, Jean Louis wrote:
> > * Tim Cross [2023-01-28 00:15]:
> > > > > • Offset (fixed)
> > > > >• This captures the idea of "when did it happen for the person who
> ^^^
> Jean, you missed it.
* Max Nikulin [2023-01-29 09:33]:
> On 29/01/2023 11:09, Jean Louis wrote:
> > * Tim Cross [2023-01-28 00:15]:
> > > > > • Offset (fixed)
> > > > >• This captures the idea of "when did it happen for the person who
> ^^^
> Jean, you missed it.
Dear Thomas,
I give my best to find references for you and explain you the possible
problem in calculation of time stamps. That problems exist is clear.
To solve problem it is important to first define it. And when there
are developers reading it, I wish to provide best possible references
for th
* Tim Cross [2023-01-29 23:38]:
> Yes, a timezone is defined by the offset it has from UTC
Other way around Tim, the UTC offset is defined for the time zone.
Time zone is not derived fro UTC offset, that does not work. UTC
offset is derived from time zone.
> Yes, a location time zone may change
On 1/30/23 20:40, Greg Minshall wrote:
> i see, yes. i'm just thinking that, for a given release CUR (like i
> know anything about org-mode release procedures!) we would use whatever
> has been available in compat.el since release CUR-n (for whatever n we
> use -- 2?), and supplement that, in org
Hi Ihor,
* Ihor Radchenko wrote:
> Karl Voit writes:
>
>>> What is the return value of
>>>
>>> (epg-list-keys (epg-make-context nil t t) org-crypt-key)
>>>
>>> ?
>>>
>>> Does it show the right key?
>>
>> It shows:
>>
>> (#s(epg-key ultimate
>> (#s(epg-sub-key ultimate ... nil 1 4096
Jean Louis writes:
> * Tim Cross [2023-01-29 23:38]:
>> Saying that an offset is a fixed value is very different from saying
>> that a time zone has a fixed offset. I think this is where your
>> confusion is coming from.
>
> I said neither of those. I never said that UTC offset is fixed. I am
>
In short, you cannot nest code in verbatim or verbatim in code
because they are both terminal (end of the line for nesting).
In fact you can't nest anything inside them by their very nature.
Anything inside of them cannot have special functionality, even
escape codes don't play well in that part o
Aloha Jean Louis,
Jean Louis writes:
Dear Thomas,
I give my best to find references for you and explain you the
possible
problem in calculation of time stamps. That problems exist is
clear.
To solve problem it is important to first define it. And when
there
are developers reading it, I w
unable to follow this but it sounds like a big deal and i am glad that
you are looking into it. thanks.
[my use case fwiw:
1] it is disruptive for me having org-capture not work [i do not alwys use kb].
2] x-wide capture using emacsclient would presumably not contain the
page title in firefox.
3]
* Tim Cross [2023-01-31 01:05]:
> Jean,
>
> you have a very irritating habit of changing the topic of the discussion
> in order to push whatever you feel you want to argue about. My response
> to you had nothing to do with all the irrelevant points you insist on
> repeating despite numerous attem
Dear Heinz,
Thanks, let me see.
* Heinz Tuechler [2023-01-31 01:02]:
> Dear Jean Louis,
>
> it appears to me that you mix two aspects. I agree with you that a time
> zone needs an offset from UTC to be defined. Consequently the definition
> of a time zone requires an offset.
Yes, that is good
Hi,
I have been replacing to calls to =custom-set-variables= with calls to
the safer
=setopt= (new in Emacs-29.0.60) and I discovered that calling
src_emacs-lisp{(setopt org-babel-load-languages '((eshell t) (emacs-lisp
t)))}
raises a warning because =eshell= is missing from the
=org-babel-lo
39 matches
Mail list logo
