Re: [Patch] Pre-/postpend arbitrary LaTeX code to a section
Ihor Radchenko writes: > What I have in mind is to modify `org-export-read-attribute' directly. > Then, we can call `org-export-read-attribute' in `org-export-data'; > resolve the refs in the template (re-use code from > `org-babel-ref-resolve' and `org-babel-parse-multiple-vars'); do normal > export and pass it to the template. Before running the normal export, we > strip :export_template from the INFO to avoid issues with ox-html which > puts every single attr into the generated html. OK, it makes sense. I can try something on this idea, although I'm afraid not in the short term. If someone else wants to do it I have no problem. Best regards, Juan Manuel -- -- -- Juan Manuel Macías https://juanmanuelmacias.com https://lunotipia.juanmanuelmacias.com https://gnutas.juanmanuelmacias.com
Re: org-assert-version considered harmful
Bastien writes: > Still, "Org mode version 9.6-pre (...)" is more accurate IMO. Ok. Pushed the patch + version change onto main. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c29d3e997d703f6bf14db559e351729cc25e4f26 https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=c8e0a402df91e168e1ec263a617b4cec6eb29e2d -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: org-assert-version considered harmful
Bastien writes: > Ihor Radchenko writes: > >> Then, I am inclined towards easing the version check to (org-version) >> instead of (org-git-version). > > FWIW strong +1 here. Done now. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=73f25bba8ffb9fe434486832c6acb98794dd2e69 Note that I used `org-release' macro. `org-version' would require loading 'org. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [BUG] Face attribute customization is ignored [9.5.5 (9.5.5-gbe2246 @ /home/dav/.emacs.d/straight/build/org/)]
On 25/09/22 04:29, Ihor Radchenko wrote: If you want to be really safe, try setting the :extend face property in org-font-lock-set-keywords-hook or in org-mode-hook. Yep, I was using org-mode-hook to be safe before filling this bug report. Thanks!
Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt/Cod
Matt Beshara writes: > ‘org-fill-paragraph’ does not correctly handle ^L characters > (a.k.a. form feed, C-q C-l). It should treat them as paragraph > separating whitespace, but instead treats them as any other > character which would appear in normal text. Here is an example > to demonstrate the current behaviour: > > abc def > ^L > ghi jkl This may or may not be a correct expectation. Please remember that Org mode is a markup language. ^L is not a part of Org specification for paragraph separators. According to https://orgmode.org/worg/dev/org-syntax.html#Paragraphs, paragraph boundaries should either be empty lines, or beginning of other Org elements. > In org-mode, with point at the beginning or the end of the first > or last line, doing ‘org-fill-paragraph’ (M-q) should do nothing, > because the lines are already shorter than the fill-column. What > really happens is that I end up with one line which looks like: > > abc def ^L def ghi Which is correct wrt current Org syntax specification, although I do agree that it is counter-intuitive. Dear all, Should we add page break (^L) to our syntax? It sounds like a reasonable addition for a text-based markup. > In text-mode, ‘fill-paragraph’ does handle ^L characters > correctly, and pressing M-q anywhere in the first example results > in no change being made to the buffer. Indeed. That's because text mode syntax is treated ^L specially. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Extract toc from org file
Hi list Is there a way to extract a toc from an org file e.g: #+INCLUDE: myfile.org :toc only I want to assemble the toc's from several files into one file and there seems to be no easy way to do this. Best, Reza OpenPGP_0xC375C6AF05125C52.asc Description: application/pgp-keys OpenPGP_signature Description: PGP signature
Re: [BUG] org-create-file-search-functions and description [9.5.5 (release_9.5.5 @ /usr/share/emacs/29.0.50/lisp/org/)]
Magnus Therning writes:
> The documenation on org-create-file-search-functions contains this
> piece of text
>
> A function in this hook may also use setq to set the variable
> description to provide a suggestion for the descriptive text to
> be used for this link when it gets inserted into an Org buffer
> with org-insert-link.
>
> This doesn't seem to be true though. I really would love for there
> to be a way to influence the link description, but no matter what
> the documentation should be corrected.
>
> For some more info look at
> https://www.reddit.com/r/orgmode/comments/xmvtsy/orgcreatefilesearchfunctions_and_description/
Thanks for reporting!
Confirmed.
This is a regression after we switched to lexical binding, and after we
removed the apparently uninitialized `description' variable from
let-binding in `org-store-link'.
a85b4cc5c64b1eb6b97f5d7843dd54eb0632ef91
Author: Stefan Monnier
AuthorDate: Thu Mar 11 13:07:37 2021 -0500
Commit: Kyle Meyer
CommitDate: Sun Mar 14 17:54:17 2021 -0400
Backport commit 7d0dc3183 from Emacs
...
* lisp/ol.el (org-store-link):
Remove always-nil variable `description`.
In order to make things work now with lexical binding, we need to create
a top-level defvar in ol.el, which is not nice since `description'
variable name is a bad name to define.
Interestingly, this issue has not been noticed for a long time and not
many users are probably making use of it.
Thus, we may as well take this opportunity and allow
`org-create-file-search-functions' to return a cons cell
("search term" . "description"). This will not require unintuitive
global variables.
WDYT?
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
Re: [BUG] org-create-file-search-functions and description [9.5.5 (release_9.5.5 @ /usr/share/emacs/29.0.50/lisp/org/)]
Ihor Radchenko writes:
Magnus Therning writes:
The documenation on org-create-file-search-functions contains
this
piece of text
A function in this hook may also use setq to set the variable
description to provide a suggestion for the descriptive text
to
be used for this link when it gets inserted into an Org
buffer
with org-insert-link.
This doesn't seem to be true though. I really would love for
there
to be a way to influence the link description, but no matter
what
the documentation should be corrected.
For some more info look at
https://www.reddit.com/r/orgmode/comments/xmvtsy/orgcreatefilesearchfunctions_and_description/
Thanks for reporting!
Confirmed.
This is a regression after we switched to lexical binding, and
after we
removed the apparently uninitialized `description' variable from
let-binding in `org-store-link'.
a85b4cc5c64b1eb6b97f5d7843dd54eb0632ef91
Author: Stefan Monnier
AuthorDate: Thu Mar 11 13:07:37 2021 -0500
Commit: Kyle Meyer
CommitDate: Sun Mar 14 17:54:17 2021 -0400
Backport commit 7d0dc3183 from Emacs
...
* lisp/ol.el (org-store-link):
Remove always-nil variable `description`.
In order to make things work now with lexical binding, we need
to create
a top-level defvar in ol.el, which is not nice since
`description'
variable name is a bad name to define.
Interestingly, this issue has not been noticed for a long time
and not
many users are probably making use of it.
Thus, we may as well take this opportunity and allow
`org-create-file-search-functions' to return a cons cell
("search term" . "description"). This will not require
unintuitive
global variables.
WDYT?
I think returning a cons cell would be a very nice solution.
/M
--
Magnus Therning OpenPGP: 0x927912051716CE39
email: mag...@therning.org
@magthe@mastodon.technology http://magnus.therning.org/
Never argue with stupid people, they will drag you down to their
level
and then beat you with experience.
― Mark Twain
signature.asc
Description: PGP signature
Re: [BUG] org-auto-repeat-maybe: error "Can’t expand minibuffer to full frame" and missing log note
Bhavin Gandhi writes: > I'm attaching the patch for the current approach we discussed in this > thread. I have tried basic operations like taking note on state change, > and have tried with recurring entries which need more than 10 cycles to > be marked as done (original bug report). > > As I was changing the indentation of code from org-add-log-note, I converted > some tabs to spaces, is it okay to do so? Thanks! Should be fine I think. We have a mess with spaces and tabs in some places. Applied onto main with amendments. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=2e012db31a8dbae0f859b8fbfc899aeed3e34244 I have changed the commit message to `quote' lisp symbols and have double space " " between sentences. I also added defvars for the new variables to pacify the compiler and changed the commit message accordingly. Applied Fixed -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: refresh not working for org-mode from git
Colin Baxter writes: > The solution is to use `make autoloads'. I suppose that should have been > obvious to me at the beginning. After git pull (`+' in vc-dir) the > working recipe is: FYI, the versions checks are less strict now to work around some Emacs limitations. See https://list.orgmode.org/orgmode/jwvczc05u7r.fsf-monnier+em...@gnu.org/ Though I'd still advice to run make autoloads && make if you can. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Syntax highlighting for julia source blocks
Hi list When exporting to html, syntax highlighting is automatically applied to exported python source blocks (syntax elements get a span element applied). But this does not work for julia source code blocks. Is this just not implemented or do I miss something? Cheers, Reza OpenPGP_0xC375C6AF05125C52.asc Description: application/pgp-keys OpenPGP_signature Description: PGP signature
Re: emacs really slow when inserting a new source code block
On Mon, Sep 26, 2022 at 6:41 AM Ihor Radchenko wrote: > Thanks for reporting! > May you > 1. M-x profiler-start cpu > 2. Move/paste/edit your source block > 3. M-x profiler-report > 4. M-x profiler-report-write-profile and share the resulting file here Apparently I'm not able to get the profiler report written. However, I discovered that, for instance, when I'm editing a piece of code with regexp Emacs seems to suffer, at least it is the only chances I had today to get it slower. The messages buffer does not help very much: CPU and memory profiler started End of ‘m/ ... /’ string/RE not found: (scan-error Unbalanced parentheses 74 82) Auto-saving...done CPU and memory profiler stopped profiler-write-profile: Wrong type argument: arrayp, nil As you can see, I cannot save the profiler report, neither by placing a filename, nor leaving it to save in the current directory of the file I'm editing. Oh, I also tried to disable flyspell, but it seems to me it gets re-enabled for the source code block I'm within (but it's just a feeling). Any idea? Luca
Re: Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt
^L is not a part of Org specification for paragraph separators. According to https://orgmode.org/worg/dev/org-syntax.html#Paragraphs, paragraph boundaries should either be empty lines, or beginning of other Org elements. Fair enough. If the consensus from others is that ^L should be recognised as a paragraph separator and the code is eventually written to make that work, that would be nice, but as it stands I can just start adding newlines after ^L. Thanks for your work on Org mode! Matt
Re: Extract toc from org file
On 26/09/2022 18:53, reza wrote: Is there a way to extract a toc from an org file e.g: #+INCLUDE: myfile.org :toc only I want to assemble the toc's from several files into one file and there seems to be no easy way to do this. Likely `org-element-map' allows to extract headings. There are should be some example in the mail list archive and at worg (hacks, perhaps in FAQ).
Re: emacs really slow when inserting a new source code block
Luca Ferrari writes: > On Mon, Sep 26, 2022 at 6:41 AM Ihor Radchenko wrote: >> Thanks for reporting! >> May you >> 1. M-x profiler-start cpu >> 2. Move/paste/edit your source block >> 3. M-x profiler-report >> 4. M-x profiler-report-write-profile and share the resulting file here > > Apparently I'm not able to get the profiler report written. > However, I discovered that, for instance, when I'm editing a piece of > code with regexp Emacs seems to suffer, at least it is the only > chances I had today to get it slower. > The messages buffer does not help very much: > > CPU and memory profiler started > End of ‘m/ ... /’ string/RE not found: (scan-error Unbalanced parentheses 74 > 82) > Auto-saving...done > CPU and memory profiler stopped > profiler-write-profile: Wrong type argument: arrayp, nil I think you tried to use M-x profiler-stop instead of M-x profiler-report M-x profiler-report show yield a new buffer displayed the profiler tree. M-x profiler-write-profile will work from inside that buffer. You can refer to https://cubeatic.com/index.php/s/iQakFWXgxsJzyXP (around 22:00) for a more detailed showcase. > Oh, I also tried to disable flyspell, but it seems to me it gets > re-enabled for the source code block I'm within (but it's just a > feeling). > > Any idea? Another thing you can try is setting org-src-fontify-natively to nil in your config. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Syntax highlighting for julia source blocks
On 9/26/22 17:15, Fraga, Eric wrote: > On Monday, 26 Sep 2022 at 14:09, reza wrote: >> When exporting to html, syntax highlighting is automatically applied to >> exported python source blocks (syntax elements get a span element >> applied). But this does not work for julia source code blocks. Is this >> just not implemented or do I miss something? > > What are you using to convert src blocks to HTML? Specifically, what is > the setting of org-html-htmlize-output-type? it is set to `css', this is the correct choice, no? OpenPGP_0xC375C6AF05125C52.asc Description: application/pgp-keys OpenPGP_signature Description: PGP signature
Re: Syntax highlighting for julia source blocks
On Monday, 26 Sep 2022 at 14:09, reza wrote: > When exporting to html, syntax highlighting is automatically applied to > exported python source blocks (syntax elements get a span element > applied). But this does not work for julia source code blocks. Is this > just not implemented or do I miss something? What are you using to convert src blocks to HTML? Specifically, what is the setting of org-html-htmlize-output-type? -- : Eric S Fraga, with org release_9.5.5-840-g52be6f in Emacs 29.0.50
Re: Syntax highlighting for julia source blocks
On 9/26/22 17:15, Fraga, Eric wrote: > On Monday, 26 Sep 2022 at 14:09, reza wrote: >> When exporting to html, syntax highlighting is automatically applied to >> exported python source blocks (syntax elements get a span element >> applied). But this does not work for julia source code blocks. Is this >> just not implemented or do I miss something? > > What are you using to convert src blocks to HTML? Specifically, what is > the setting of org-html-htmlize-output-type? Looks like I was missing `julia-mode', but still after installation, no syntax highlighting for julia source code blocks... OpenPGP_0xC375C6AF05125C52.asc Description: application/pgp-keys OpenPGP_signature Description: PGP signature
Re: [BUG] org-create-file-search-functions and description [9.5.5 (release_9.5.5 @ /usr/share/emacs/29.0.50/lisp/org/)]
On 26/09/2022 19:12, Ihor Radchenko wrote:
Magnus Therning writes:
The documenation on org-create-file-search-functions contains this
piece of text
A function in this hook may also use setq to set the variable
description to provide a suggestion for the descriptive text to
be used for this link when it gets inserted into an Org buffer
with org-insert-link.
This doesn't seem to be true though. I really would love for there
to be a way to influence the link description, but no matter what
the documentation should be corrected.
Thus, we may as well take this opportunity and allow
`org-create-file-search-functions' to return a cons cell
("search term" . "description"). This will not require unintuitive
global variables.
There is the `org-store-link-plist' variable used by :store functions
from `org-link-parameters' but not by the
`org-create-file-search-functions' hook. Maybe it is enough to add
(setq desc (plist-get org-store-link-plist :description))
after calling of the hook.
For a while, I hope, it is possible to create a workaround using
(org-link-set-parameters
"file"
:store ...)
Re: Extract toc from org file
reza writes: > Is there a way to extract a toc from an org file e.g: > > #+INCLUDE: myfile.org :toc only > > I want to assemble the toc's from several files into one file and there > seems to be no easy way to do this. Maybe the org-make-toc package can help you with what you're looking for: https://github.com/alphapapa/org-make-toc You can choose a heading on every document to contain a TOC. And then link each heading via org-transclusion: https://github.com/nobiot/org-transclusion Best regards, Juan Manuel -- -- -- Juan Manuel Macías https://juanmanuelmacias.com https://lunotipia.juanmanuelmacias.com https://gnutas.juanmanuelmacias.com
Re: IM dev discussions?
Payas Relekar writes: > Admittedly I am yet to try it, but it can also provide filtering to mute > particular categories so they don't clutter your mailbox :) > > Replying to discourse notification emails has worked well in my experience, > and there are apparently ways to create new posts by sending emails as well: I've tried an email-based workflow with Discourse before and I'll say it's fairly decent, much better than, say, replying to GitHub email notifications, where they can't even apply GitHub Flavored Markdown consistently! I have no experience in setting up / administrating Discourse myself, however. ~ Hendursaga
Re: Extract toc from org file
On 26/09/2022 22:21, Max Nikulin wrote: On 26/09/2022 18:53, reza wrote: Is there a way to extract a toc from an org file e.g: #+INCLUDE: myfile.org :toc only I want to assemble the toc's from several files into one file and there seems to be no easy way to do this. Likely `org-element-map' allows to extract headings. There are should be some example in the mail list archive and at worg (hacks, perhaps in FAQ). See also info "(org) Using the Mapping API" https://orgmode.org/manual/Using-the-Mapping-API.html for `org-map-entries'.
Re: Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt
On 26/09/2022 18:39, Ihor Radchenko wrote: Should we add page break (^L) to our syntax? It sounds like a reasonable addition for a text-based markup. I do not have strong opinion. It is a control character while I prefer explicit markup and printable characters or commands in such case. On the other hand the character is widely used in .el files. Users may expect \newline when ^L is exported to LaTeX.
Re: [PATCH] ob-clojure.el: Add support for babashka and nbb backend
Hi! Bastien writes: > Applied in main as 764642f5, thanks a lot and sorry for the delay. > > I also added you to https://orgmode.org/worg/contributors.html. Thank you very much :) > Would you consider taking over the maintainance of ob-clojure.el? I think I would. What does this exactly entail? Should I subscribe to https://updates.orgmode.org/ or something? Is there a backlog if issues to go through and try to resolve? Cheers, Daniel
Re: on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/s
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
--8<---cut here---start->8---
** PE etiro.espiritual {collaborator.family} :DAVID:
:PROPERTIES:
:CATEGORY: da.santi
:END:
<2022-09-24 Sat 9:00-11:00>
--8<---cut here---end--->8---
That above is an equivalent example using normal timestamps.
On my use case. I have seven categories on this file
for example: chores, work, home, family. I add entries for all this
categories every week (I just try to add entries once a week if possible
on the weekends).
In case I pick normal timestamps I would need to yank 5 lines and edit 2
lines one at the top and other at the bottom of the yanked region. On my
current worflow using diary-style timestamps I just need to add a line
at the bottom and edit that line.
The advantage of using normal timestamps is I could append the line at
the end of the file. On diary-style timestamps I should do occur for the
category and after it C-c C-n for appending at the end of the current subtree.
For my use case I should keep working with diary-style timestamps but
YMMV.
Thanks guys for the help, the tips and the explanation.
Best Regards
Confused about what the COMMENT keyword means
Hello. I have the file: * COMMENT foo #+EXPORT_FILE_NAME: foo.pdf #+TITLE: foot fofoo * bar #+EXPORT_FILE_NAME: bar.pdf #+TITLE: bart babar If I do 'C-c e l p', the file 'foo.pdf' is created from the 'foo.tex' file. The content is bar'ish, though, as I expect. By contrast, with this file # * foo # #+EXPORT_FILE_NAME: foo.pdf # #+TITLE: foot # fofoo * bar #+EXPORT_FILE_NAME: bar.pdf #+TITLE: bart babar for which I explicitly comment the whole 'foo' tree, the content is the same but the files are 'bar.pdf' and 'bar.tex'. But I thought both way of commenting were equivalent. What am I missing? Thank you. NB: I used 'emacs -Q' GNU Emacs 27.2 (build 1, x86_64-redhat-linux-gnu, GTK+ Version 3.24.30, cairo version 1.17.4) of 2021-08-07 Org mode version 9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/) -- EOST (École et Observatoire des Sciences de la Terre) ITE (Institut Terre & Environnement) | alain.coch...@unistra.fr 5 rue René Descartes [bureau 106] | Phone: +33 (0)3 68 85 50 44 F-67084 Strasbourg Cedex, France | [ slot available for rent ]
Compiling a C++ source block
Hello,
I wish to compile & run this source block in org-mode:
#+name: gnc_cav
#+header: :includes
#+header: :libs -L/usr/local/lib -lginac -lcln
#+header: :flags -std=c++17
#+header: :namespaces std GiNaC
# #+header: :var table=
#+header: :var job="vectors" :var vol=113.13115406160385926 :var
r=1.0995524816924328312
#+header: :var a=4.916 :var c=5.4054
#+header: :main no
#+begin_src C++
ex vol(symbol a, symbol c)
{
ex v = a*a * c * sin(60*Pi/180);
return v;
}
ex coa(symbol a, symbol c) {
ex covera = c/a;
return covera;
}
ex scl(symbol a, symbol c, double ad, double cd) {
// symbol v("v");
// symbol r("r");
ex v = vol(a,c);
ex r = coa(a,c);
numeric three(3);
// ex s =
power(v.subs(lst{a==ad,c==cd})),1/three)/(power(sin(60*Pi/180),1/three) *
power(r.subs(lst{a==ad,c==cd}),1/three));
ex s =
power(v.subs(lst{a==ad,c==cd}),1/three)/(power(sin(60*Pi/180),1/three) *
power(r.subs(lst{a==ad,c==cd}),1/three));
return s;
}
ex scl(double vd, double rd) {
numeric three(3);
ex s = power(vd,1/three)/(power(sin(60*Pi/180),1/three) *
power(rd,1/three));
return s;
}
int main () {
if ( strncmp(job, "volume", 6) == 0) { // ./v volume a c, calculate volume
symbol as("as");
symbol cs("cs");
ex v = vol(as, cs);
cout << "Volume = " << v.subs(lst{as == a, cs == c}).evalf() << "\n";
ex r = coa(as, cs);
cout << "c/a = " << r.subs(lst{as == a, cs == c}).evalf() << "\n";
ex a_calc = scl(as, cs, a, c);
cout << "a_calc = " << a_calc.evalf() << "\n";
cout << "c_calc = "
<< a_calc.evalf() * r.subs(lst{as == a, cs == c}).evalf() << "\n";
} else if ( job,"vectors",5) == 0 ) { // ./v vectors vol c/a
//double vd = stod(argv[2]);
//double rd = stod(argv[3]);
ex a_calc = scl(v,r);
cout << "a_calc = " << a_calc.evalf() << "\n";
cout << "c_calc = " << a_calc.evalf() * rd << "\n";
//double a_scale = a;
} // vectors
} // main
#+end_src
When I attempt compilation using 'C-c C-c' I get:
/tmp/babel-eqG2i0/C-src-3zG2ec.cpp:16:1: error: unknown type name 'ex'
ex vol(symbol a, symbol c)
and lots of similar errors. I infer this is because ginac.h is not
found. I have tried specifying in ':includes' to no
avail. I have tried specifying the full path to ginac.h:
and specifying -I/usr/local/lib/ginac/ as
part of ':includes', but the error persists.
Maybe the C++ support is not set up to handle this use case, but perhaps
I am missing something.
Any help will be much appreciated.
Thanks,
Roger
Re: Compiling a C++ source block
You may try:
#+header: :includes '("" "")
Also, you have this commented line:
# #+header: :var table=
It seems to break the #+header: chain
Just remove it.
By the way, to figure out future compilation problems, you
may click on the error:
/tmp/babel-eqG2i0/C-src-3zG2ec.cpp:16:1: error: unknown
type name 'ex'
This will open the source file actually being compiled.
Have fun!
Le 26/09/2022 à 21:13, Roger Mason
a écrit :
Hello,
I wish to compile & run this source block in org-mode:
#+name: gnc_cav
#+header: :includes
#+header: :libs -L/usr/local/lib -lginac -lcln
#+header: :flags -std=c++17
#+header: :namespaces std GiNaC
# #+header: :var table=
#+header: :var job="vectors" :var vol=113.13115406160385926 :var r=1.0995524816924328312
#+header: :var a=4.916 :var c=5.4054
#+header: :main no
#+begin_src C++
ex vol(symbol a, symbol c)
{
ex v = a*a * c * sin(60*Pi/180);
return v;
}
ex coa(symbol a, symbol c) {
ex covera = c/a;
return covera;
}
ex scl(symbol a, symbol c, double ad, double cd) {
// symbol v("v");
// symbol r("r");
ex v = vol(a,c);
ex r = coa(a,c);
numeric three(3);
// ex s = power(v.subs(lst{a==ad,c==cd})),1/three)/(power(sin(60*Pi/180),1/three) * power(r.subs(lst{a==ad,c==cd}),1/three));
ex s = power(v.subs(lst{a==ad,c==cd}),1/three)/(power(sin(60*Pi/180),1/three) * power(r.subs(lst{a==ad,c==cd}),1/three));
return s;
}
ex scl(double vd, double rd) {
numeric three(3);
ex s = power(vd,1/three)/(power(sin(60*Pi/180),1/three) * power(rd,1/three));
return s;
}
int main () {
if ( strncmp(job, "volume", 6) == 0) { // ./v volume a c, calculate volume
symbol as("as");
symbol cs("cs");
ex v = vol(as, cs);
cout << "Volume = " << v.subs(lst{as == a, cs == c}).evalf() << "\n";
ex r = coa(as, cs);
cout << "c/a = " << r.subs(lst{as == a, cs == c}).evalf() << "\n";
ex a_calc = scl(as, cs, a, c);
cout << "a_calc = " << a_calc.evalf() << "\n";
cout << "c_calc = "
<< a_calc.evalf() * r.subs(lst{as == a, cs == c}).evalf() << "\n";
} else if ( job,"vectors",5) == 0 ) { // ./v vectors vol c/a
//double vd = stod(argv[2]);
//double rd = stod(argv[3]);
ex a_calc = scl(v,r);
cout << "a_calc = " << a_calc.evalf() << "\n";
cout << "c_calc = " << a_calc.evalf() * rd << "\n";
//double a_scale = a;
} // vectors
} // main
#+end_src
When I attempt compilation using 'C-c C-c' I get:
/tmp/babel-eqG2i0/C-src-3zG2ec.cpp:16:1: error: unknown type name 'ex'
ex vol(symbol a, symbol c)
and lots of similar errors. I infer this is because ginac.h is not
found. I have tried specifying in ':includes' to no
avail. I have tried specifying the full path to ginac.h:
and specifying -I/usr/local/lib/ginac/ as
part of ':includes', but the error persists.
Maybe the C++ support is not set up to handle this use case, but perhaps
I am missing something.
Any help will be much appreciated.
Thanks,
Roger
Re: Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt
Max Nikulin writes: > On 26/09/2022 18:39, Ihor Radchenko wrote: >> Should we add page break (^L) to our syntax? It sounds like a reasonable >> addition for a text-based markup. > > I do not have strong opinion. It is a control character while I prefer > explicit markup and > printable characters or commands in such case. On the other hand the > character is widely > used in .el files. > > Users may expect \newline when ^L is exported to LaTeX. I think I'm with you as well. I don't have a strong opinion and while personally, I don't like control characters used as part of the syntax, ^L is often used in elisp files, so ..
Please add support for dlangs packagemanager to ob-C.el
Please see the patch comment. I reworked my original patch to fit into the TINYPATCH category. Kind regards, Christian 0001-lisp-ob-C.el-Support-dub-dependencies-for-dlang.patch Description: Binary data
Re: Extract toc from org file
reza writes: > Hi list > > Is there a way to extract a toc from an org file e.g: > > #+INCLUDE: myfile.org :toc only > > I want to assemble the toc's from several files into one file and there > seems to be no easy way to do this. I presume that you are attempting to export multiple org files at the same time. Such functionality is covered by Org publish. Org publish allows generating a sitemap, which is another word for TOC in a multifile export. See 14.1.7 Generating a sitemap section of Org manual. If you are exporting a single Org file that is using contents of multiple #+include'd files, you can use the normal TOC generation as described in 13.3 Table of Contents section of the Org manual. Hope it helps. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [BUG] org-create-file-search-functions and description [9.5.5 (release_9.5.5 @ /usr/share/emacs/29.0.50/lisp/org/)]
Max Nikulin writes:
>> Thus, we may as well take this opportunity and allow
>> `org-create-file-search-functions' to return a cons cell
>> ("search term" . "description"). This will not require unintuitive
>> global variables.
>
> There is the `org-store-link-plist' variable used by :store functions
> from `org-link-parameters' but not by the
> `org-create-file-search-functions' hook. Maybe it is enough to add
>
> (setq desc (plist-get org-store-link-plist :description))
>
> after calling of the hook.
This makes sense. Instead of making `org-create-file-search-functions'
return a cons cell, we can use the same scheme as in
`org-store-link-functions' where the functions can call
`org-link-store-props' inside to set e.g. the description.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
[BUG] org-store-link-functions advertizes that the first non-nil return value is used, but it is not how org-store-link handles it (was: [BUG] org-create-file-search-functions and description [9.5.5 (
Max Nikulin writes: > There is the `org-store-link-plist' variable used by :store functions > from `org-link-parameters' but not by the > `org-create-file-search-functions' hook. Maybe it is enough to add Reading through `org-store-link-functions' docstring and `org-store-link' code, I noticed that `org-store-link-functions' promises the following: Each function will be called in turn until one returns a non-nil value. Yet, `org-store-link' does the following: (dolist (f (org-store-link-functions)) (when (funcall f) (push (cons f (copy-sequence org-store-link-plist)) results-alist))) (pcase results-alist ... ;; Reinstate link plist associated to the chosen ;; function. (apply #'org-link-store-props (cdr (assoc-string (completing-read (format "Store link with (default %s): " name) (mapcar #'car results-alist) nil t nil nil (symbol-name name)) results-alist))) t)) That is, all the store link functions are actually being executed, not until first non-nil return value. If multiple non-nil values are returned, an interactive query is displayed to the user. --- The actual behaviour is indeed nice, but I am wondering how it is going to work in non-interactive case. Thoughts? -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Syntax highlighting for julia source blocks
reza writes: > Looks like I was missing `julia-mode', but still after installation, no > syntax highlighting for julia source code blocks... Can you please provide an example file and exact steps you did to export it? See https://orgmode.org/manual/Feedback.html -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
org exported pdf files
can these files include the language attribute like what happens in microsoft word? If yes, and the contents are text that would go a long way to making those pdf files screen-reader accessible. Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) .
Re: Confused about what the COMMENT keyword means
alain.coch...@unistra.fr writes: > Hello. I have the file: > >* COMMENT foo >#+EXPORT_FILE_NAME: foo.pdf >#+TITLE: foot >fofoo >* bar >#+EXPORT_FILE_NAME: bar.pdf >#+TITLE: bart >babar #+EXPORT_FILE_NAME is an in-buffer export setting with global effect. According to 13.2 Export Settings section of the Org manual, In-buffer settings may appear anywhere in the file, either directly or indirectly through a file included using ‘#+SETUPFILE: filename or URL’ syntax. Because export settings are global, they have higher priority over the COMMENTed heading. Further, you have two instances of the #+EXPORT_FILE_NAME in your buffer. The behaviour of Org is undefined in such scenario, but the current implementation detail makes Org use the first instance found in the file during export. Do note that usage of #+EXPORT_FILE_NAME and #+TITLE like in your example is erroneous - they do not apply to their subtrees. Please use heading properties instead for the desired effect. > By contrast, with this file > ># * foo ># #+EXPORT_FILE_NAME: foo.pdf ># #+TITLE: foot ># fofoo >* bar >#+EXPORT_FILE_NAME: bar.pdf >#+TITLE: bart >babar This file contains no export settings. # #+EXPORT_FILE_NAME: foo.pdf line is not an export setting. It does not matter that it is a comment, blah#+EXPORT_FILE_NAME: foo.pdf would not work either. I think that the manual is not clear enough about applying in-buffer settings and keywords. We may want to clarify this detail. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: [PATCH] ob-clojure.el: Add support for babashka and nbb backend
Daniel Kraus writes: >> Would you consider taking over the maintainance of ob-clojure.el? > > I think I would. What does this exactly entail? > Should I subscribe to https://updates.orgmode.org/ or something? We have some info in https://orgmode.org/worg/org-maintenance.html#org37c7d5d Ideally, you can subscribe to Org mailing list and participate in the relevant discussions. Most importantly, when people propose new patches and report bugs related to ob-clojure.el. If you time does not permit following the mailing list closely, do note that we may CC you in emails when we need your attention wrt specific discussions. Since you are interested in maintaining a specific programming language backend, it would be best if you can help with confirming bugs. It is hard for the core maintainers to test all the possible supported programming languages. (I don't even have clojure installed on my machine). Finally, and optionally, you can also contribute new features to the maintained file, contribute to the ob-clojure documentation at https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-clojure.html (see WORG repo at https://sr.ht/~bzg/org/), and possibly write tests in tests/lisp/test-ob-clojure.el > Is there a backlog if issues to go through and try to resolve? I recall a couple of proposed patches and bug reports. Let me quickly pull them out of my todo list... https://orgmode.org/list/paxpr08mb6640fa07d8236d848005bb84a3...@paxpr08mb6640.eurprd08.prod.outlook.com https://list.orgmode.org/orgmode/m2lewez8zh.fsf@numbch...@gmail.com/ https://orgmode.org/list/cagtweadodwkm8s217ufxzxw0zpycvo45khgq13lwgyvz6v9...@mail.gmail.com https://orgmode.org/list/m2v9jp40ry@gmail.com -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: on picking diary-style timestamps or normal timestamps when adding agenda entries (was: [BUG] org-agenda-list takes 4m compared to 27 that took 15 seconds [9.5.2 (release_9.5.2-25-gaf6f12 @ /usr/s
andrés ramírez writes:
> --8<---cut here---start->8---
> ** PE etiro.espiritual {collaborator.family} :DAVID:
> :PROPERTIES:
> :CATEGORY: da.santi
> :END:
> <2022-09-24 Sat 9:00-11:00>
> --8<---cut here---end--->8---
>
> That above is an equivalent example using normal timestamps.
>
> On my use case. I have seven categories on this file
> for example: chores, work, home, family. I add entries for all this
> categories every week (I just try to add entries once a week if possible
> on the weekends).
>
> In case I pick normal timestamps I would need to yank 5 lines and edit 2
> lines one at the top and other at the bottom of the yanked region. On my
> current worflow using diary-style timestamps I just need to add a line
> at the bottom and edit that line.
Not at all.
You can as well do
* PE
:PROPERTIES:
:CATEGORY: da.santi
:END:
** <2022-09-24 Sat 9:00-11:00> etiro.espiritual {collaborator.family} :DAVID:
** <2022-09-27 Tue> Another entry to be displayed in agenda. It inherits parent
category
> The advantage of using normal timestamps is I could append the line at
> the end of the file. On diary-style timestamps I should do occur for the
> category and after it C-c C-n for appending at the end of the current subtree.
Note org-refile command. See "9.1 Refile and Copy" section of Org manual.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
Re: org exported pdf files
Jude DaShiell writes: > can these files include the language attribute like what happens in > microsoft word? AFAIK, yes. See org-latex-hyperref-template > If yes, and the contents are text that would go a long > way to making those pdf files screen-reader accessible. Have you tried Org-exported pdfs on screen-reader? (I haven't, so I am curious to see if there are any improvements we can make in this area). -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: on picking diary-style timestamps or normal timestamps when adding agenda entries
Hi. Ihor.
> "Ihor" == Ihor Radchenko writes:
[...]
Ihor> Not at all. You can as well do
--8<---cut here---start->8---
* PE
:PROPERTIES:
:CATEGORY: da.santi
:END:
** <2022-09-24 Sat 9:00-11:00> etiro.espiritual {collaborator.family} :DAVID:
** <2022-09-27 Tue> Another entry to be displayed in agenda. It inherits parent
category
--8<---cut here---end--->8---
That one looks promising. Could I omit the day-on-letters (three
letters) before the closing bracket?.
I remember there was a keybinding for picking the day from calendar. But I
noticed killing and yanking was quicker than using the calendar. I am a
viper-mode user. killing and yanking is just yyp.
Ihor> Note org-refile command. See "9.1 Refile and Copy" section of Org
manual.
Last time I tried org-refile I did not stick on my workflow, perhaps I
should try again.
Best Regards
Re: org exported pdf files
Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . On Tue, 27 Sep 2022, Ihor Radchenko wrote: > Jude DaShiell writes: > > > can these files include the language attribute like what happens in > > microsoft word? > > AFAIK, yes. See org-latex-hyperref-template > > > If yes, and the contents are text that would go a long > > way to making those pdf files screen-reader accessible. > > Have you tried Org-exported pdfs on screen-reader? > (I haven't, so I am curious to see if there are any improvements we can > make in this area). > Not yet, but that will be on my list. Is that latex template automatically used by orgmode when doing a pdf export or is code needed in some file to pull it in? >
Re: on picking diary-style timestamps or normal timestamps when adding agenda entries
andrés ramírez writes:
> --8<---cut here---start->8---
> * PE
> :PROPERTIES:
> :CATEGORY: da.santi
> :END:
> ** <2022-09-24 Sat 9:00-11:00> etiro.espiritual {collaborator.family} :DAVID:
> ** <2022-09-27 Tue> Another entry to be displayed in agenda. It inherits
> parent category
> --8<---cut here---end--->8---
>
> That one looks promising. Could I omit the day-on-letters (three
> letters) before the closing bracket?.
Yup.
>From a footnote in 8.1 Timestamps sections of Org manual:
(1) The Org date format is inspired by the standard ISO 8601
date/time format. To use an alternative format, see *note Custom time
format::. The day name is optional when you type the date yourself.
However, any date inserted or modified by Org adds that day name, for
reading convenience.
> I remember there was a keybinding for picking the day from calendar. But I
> noticed killing and yanking was quicker than using the calendar. I am a
> viper-mode user. killing and yanking is just yyp.
Inserting timestamp for today's date is as easy as C-c .
Choosing tomorrow is just C-c . +
Choosing next week is C-c . +w
See 8.2.1 The date/time prompt
Also, you can copy the whole heading shifting time in its timestamps.
See org-clone-subtree-with-time-shift (C-c C-x c)
> Ihor> Note org-refile command. See "9.1 Refile and Copy" section of Org
> manual.
>
> Last time I tried org-refile I did not stick on my workflow, perhaps I
> should try again.
Depending on your preference, you may want to customize
org-refile-use-outline-path and org-outline-path-complete-in-steps.
In particular, changing org-outline-path-complete-in-steps to nil works
best with fuzzy completion backends like helm/ivy/orderless.
--
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92
Re: org exported pdf files
Jude DaShiell writes: >> Have you tried Org-exported pdfs on screen-reader? >> (I haven't, so I am curious to see if there are any improvements we can >> make in this area). >> > Not yet, but that will be on my list. Is that latex template > automatically used by orgmode when doing a pdf export or is code needed > in some file to pull it in? Yes, the template is used by default. You can also control what is filled in there in export settings (see 13.10.2 LaTeX specific export settings) And, of course, you can override/extend it if necessary. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: org exported pdf files
Having examined 13.10.2, with the polyglossia package installed and accessible to orgmode putting set-language into the right place would default to English and other languages would need to specify their language for a pdf export. On Linux I have espeak-ng running as default and I run orca as necessary. I mostly live on the command line so orca is used rarely. I think a reasonable test of export quality will be to make a pdf with orgmode then run that pdf through pdftotext and compare the extracted text with the pdf file. I can't do that since without use of pdftotext the screen readers will not work on pdf files. Jude "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author, 1940) . On Tue, 27 Sep 2022, Ihor Radchenko wrote: > Jude DaShiell writes: > > >> Have you tried Org-exported pdfs on screen-reader? > >> (I haven't, so I am curious to see if there are any improvements we can > >> make in this area). > >> > > Not yet, but that will be on my list. Is that latex template > > automatically used by orgmode when doing a pdf export or is code needed > > in some file to pull it in? > > Yes, the template is used by default. You can also control what is > filled in there in export settings (see 13.10.2 LaTeX specific export > settings) > > And, of course, you can override/extend it if necessary. > >
Re: org exported pdf files
Jude DaShiell writes: > Having examined 13.10.2, with the polyglossia package installed and > accessible to orgmode putting set-language into the right place would > default to English and other languages would need to specify their > language for a pdf export. The default can be changed in your Emacs configuration. Check out org-export-default-language. > On Linux I have espeak-ng running as default > and I run orca as necessary. I mostly live on the command line so orca is > used rarely. > I think a reasonable test of export quality will be to make a pdf with > orgmode then run that pdf through pdftotext and compare the extracted text > with the pdf file. I can't do that since without use of pdftotext the > screen readers will not work on pdf files. I checked on of my exported PDFs, and it looks mostly consistent with the org source from a brief look. The only minor deficiency is sparkled text from included vector images with text, but I imagine that it is common and may or may not be a real deficiency. Do note that Org to PDF export works by first exporting to a .tex file and then running TeX. As long as TeX makes a decent job with PDF accessibility, we should be good to go. Just need to make sure that we pass the correct options to TeX in the generated .tex file. You mentioned that one of the TeX options is setting the correct metadata. I am not aware about other required options that can improve accessibility. If you know any, feel free to share. Also, you can refer to our previous discussion about accessibility of documents exported by Org. https://list.orgmode.org/orgmode/87czew3w5l.fsf@localhost/ -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org development at https://liberapay.com/org-mode, or support my work at https://liberapay.com/yantar92
Re: Should page break (^L) work as paragraph element separator and be included into Org syntax? (was: [BUG] org-fill-paragraph doesn't handle ^L correctly [9.5.4 (release_9.5.4-19-g4dff42 @ /home/matt
On Tue, 27 Sep 2022 01:10:49 +1000 Matt Beshara wrote: > > ^L is not a part of Org specification for paragraph separators. > > According to > > https://orgmode.org/worg/dev/org-syntax.html#Paragraphs, > > paragraph boundaries should either be empty lines, or beginning > > of other > > Org elements. > > Fair enough. If the consensus from others is that ^L should be > recognised as a paragraph separator and the code is eventually > written to make that work, that would be nice, but as it stands I > can just start adding newlines after ^L. > > Thanks for your work on Org mode! > Matt > Actually ^L is a *page* separator (to be exact “FORM FEED”). Best regards Robert
