"Tom Davey" writes:
> Hi Tim,
>
> Thanks for these thoughtful comments. I agree that the Org developers (to
> whom I, as a mere user, owe enormous thanks) must be wary before making
> changes to how timestamps are handled.
>
> This argues, I would say, for keeping what I believe was the statu
On 3/22/22, Ihor Radchenko wrote:
> lax - agenda may match anything date-looking (with or without brackets).
> A specialized regex agenda matcher with regex constructed using current
> agenda date.
>
> Maybe we can introduce a new agenda view? Or maybe a special agenda
> mode, similar to org-agend
Hello Rudy!
On 3/22/22 21:51, Rudolf Adamkovič wrote:
Zelphir Kaltstahl writes:
Hello Zelphir!
At some point something changed, I think, […]
In Geiser or in Org? I use Geiser for work heavily and it works like
magic. I ask because if the problem resides in Geiser, we could report
a new bu
Hello,
Max Nikulin writes:
> Nicolas, I think, a part of problem is that you are not an org-cite
> user. The packages require some *polishing*, but it have to be
> *user-driven*.
Just to be clear: the development was _user-driven_ from the start.
I read years of discussions about citation, sug
Hi Tim,
Thanks for these thoughtful comments. I agree that the Org developers (to
whom I, as a mere user, owe enormous thanks) must be wary before making
changes to how timestamps are handled.
This argues, I would say, for keeping what I believe was the status quo
since at least Org version 9.4
Hello,
Ihor Radchenko writes:
> So, depending on the current command, Org may on may not treat objects
> matching org-ts-regexp-both as timestamps.
>
> This situation complicates syntax and makes org-element unreliable when
> dealing with Org buffers.
This is orthogonal to syntax. I think the d
Ihor Radchenko writes:
> Ihor Radchenko writes:
>
>> After further reading the source code, I figured that agenda is, in
>> fact, supposed to handle timestamps inside property drawers. Optional
>> arguments for org-at-timestamp-p imply that, in agenda specifically,
>> timestamps inside node pr
Ihor Radchenko writes:
> Samuel Wales writes:
>
>> so i guess i am interested in the rationale. example of ts [and text]
>> search being useful might be an example or ledger block that contains
>> ledger source, or something like that. i can get why bare ts not
>> being matched inside links
Zelphir Kaltstahl writes:
Hello Zelphir!
> At some point something changed, I think, […]
In Geiser or in Org? I use Geiser for work heavily and it works like
magic. I ask because if the problem resides in Geiser, we could report
a new bug there.
Rudy
--
"One can begin to reason only when a
Ihor Radchenko writes:
> We can auto-magically determine whether to use BEGIN_ or begin_
> depending on the case in template type. Tentative patch attached.
Interesting!
> +with \"#+begin_\" and \"#+end_\" added automatically. If the block
> +type is written using upper case letter, \"#+BEGIN_
On Tue, Mar 22, 2022 at 10:42 AM Max Nikulin wrote:
>
> On 21/03/2022 22:19, Bruce D'Arcus wrote:
> > On Mon, Mar 21, 2022 at 10:41 AM Max Nikulin wrote:
> >
> >> A bit of routine work will alleviate some user issues:
> >> - add missed styles
> >
> > The initial list of style-command mappings was
Hello,
On Di, Mär 22 2022 at 20:27:27 +0800, Ihor Radchenko
wrote:
To clarify, org-cite must detect changes in your .bib file and if a
citation record key in the .bib files was changed, trying to insert it
should trigger org-cite to mark the new citation in red. Regardless if
the citation get
On 19 March 2022 11:25, Juan Manuel Macías wrote:
> #+begin_src emacs-lisp
> (defun my-org-rename-link-file-at-point ()
> (interactive)
> (let* ((curr-dir (if (equal (org-element-property :type
> (org-element-context)) "attachment")
>(concat (abbreviate-file-nam
On 21/03/2022 22:19, Bruce D'Arcus wrote:
On Mon, Mar 21, 2022 at 10:41 AM Max Nikulin wrote:
A bit of routine work will alleviate some user issues:
- add missed styles
The initial list of style-command mappings was pretty comprehensive,
but we left out some of the more obscure biblatex comma
Hi Juh,
juh writes:
> [[PGP Signed Part:Undecided]]
> Am Sun, Mar 20, 2022 at 08:31:29PM -0400 schrieb John Kitchin:
>> For those who need high fidelity LaTeX export like I do, I think
>> org-ref is still a superior solution. For everyone else, and
>> especially if you do not need sophisticated
Hello,
I think `org-complex-heading-regexp' and
`org-complex-heading-regexp-format' should consider COMMENT keywords, as
they do with TODO keywords, priorities, and tags.
Firstly, with things as they are, different methods for accessing the
headline text are inconsistent. For example, for the he
psychosis writes:
>> I assume that your bibliography is much larger than 10Mb. Am I
>> correct?
>
> Actually, it is only 2Mb (7000 entries). Probably there is a problem
> with the data structure of my .bib-file? I create it from Zotero and
> the BibLaTeX-export of the BetterBibTeX-Plugin.
> *
Samuel Wales writes:
> so i guess i am interested in the rationale. example of ts [and text]
> search being useful might be an example or ledger block that contains
> ledger source, or something like that. i can get why bare ts not
> being matched inside links might be useful.
>
> otoh i can ge
Samuel Wales writes:
> - not quite grasp why bare active and inactive tses should not be
> matched by ts agenda almost anywhere including blocks. perhaps the
> idea is that you might wnt to store lots of data with tses and they
> would be too much clutter?
See
https://orgmode.org/list/202201011
Ihor Radchenko writes:
> After further reading the source code, I figured that agenda is, in
> fact, supposed to handle timestamps inside property drawers. Optional
> arguments for org-at-timestamp-p imply that, in agenda specifically,
> timestamps inside node properties are considered timestamps
Ignacio Casso writes:
>>> What you see in the new Org version is not a bug. Property values are
>>> treated as plain text by Org.
>
> I think that even if timestamps were never intended to be used inside
> property drawers before, the fact that it worked for a long time and
> nothing in the docum
21 matches
Mail list logo
