On Wed, Nov 3, 2021 at 7:43 AM Ihor Radchenko wrote:
>
> Aaron Jensen writes:
>
> > Here is a backtrace. The package it mentions is my own:
> > https://github.com/aaronjensen/emacs-orgonomic and
> > https://github.com/Somelauw/evil-org-mode is mentioned too.
>
> The mentions are ok. Backtrace
Glad I could be of assistance!
--
: Eric S Fraga via Emacs 28.0.60, Org release_9.5-192-gd4e192
: Latest paper written in org: https://arxiv.org/abs/2106.05096
Greg Coladonato writes:
> I uninstalled undo-fu and re-ran the profiler. It takes even longer to save
> org files now. Here's the profiler report now, does it look like helm-M-x
> is
> now the bottleneck?
The profiler does not show anything about saving buffer. I suspect that
you had profiler
Aaron Jensen writes:
> Here is a backtrace. The package it mentions is my own:
> https://github.com/aaronjensen/emacs-orgonomic and
> https://github.com/Somelauw/evil-org-mode is mentioned too.
The mentions are ok. Backtrace should mention every command that
actually changes the buffer.
>
Aaron Jensen writes:
> Here is another that just happened:
> https://gist.github.com/aaronjensen/5294a64f243a306b58062113b9306bab
>
> It's scrubbed of all string data, hopefully not over-scrubbed for you.
Thanks! It was really helpful. The problem was org-roam calling
org-element-parse-buffer
Greg Minshall writes:
> my thought about flycheck, flymake, whatever, is that (optionally) a
> silent, background, =tangle= and/or =<> expansion= would take
> place to produce a "full source file buffer"[*], then the narrowed
> version of that (corresponding to the part where =C-c '= was issued)
Ihor,
thanks for the clarification.
maybe, in that ideal world, <> might expand, optionally.
another point: watching Noboru's "most recent" (9?) video, i see another
feature of his transclusion: a way to say, "this is *exactly* like a
source block -- with language, :results, :tangle, :var,
Hello,
Emmanuel Charpentier writes:
> This (minuscule) patch allows to pass a relative (to the buffer's
> default directory) file name to denote the CSL style file.
Thank you. However, I'm not sure to understand the purpose of the patch.
> Rationale : this allows the use of "one-of" styles
I have this in an org file
0,Mon [start_plus_0] at 03:00 PM
30,Mon [start_plus_0] at 03:30 PM
60,Mon [start_plus_0] at 04:00 PM
90,Mon [start_plus_0] at 04:30 PM
120,Mon [start_plus_0] at 05:00 PM
I want to export to ASCII text and have it look exactly like that, 5 lines.
Doing nothing, I get 3
In a basically vanilla emacs, if I have a target like <> with my
point on it, and I run org-store-link (via C-c l), and then somewhere else
do org-isnert-link (via C-c C-l) I get a link like
[[file:~/s/f.org::test]]
If I define a link now like this:
#+BEGIN_SRC emacs-lisp
On 02/11/2021 17:55, Ihor Radchenko wrote:
Max Nikulin writes:
Ihor, your fix affects linux as well. .cache directory may be missed in
fresh accounts. E.g. I just have created a new test container (my old
one has emacs-25):
After second thought, I am not sure anymore if using XDG is a good
Hi Nicolas,
Nicolas Goaziou writes:
> Thank you.
>
> Could you also document it in the manual?
Of course, tomorrow I will upload an updated version of the patch with
the documentation in the manual. Should I also add an entry in ORG-NEWS,
in "Version 9.6" node?
Best regards,
Juan Manuel
Hello,
"Bruce D'Arcus" writes:
> Can you please fix that, if the patchis otherwise fine?
OK.
> The biblatex manual (section 2.3.8 Date and Time Specifications), says
> the following:
>
> "Date fields such as the default data model dates date, origdate,
> eventdate, and urldate adhere to
Hello,
Marvin Gülker writes:
> trying to export the following org-document results in an Elisp error:
>
> #+TITLE: Test
> #+AUTHOR: Testauthor
>
> #+LANGUAGE: de
> #+bibliography: /tmp/mwe/mwe.bib
>
> #+cite_export: csl /tmp/mwe/juristische-schulung.csl
>
> Test
On Wed, Nov 3, 2021 at 12:21 PM Nicolas Goaziou wrote:
> oc-basic relies on a cache. The cache key contains a hash of the
> contents of the bib file. So whenever the bib file is modified, the
> cache is invalidated, and oc-basic parses again the file.
Of course; clever!
Bruce
I believe my confusion was due to the fact that the docstring of
org-startup-folded is not particularly precise regarding to its
possible values. On the one hand it seems to be a toggle, but its
initial value is nevertheless showeverything and not t. On the other
hand it states that "This can also
Hello,
Sébastien Miquel writes:
> Subject: [PATCH] org.el (org-display-inline-image--width): Small fix
I expounded the commit message and applied your patch. Thank you.
Regards,
--
Nicolas Goaziou
Hello,
"Bruce D'Arcus" writes:
> On Thu, Oct 21, 2021 at 10:12 AM Eric S Fraga wrote:
>>
>> Dear all,
>>
>> simple question: how can I get org-cite to rescan my bibliography (.bib)
>> file when it changes? When I'm writing a paper, as I'm doing now, I add
>> entries to my bibliography as I
Hello,
Juan Manuel Macías writes:
> The `:options' attr. allows adding an optional argument with various
> table options (between brackets in LaTeX export), since certain tabular
> environments, such as `longtblr' of the `tabularray' LaTeX package,
> provides this structure (see:
>
Hi,
stardiviner writes:
> I would like to be the maintainer of org-contacts.el. (I might
> already replied this message? Sorry if duplicated.)
You are already org-contacts.org's maintainer:
https://git.sr.ht/~bzg/org-contrib/tree/master/item/lisp/org-contacts.el#L6
> I have separated and put
Juan Manuel Macías writes:
> Of course, tomorrow I will upload an updated version of the patch with
> the documentation in the manual. Should I also add an entry in ORG-NEWS,
> in "Version 9.6" node?
Good idea. Thanks.
Regards,
Hi,
With point at the bol of the empty line after the keyword and before
the heading at the end of this mail, =org-element-at-point= returns
the headline element. It used to (a month ago, before all the caching)
return the keyword.
This breaks =org-element-context= which errors out when called
"Christopher W. Ryan" writes:
> I have this in an org file
>
> 0,Mon [start_plus_0] at 03:00 PM
> 30,Mon [start_plus_0] at 03:30 PM
> 60,Mon [start_plus_0] at 04:00 PM
> 90,Mon [start_plus_0] at 04:30 PM
> 120,Mon [start_plus_0] at 05:00 PM
>
> I want to export to ASCII text and have it look
idk if this is useful, but i was thinking of doing something similar,
except, automatically for the purpose of recording progress.
as in, the number of times i did something to the task. in tags not
properties, thus on the header. like :n_2:
i tried keywords for progress instead, but that is
On Wed, Nov 3, 2021 at 10:30 AM Aaron Jensen wrote:
>
> On Wed, Nov 3, 2021 at 7:43 AM Ihor Radchenko wrote:
> >
> > Aaron Jensen writes:
> >
> > > Here is a backtrace. The package it mentions is my own:
> > > https://github.com/aaronjensen/emacs-orgonomic and
> > >
hi.
i'm wondering if anyone programming in typescript might have run into,
and solved, this "problem", of tangling into a subdirectory, and tide
[1] not being able to resolve "relative" imports.
i have a file in path /a/b/foo.org. it includes various source blocks,
and they do things like
How to use elisp code to generate an org-agenda view for clocked tasks and
logs etc which are sorted by timestamps? I want to view my daily done tasks
and attach them as part of diary (maybe use org source block elisp code to
generate output?)
So how to setup `org-agenda-custom-commands` to
On Wednesday, 3 Nov 2021 at 06:43, Colin Baxter wrote:
> I have this
>
> #+begin_src elisp
> &%%(org-diary :deadline* :timestamp :scheduled*)
> #+end_src
I cannot help you directly but I do note that my equivalent entry in my
Emacs diary file is subtly different:
%%(org-diary :scheduled
> Eric S Fraga writes:
> On Wednesday, 3 Nov 2021 at 06:43, Colin Baxter wrote:
>> I have this
>>
>> #+begin_src elisp &%%(org-diary :deadline* :timestamp
>> :scheduled*) #+end_src
> I cannot help you directly but I do note that my equivalent entry
> in my
Hello,
I have this
#+begin_src elisp
&%%(org-diary :deadline* :timestamp :scheduled*)
#+end_src
at line 9 in my main diary file ~/.emacs.d/diary/main. It worked well up
until recently (a week or so, I think). Now I get the following warning:
--8<---cut
>>> "ESF" == Eric S Fraga writes:
> On Monday, 1 Nov 2021 at 20:53, Uwe Brauer wrote:
>> (format "%s" (- 1 (string-to-number
> Shouldn't this be the other way around, i.e.
> (- (string-to-number ...) 1)
> ?
Oops you are right, thanks
smime.p7s
Description: S/MIME cryptographic signature
Ihor,
(Noboru Ota -- i do find transclusion very interesting.)
> 2. A much faster tangle system. If we can directly transclude and sync
>contents of source blocks with actual programming language buffer,
>C-c ' can trivially support flycheck-mode and provide a more
>IDE-like
32 matches
Mail list logo
