Ihor writes:
> * headline
> :PROPERTIES:
> :ATTR_BACKEND: :export_template "\begin{myenv}\n%s\n\end{myenv}"
> :ATTR_BACKEND+: "The %%s instances are replaced by the exported element"
> :ATTR_BACKEND+: (concat "arbitrary sexp, the exported element is bound
to: " *this*)
> :ATTR_BACKEND+:
andrés ramírez writes:
> Ihor> Also, can you do 1. M-x trace-function org-diary-sexp-entry
> 2. refresh the
> Ihor> agenda 3. share the trace output 4. M-x untrace-all
Now, I see what went wrong.
Just pushed a patch that should reduce the time taken by
`org-diary-sexp-entry' during
andrés ramírez writes:
> A few seconds ago. I have done git pull; make.
>
> This is my latest file
Thanks!
This is strange.
Can you please check the value of org--diary-sexp-entry-cache?
Also, can you do
1. M-x trace-function org-diary-sexp-entry
2. refresh the agenda
3. share the trace
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> Thanks!
Ihor> Something appears to be off:
Ihor> 767 8% - org-diary-sexp-entry 407 4% + eval
Ihor> I added caching of `org-diary-sexp-entry' results in
Ihor>
andrés ramírez writes:
> Ihor> cpu+mem report should generate two reports: one for cpu time and
> one for memory. I meant
> Ihor> you to save both (there are two buffers). Sorry for not being clear.
>
> The two files on an archive
Thanks!
Something appears to be off:
767
Ihor Radchenko writes:
> Tim Cross writes:
>
>> One thing I do find frustrating these days is the fracturing of
>> communications across so many different solutions. Makes me really miss
>> newsgroups! It seems like almost every project I'm interested in these
>> days is using a different
Tim Cross writes:
> +1. As usual, I'm concerned about over engineering and over
> complicating matters for corner cases. As you correctly point out,
> implementing something here is likely to force a specific interpretation
> of cancelled with may not fit with other interpretations.
For
Bastien writes:
> Would it be okay to
>
> 1. replace both "report bug" and "feedback" buttons by a "feedback"
>button, pointing to manual https://orgmode.org/manual/Feedback.html ?
I feel like it is good idea to keep both "report bug" and "feedback"
buttons, even if they point to the same
Tim Cross writes:
> One thing I do find frustrating these days is the fracturing of
> communications across so many different solutions. Makes me really miss
> newsgroups! It seems like almost every project I'm interested in these
> days is using a different solution for IM. (one reason I
Bastien writes:
> But IMO there is an even stronger argument: in the case of Org, we
> should encourage discussions where both "users" and "developers" can
> chime in. Because many Org users are potential contributors. (This
> would not be the same with another Free Software project, of
Max Nikulin writes:
> Since `org-confirm-babel-evaluate' may be customized to a function,
> every participant of this thread may implement their preferred policies
> with no modification of Org code or even an advice to the default
> function.
Not that easy.
`org-confirm-babel-evaluate' only
Timothy writes:
> Hi Ihor,
>
>>> - (message “executing %s code block%s…”
>>> + (message “executing %s %s %s…”
>>> (capitalize lang)
>>> + (pcase (org-element-type (org-element-at-point))
>>> + (’src-block “code block”)
>>> +
Max Nikulin writes:
> While I work with my notes file, performance degrades after some
> operations. E.g. searches become significantly slower after caching
> refile targets. Previous discussion of the issue:
> Ihor Radchenko. Re: profiling latency in large org-mode buffers (under
> both main
Hi,
I noticed that https://orgmode.org/, https://orgmode.org/fr/index.html,
and https://orgmode.org/ja/index.html are not consistent.
In particular, the new badges are not shown in non-English versions.
Further, French version has a different Org syntax example.
Other parts of text present in
Daniel Ortmann writes:
> Was Eli Z's observation the key? Of code not autoloading when
> eval-buffer is running?
Yes, it is.
Bastien,
In f36b19eef, you introduced the following code into org.el:
(or (eq this-command 'eval-buffer)
(condition-case nil
(load (concat
Ken Mankoff writes:
> #+BEGIN_SRC plantuml :noweb yes :file cache-yes.png
> @startjson
> <>
> @endjson
> #+END_SRC
>
> #+RESULTS:
> [[file:cache-yes.png]]
>
> The above graphic is an error message. It states,
>
> "Your data does not sound like JSON data".
I tried your example it is working just
Thank you for the fix!
Joseph
Bastien Guerry writes:
> Ihor Radchenko writes:
>
>> Bastien, there seems to be an issue with Worg export on server. Can you
>> please check?
>
> This is now fixed, thanks:
>
> https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e
Bastien writes:
> Daniel Fleischer writes:
>
>> At first it makes sense, but we do have headlines and TODO keywords to
>> express different states, colors and even sets of states. This is just a
>> checklist construct. I think if I wanted to mark something as canceled
>> or not relevant I
Bastien writes:
> Hi Ihor,
>
> Ihor Radchenko writes:
>
>> This is an option. #emacs is very too noisy for me, but #org-mode
>> appears to be fairly quiet. It may work.
>
> I agree with Russell that we should first use the available resources,
> and our IRC chan on irc.libera.chat is a good
Max Nikulin writes:
> On 22/09/2022 19:46, Tyler Grinn wrote:
>> Ihor Radchenko writes:
>>
>>> Why don't just modify :activate-func in the ordinary file links?
>> I like this idea, in fact so much I got rid of the todo style
>> link. But
>> one thing that's still problematic is that I'd like
>>> One other possibility is to use a slightly different :relative-width
>>> factor for the two spaces in a table cell: one with the value of 1,
>>> the other with 1.001 (say). They will be indistinguishable on
>>> display, but since the values are not equal, both stretch gfyphs will
>>> be
Was Eli Z's observation the key? Of code not autoloading when
eval-buffer is running?
On 9/21/22 03:37, Ihor Radchenko wrote:
Daniel Ortmann writes:
These two lines are in my *Messages* buffer:
File mode specification error: (void-function org-element-cache-reset)
Error during redisplay:
Hi Max,
Max Nikulin writes:
> The updated page has
>
> alt="Install from ELPA"
>
> that likely should be "Install from GNU ELPA".
Fixed, thanks.
> I like that new link
> leads directly to the Org package at GNU ELPA, earlier version had a
> link to the site top page.
+1!
> However
> "B" == Bastien writes:
B> FWIW, I use this:
B> - [X] +This task will probably be canceled+
B> I don't think we should implement a new status for canceled
B> tasks.
Such a workaround doesn’t work well for lists that are to be re-used
next time or cleared when the whole
On 22/09/2022 21:20, Sterling Hooten wrote:
When trying to insert a stored 'id' link with org-insert-link the
candidates are just the 'id' numbers themselves. This doesn't help
when trying to determine what the 'id' actually points to. Is there a
way for org-insert-link to display headings or
Hi Ika,
Timothy writes:
> Thanks for getting in touch! The basics of mailing-list developments is just
> using an email chain issues of issues/PRs, and submitting changes as git patch
> attachments — that’s all there really is to it
... and you can read
Hi Ihor,
Ihor Radchenko writes:
> This is an option. #emacs is very too noisy for me, but #org-mode
> appears to be fairly quiet. It may work.
I agree with Russell that we should first use the available resources,
and our IRC chan on irc.libera.chat is a good one.
(I'm actually there BTW,
Ihor Radchenko writes:
> Bastien, there seems to be an issue with Worg export on server. Can you
> please check?
This is now fixed, thanks:
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e
--
Bastien
Ihor Radchenko writes:
> Ypo writes:
>
>> If we find a typo, how should it be reported?
You can send a patch to the mailing list.
When editing the documentation from within Emacs, `C-x v =' will
create a buffer with the diff that you can simply inline to your
email, that's easier to read for
Hi Ihor,
Ihor Radchenko writes:
> Bastien writes:
>
>>> Also, having an actual mirror in sr.ht means that we may set up automatic
>>> tests. WDYT about this idea?
>>
>> Tests are useful if they prevent contributors from changing the code
>> in a way that break them: this must happen before
On 20/09/2022 12:41, Timothy wrote:
Hi Bastien,
The whole top banner has become a bit messy, IMO. I’ll have a go at cleaning it
up later today. See Matrix for a preview I put together by just editing the
in-browser HTML. Also let me know if you don’t use Matrix at all, I just thought
I’d send
Hi Timothy,
Timothy writes:
> The whole top banner has become a bit messy, IMO. I’ll have a go at cleaning
> it
> up later today. See Matrix for a preview I put together by just editing the
> in-browser HTML. Also let me know if you don’t use Matrix at all, I just
> thought
Thank you for the
Hi Angel,
Angel de Vicente writes:
> As per the example I was giving, I don't want that entry to be scheduled
> for October 16 (and thus clutter my agenda view), I just want it to be
> visible in my Global TODO list from that date, so then, depending on how
> busy I'm around that date, then I
On 22/09/2022 19:18, Ihor Radchenko wrote:
Joseph Turner writes:
Actually, I just looked at the org-mode documentation on the site today,
and noticed that the examples of use section
(https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e)
has the wrong ASCII
Daniel Fleischer writes:
> At first it makes sense, but we do have headlines and TODO keywords to
> express different states, colors and even sets of states. This is just a
> checklist construct. I think if I wanted to mark something as canceled
> or not relevant I would do something like this:
Russell Adams writes:
> The #org-mode channel has a large footprint already, though lower
> utilization than #emacs. There are 230 org users online right now.
>
> It would be great to see some dev discussions on IRC, and if we ever
> get too much traffic, maybe make a #org-mode-dev channel.
>
>
On 22/09/2022 03:56, Rudolf Adamkovič wrote:
Greg Minshall writes:
i'm a bit unclear. does your (single?) Org notebook consist of *one*
file (and thus, [normally? always? my ignorance precedes me], one
buffer), or two files (thus, two buffers).
One file, two kinds of "src" blocks.
in the
Daniel Fleischer writes:
> If org-latex-classes is not a good enough solution I also think it should
> be a general export feature, not specific to latex. In that case you
> need a general syntax, e.g. properties like "export_prefix",
> "export_postfix" and the code should be as simple as
On 22/09/2022 19:46, Tyler Grinn wrote:
Ihor Radchenko writes:
Why don't just modify :activate-func in the ordinary file links?
I like this idea, in fact so much I got rid of the todo style link. But
one thing that's still problematic is that I'd like org-todo-link-mode
to be a local mode
"Fraga, Eric" writes:
> This looks fine to me. I don't particularly care about the actual
> syntax. However, a minor point out of curiosity: why not just ":latex:"
> for the property name?
Because attr_backend is our convention for export attributes.
> And I would hope to have ":beamer:" (or
Hi,
When trying to insert a stored 'id' link with org-insert-link the
candidates are just the 'id' numbers themselves. This doesn't help
when trying to determine what the 'id' actually points to. Is there a
way for org-insert-link to display headings or other information
(maybe the tags or other
Juan Manuel Macías writes:
>> I suggest to use more canonical attr_latex that explicitly limits the
>> export backend.
>
> I see. But in any case, something like `:prepend "section"' would be
> unnecessary (and even counterproductive) for what I'm proposing, but I'm
> afraid I didn't explain
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
Ihor> cpu+mem report should generate two reports: one for cpu time and one
for memory. I meant
Ihor> you to save both (there are two buffers). Sorry for not being clear.
The two files on an archive
<>
Best Regards
Ihor Radchenko writes:
I've moved the project to gitlab:
https://gitlab.com/tygrdev/org-todo-link
> Why don't just modify :activate-func in the ordinary file links?
I like this idea, in fact so much I got rid of the todo style link. But
one thing that's still problematic is that I'd like
On 22/09/2022 14:03, Timothy wrote:
On 18/09/2022 10:09, Timothy wrote:
and now this might look like so:
┌
│ executing Emacs-Lisp call on line 143…
│ Code block evaluation complete (took 0.2s).
└
I do not mind to have such feature, but I am unsure concerning its price. I just
have
> From: Ihor Radchenko
> Cc: homeros.mis...@gmail.com, t...@misasa.okayama-u.ac.jp,
> 45...@debbugs.gnu.org, emacs-orgmode@gnu.org
> Date: Thu, 22 Sep 2022 20:03:55 +0800
>
> Eli Zaretskii writes:
>
> > One other possibility is to use a slightly different :relative-width
> > factor for the
Joseph Turner writes:
> Actually, I just looked at the org-mode documentation on the site today,
> and noticed that the examples of use section
> (https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-plantuml.html#org6cd541e)
> has the wrong ASCII output. The output should be
>
>
Eli Zaretskii writes:
>> I don't think this is the right solution. One possible solution that
>> is better is to bind to an org-table specific command, which
>> would insert some character displayed as a thin space between the two
>> spaces that have the 'display' property. But I'll let Ihor
Hi Ihor,
>> -(message “executing %s code block%s…”
>> +(message “executing %s %s %s…”
>> (capitalize lang)
>> + (pcase (org-element-type (org-element-at-point))
>> + (’src-block “code block”)
>> +
Hi Max,
> On 18/09/2022 10:09, Timothy wrote:
>> and now this might look like so:
>> ┌
>> │ executing Emacs-Lisp call on line 143…
>> │ Code block evaluation complete (took 0.2s).
>> └
>
> I do not mind to have such feature, but I am unsure concerning its price. I
> just
> have tried
>
>
Hi Ihor,
>> +(defcustom org-babel-tangle-finished-hook nil
>
> I’d also mention the active buffer when the hook is ran. (And also add
> the relevant info to org-babel-pre-tangle-hook docstring)
Done.
>> +- `org-babel-tangle-finished-hook' ::
>> + #+vindex: org-babel-tangle-finished-hook
>>
Hi Ika,
> There seems to be a typo in the Org Manual.
>
> In section 13.8.4: Beamer specific syntax, in the segment showed below,
> The `#+END_BEAMER’ part does neither run correctly nor makes sense,
> The correct code here should be `#+END_EXPORT’.
Thanks for pointing that out, I’ve just pushed
Ihor writes;
> More concretely, I mean something like
>
> * Section
> :PROPERTIES:
> :attr_latex: :prepend "section" \setcounter{secnumdepth}{0}
> :attr_latex+: :prepend "section"
\addtocontents{toc}{\protect\setcounter{tocdepth}{0}\ignorespaces}
> :attr_latex+: :append "section"
53 matches
Mail list logo
