> Uwe Brauer writes:
Uwe> Sorry, you misunderstood me, this time string, inserts the time string,
Uwe> when I execute the capture, but I want to extract the time string, when
Uwe> the message was received. This is why I used
Uwe> %:date
Uwe> in my first attempt, that works but inserts
Uwe> Tue,
I recall at least a few threads over the years that may be useful in
thinking about this issue. Here are the ones I quickly found again:
https://lists.gnu.org/archive/html/emacs-orgmode/2013-06/msg00221.html
https://lists.gnu.org/archive/html/emacs-orgmode/2017-02/msg00052.html
Josiah
Qqwy/Wiebe-Marten writes:
> With `org-list-allow-alphabetical` on, it is possible to use syntax like
>
> `a.`, `b.`, `c.` to create lists.
>
> However, the LaTeX that is exported will still create normal `enumerize`
> lists that do /not/ show up as alphabetical but rather still use `1.`,
> `2.`
I just heard about the note-taking tool Dendron, and am passing the link along
because it has similarities to Org. It's always worth seeing what related
projects are doing:
https://dendron.so/
"Dendron is an open-source, local-first, markdown-based, note-taking tool built
on top of VSCode. L
if you are willing to try something as a complete stab in the dark,
here is something i have had from many years ago that fixed issues
possibly including a defaulting issue. the issues include other stuff
too, but i do not understand the code now for health reasons to rule
this out as a solution t
trs> [smaller files] My agenda is not cluttered.
it is not clear to me why more smaller files and shallower trees in
the outline would improve the agenda. sounds good though.
tim> naming convention ... to determine what is included
this is also what i do. org-agenda-files is just set at startu
interesting. that would be great to speed it up. [i just meant that
the file list used to be correct.]
but it is slow these days. for me, (benchmark-run 1 (length
(org-refile-get-targets))) is 8s for 5886 targets.
i presume you mean something like that up heading is unnecessary
because you can
Uwe Brauer writes:
"RP" == Robert Pluim writes:
>
>>> On Thu, 04 Mar 2021 15:22:21 +0100, Uwe Brauer
> said:
>Uwe> Sorry, you misunderstood me, this time string, inserts the time
> string,
>Uwe> when I execute the capture, but I want to extract the time string,
> when
>>> "RP" == Robert Pluim writes:
>> On Thu, 04 Mar 2021 15:22:21 +0100, Uwe Brauer said:
Uwe> Sorry, you misunderstood me, this time string, inserts the time string,
Uwe> when I execute the capture, but I want to extract the time string, when
Uwe> the message was received. This i
TRS-80 writes:
> On 2021-03-03 16:59, Samuel Wales wrote:
> I have come to similar conclusion about "don't let org files get too
> big." Besides agenda speed, I think it is just easier to
> conceptualize things when each file covers only a limited scope, trees
> are more shallow, etc.
>
> So,
Carsten Dominik writes:
> On Fri, Feb 5, 2021 at 7:33 PM Eric Abrahamsen
> wrote:
>
>> Carsten Dominik writes:
>>
>> > On Fri, Feb 5, 2021 at 11:13 AM Christian Moe
>> wrote:
>> >
>> >>
>> >> Tim Cross writes:
>> >>
>> >> > Eric Abrahamsen writes:
>> >> >
>> >> >>> Does it actually need a key
On 2021-03-03 16:59, Samuel Wales wrote:
along lines of reducing logbook entries
I guess you must have picked up on my comment in another recent
thread. :)
i often want to reduce org
files, and i wonder if anybody already had the same desire.
here are some random ideas. my org files are so
> On Thu, 04 Mar 2021 15:22:21 +0100, Uwe Brauer said:
Uwe> Sorry, you misunderstood me, this time string, inserts the time string,
Uwe> when I execute the capture, but I want to extract the time string, when
Uwe> the message was received. This is why I used
Uwe> %:date
Uw
Dear org-mode community,
With `org-list-allow-alphabetical` on, it is possible to use syntax like
`a.`, `b.`, `c.` to create lists.
However, the LaTeX that is exported will still create normal `enumerize`
lists that do /not/ show up as alphabetical but rather still use `1.`,
`2.`, `3.` for numb
On 03/03/2021 00:15, Maxim Nikulin wrote:
There is one issue however. Default option option does not work if after
cache clean other command is called, e.g.
- jump using C-u C-c C-j
- clean cache C-u C-u C-u C-c C-w
- try to jump or to refile [C-u] C-c C-w to default offered option
- "user-err
>>> "AA" == Alberto AP writes:
Hi
> Hi
> What I use is the result of format-time-string (as explained in the Org
> Capture Templates help; check also the help for the format-time-string
> function).
> The string I use is:
> %<%Y%m%d-T%H%M%S>
> It
On 03/03/2021 09:34, Samuel Wales wrote:
until recently in maint, ido and ido hacks with both refile and refile
goto [note: org-refile with a goto arg, not org-goto] has worked
perfectly. with no cache. now, there is an issue, where with no
cache that i know of, the first use, or the first use
Hi
What I use is the result of format-time-string (as explained in the Org
Capture Templates help; check also the help for the format-time-string
function).
The string I use is:
%<%Y%m%d-T%H%M%S>
It gives me, for example, 20210304-T095526.
If you don't want the hour just remove "
Please see the attached updated patch with the changes requested.
Nick
On 3/4/21 12:25 AM, Kyle Meyer wrote:
Nick Savage writes:
Hi everyone,
See the attached patch. It is a small change to reduce code duplication
between ob-sql.el and ob-sqlite.el by reusing org-babel-sql-expand-vars
as sug
Hi
I try to add a new entry to my org-capture-templates
for mails what I read via gnus. I'd like to have a timestamp that
reflects when the message was received, not when the entry was created
(for that I would to have to use %t)
Now I have set
"| | %:fromname|%:fromaddress|%^{Sheet
> Kyle Meyer writes:
>> Stefan Monnier writes:
>>
>>> Since I'm not using it, I can't really test the result in any meaningful
>>> way. Furthermore, just like `calendar.el`, it relies on dynamic scoping
>>> and `eval` in all kinds of ways, so it's very difficult to be sure the
>>> result is "suffi
21 matches
Mail list logo
