Hi,
I wanted to play with special blocks and started by installing the
package org-special-block-extras and defining a new block:
(org-defblock hmwfoo nil (reps 3)
"Ahoj"
(message "ahoj: %s" contents)
(org-parse (s-repeat reps contents)))
For the tests I started with exporting to html.
A
On 25/02/2023 23:47, Ken Mankoff wrote:
On 2023-02-25 at 08:05 -08, Max Nikulin wrote:
I believe, it is safer to define
`org-babel-variable-assignments:screen' some way: alias, substitution,
function that calls `org-babel-variable-assignments:shell'. I am
unsure which variant is better. I see a
"Mark A. Hershberger" writes:
> Loading the following file with "emacs -Q", I'm un-able to type 'C-c
> C-c' in the source block to execute it.
>
> #+begin_src elisp
> (defun count-lines (dir)
> ...
> When I do the following error appears:
>
> ⛔ Warning (org-element-cache): org-element--cache: Org
Ihor Radchenko writes:
> Re-defining built-in functions is generally dangerous. You need to know
> what you are doing.
I recommend reading D.1 Emacs Lisp Coding Conventions section of Elisp
manual. In particular the paragraph about naming symbols and functions:
• You should choose a short wo
Damien Cassou writes:
> Subject: [PATCH] org.el: Avoid crash in `org-file-contents' in case of network
> failure
Applied, onto bugfix.
Thanks for your contribution!
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f9aeba5dd
--
Ihor Radchenko // yantar92,
Org mode contributor,
L
Cassio Koshikumo writes:
> Create an .org file with the following contents:
>
> * First Level
> ...
> Now, C-c / m (or M-x org-sparse-tree and select m) and Match: tag.
>
> The resulting sparse tree looks like this:
>
> * First Level
> ** One :tag:
> *** Child
> ** Four :tag:
>
> So far, so good.
Angel de Vicente writes:
> I was trying to export an .org file to .rst. I have ox-rst 20200815.1511
> installed, and I have run (require 'ox-rst), but despite this, there is
> no option for rsT in the Org Export Dispatcher. Did I miss something to
> make it work?
Works on my side with the latest
Ken Mankoff writes:
> From f7ca0258d72b3da5743b1134718b1d1f0d74491d Mon Sep 17 00:00:00 2001
> From: "Kenneth D. Mankoff"
> Date: Mon, 20 Feb 2023 21:40:39 -0800
> Subject: [PATCH] lisp/ob-screen.el: Support var header args for babel blocks
Thanks for the patch!
> +;; Reuse the variable assign
Sébastien Miquel writes:
>> The traditional user-facing approach for toggling staff in export is
>> setting export options.
>
> Indeed. Then I suggest that such use be described in the manual.
> Having the user create a whole new option in order to toggle a
> `chikenize` package seems a bit unwie
Sébastien Miquel writes:
>> If we implement export transcoders as much as possible using templates,
>> it will become very easy for users to adjust the export behavior beyond
>> what is already possible.
>
> This can be achieved in a couple of lines with advices.
Only the simplest cases of prepe
Ihor Radchenko writes:
The traditional user-facing approach for toggling staff in export is
setting export options.
Indeed. Then I suggest that such use be described in the manual.
Having the user create a whole new option in order to toggle a
`chikenize` package seems a bit unwieldy, however.
Ihor Radchenko writes:
Only the simplest cases of prepending/appending staff.
If we want to splice into the normal export template, users currently
must either write an output filter or rewrite the trnascoders
completely.
The proposed template system will provide more flexibility to modify the
d
The online manuals for 16.5 Evaluating Code Blocks seem inconsistent and
include a header argument that seems to no longer be respected.
https://orgmode.org/manual/Evaluating-Code-Blocks.html, for version 9.6,
right now says you can specify a header argument ":eval yes" on source code
blocks to by
Hi, This is first my first bug report to org-mode. So I would like to
start by thanking
everyone involved for making this life enhancing drug a reality. It's
one of the rare software which
actually does what i mean. It's wonderful :cheers:
* One Line summary
`org-agenda-list` shows the week
Thanks for pointing out that I'm re-defining an internal function.
If I can reopen this issue, it would be good if the error message actually said
that.
"Mark A. Hershberger" writes:
> If I can reopen this issue, it would be good if the error message actually
> said that.
Org has no idea which functions are built-in. Org has no idea which
functions are re-defined and just uses modified versions if the user
prefers re-defined version. Emacs give
Hi everybody
Is it at all possible to produce a correct org-ref citation format
from ivy-bibtex (or helm-bibtex, I tried both)? What I mean by
"correct" is the format: [[cite:&citekey]].
The problem seems to come down to the question what has to be inserted
in the 2nd line here:
(setq bibtex-com
Hi Ihor,
>> Anyway I tried to hack my way trough it. It seems there are two things
>> to do :
>> 1) Enable noweb-ref to contain multiple references.
>> 2) Accumulate references when using header-args+ or use tags to set the
>> value of noweb-ref
>>
>> I came up with a quick patch for 1):
>> modifi
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen. You don't know how to make a good report? See
https://orgmode.org/manual/Feedback.html#Feedback
Your bug report will be posted to the Org mailing list.
--
Hi Max,
On 2023-02-26 at 02:11 -08, Max Nikulin wrote:
> As to `org-babel-screen-test' perhaps the issue is additional newline
> added after random number. I have not tried stepping through the
> function in debugger though.
I haven't either. I'll see if I can figure out the issue with the help
Hi Ihor,
On 2023-02-26 at 04:18 -08, Ihor Radchenko wrote:
>> +;; Reuse the variable assignment code from ob-shell
>> +(defalias 'org-babel-variable-assignments:screen
>> + 'org-babel-variable-assignments:shell)
>
> This will work, but you are relying on implementation detail of
> ob-shell.el. A
On Sun, Feb 26, 2023 at 4:04 PM Joshua Lambert
wrote:
> Remember to cover the basics, that is, what you expected to happen and
> what in fact did happen. You don't know how to make a good report? See
>
> https://orgmode.org/manual/Feedback.html#Feedback
>
> Your bug report will be posted t
22 matches
Mail list logo
