Re: Confused about source code blocks evaluation when exporting

"Fraga, Eric" writes: > By default, the results of a src block evaluation is the value of the > src block which is typically the value returned by the last statement. The value of the last expression, not the last statement. Rudy -- "Strange as it may sound, the power of mathematics rests on

[PATCH] ob-core.el: Fix docstring single quotes [9.6 (9.6-gc66bdb @ /home/n/.emacs.d/elpaca/builds/org/)]

Emacs 29's byte compiler warns about single quotes in docstring examples. Emacs : GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.34, cairo version 1.17.6) of 2022-06-28 Package: Org mode version 9.6 (9.6-gc66bdb @ /home/n/.emacs.d/elpaca/builds/org/) >From

Re: index for HTML export

"Fraga, Eric" writes: > I know (well, I believe as I haven't tried yet) I can /publish/ a > project and generate an index using the #+index entries in the org > files. However, for a single file, is it possible to generate the index > as part of the export process directly (or even separately

Re: Alternatives or org-capture?

ypuntot writes: > Thanks for your template! > Maybe it would be nice to have it on the MELPA documentation? > I couldn't find other documentation. > org-capture template is just a personal usage scene, people will want to define their own org-capture template. So no need to add this to

Re: Alternatives or org-capture?

Thanks, Tim! I will try it. > Recommend you get to know/understand org-capture first and the rest will > become much clearer.

Re: Confused about source code blocks evaluation when exporting

Fraga, Eric writes on Wed 13 Jul 2022 10:57: > No, you used the word correctly. My point was that this was your > main issue! Understanding what is the "result" of a src block > evaluation is key. Thank you for the clarification. I can see that I am still very confused. > > Thank you

Re: index for HTML export

(apologies for flurry of emails) Publishing works, in the sense that my org file is exported to HTML just fine. An index file is created but is not populated with any index links. What am I missing? The info page is less than helpful unfortunately. Are index lines, e.g. #+index: test!org

Re: index for HTML export

So publishing cannot have the target directory be the same as the source directory, it would seem? Having a different directory for :publishing-directory makes publishing work. I still do not understand the error, however. My original question remains: can we create an index for HTML export

Re: Recent folding issues

Hi Ihor, > Can you try the attached patch set? Thanks for the very prompt patchset! Testing on the minimal example, the patchset solves the problem I reported. After some brief testing with my usual config, it solves the problem of headlines running together after capture, and also solves the

Re: index for HTML export

... and following up on this, when trying to /publish/ instead of just export, I am failing miserably. I created a simple project definition but every time I try to publish either a specific file or the project, I get (with file name partly elided): --8<---cut

index for HTML export

Hello all, I know (well, I believe as I haven't tried yet) I can /publish/ a project and generate an index using the #+index entries in the org files. However, for a single file, is it possible to generate the index as part of the export process directly (or even separately from the export

[rounding (ceil in matlab)] (was: calculating quartils, tercils (or percentiles) Using R?)

>>> "JJ" == Jeremie Juste writes: > Hello Uwe, >> On Sunday, 22 May 2022 at 08:40, Uwe Brauer wrote: >> but I can't not find a way to calculate other percentiles, like >> terciles or so. Does anybody know about this, or a org-function doing >> it? > I would recommend checking the R

Re: Confused about source code blocks evaluation when exporting

On Tuesday, 12 Jul 2022 at 23:13, alain.coch...@unistra.fr wrote: > I guess I didn't use 'incidental' correctly. I meant it as "not my > main concern". Anyway, thank you; I could check that if I switch the > 2 lines I indeed get '#+RESULTS:' to show foo'. No, you used the word correctly. My

[tip/offtopic] A function to describe the characters of a word at point

Sorry for the slight offtopic. Since Unicode and character issues come up here from time to time, I'm sharing this 'homemade' function that I wrote a long time ago for my work, in case someone finds it useful. It Shows a brief descriptive list of all characters in a word at point. Each character

bug#45915: 28.1; delete-char deletes two letters

As Ihor pointed out, delete-char deletes two letters. Can someone take a look and evaluate if this is issue with delete-char? I simplified the recipes as shown below. #+begin_src emacs-lisp (defun emacs-bug-reproduce-45915 () "Reproduce bug#45915." ;; (gnus-read-ephemeral-emacs-bug-group

Re: [External] : Re: missing a character / font in agenda?

On 13/07/2022 07:26, Stefan Kangas wrote: Ihor Radchenko writes: I think this should be considered a bug, since the glyph used (LEFTWARDS TRIANGLE-HEADED ARROW / #2b60) is not present in most fonts. If that is true (I don't know) then maybe we should just use a more ubiquitous glyph?

Re: [External] : Re: missing a character / font in agenda?

Stefan Kangas writes: > If that is true (I don't know) then maybe we should just use a more > ubiquitous glyph? I have done a quick test with some fonts that are ---I believe--- quite popular. This character is missing from DejaVu Sans Mono, Iosevka, Source Pro, Fira Code and Hack. JuliaMono

Re: [External] : Re: missing a character / font in agenda?

for what it's worth, without the symbola font on my machine (though i've now added it), i seem to see the left-arrow 2b60 rendered using: ftcrhb:-GNU-Unifont-normal-normal-normal-Sans-Serif-16-*-*-*-c-80-iso10646-1 (#x2B61) (if i'm interpreting the output of [C-u C-x =] correctly.)