Emacs slow-down

Hi is it just me, or have other people also noticed hiccups when editing org files with org-mode (main from savannah). The moment I revert to the org-mode shipped with emacs master, editing returns to normal (and fluid). Would it make sense to take a closer look at this? Best, /PA -- Fragen

Re: R session error (org-babel)

On Wednesday, March 6th, 2024 at 05:56, Esteban Venialgo wrote: > I tried the =emacs -Q=, and still get the same problem. Before exporting the > code, I ran this lisp from the scratch pad: > > ;; enable language support for R > (org-babel-do-load-languages > 'org-babel-load-languages > '((R .

[BUG] With R using ":var d=data" breaks ":colnames yes" [9.7-pre (release_9.6.10-881-g595a32]

Hello, It seems that using ":var d=data" breaks ":colnames yes" in the header of an R code block. In the example below the first code block uses ":colnames yes" and gives the correct output, the second code block uses ":var d=data" to read the data in the table (although it read the header as

Re: noweb-start and noweb-end header args

Amy Grinn writes: > Ihor Radchenko writes: > >> Amy Grinn writes: >> >>> I would like to add support for setting 'org-babel-noweb-wrap-start and >>> 'org-babel-noweb-wrap-end for each src block individually >> >> May you please explain the use case when changing the default values >> is

Re: To avoid zero width space: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > However to produce clean export result elements should not be > added if no attributes are specified. My expectation is > > " > Example of intraword markup > " With the latest commit now the anonymous variant without attributes simply returns the content (in LaTeX, HTML

[BUG] ob-shell async incorrect table and value results

#+name: sync table #+begin_src sh :session *test* :results table echo "hello world" #+end_src #+RESULTS: | hello world | #+name: async table #+begin_src sh :session *test* :results table :async t echo "hello world" #+end_src #+RESULTS: : hello world #+name: sync value #+begin_src sh :session

Re: To avoid zero width space: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > However to produce clean export result elements should not be > added if no attributes are specified. My expectation is > > " > Example of intraword markup > " It seems like a good idea to me. Currently, in LaTeX: &_{lorem ipsum dolor} ==> LaTeX ==> lorem ipsum dolor It

Bug: file names capitalised when using gnuplot [9.3 (release_9.3 @ /usr/share/emacs/27.1/lisp/org/)]

Hello, A bug occurs when plotting data from an Org table using Gnuplot. An example is given below. In the first code block the plot is produced as expected, but in the second code block (where I have changed a lowercase "c" to an uppercase "C") gnuplot tries to plot data from a non-existent

To avoid zero width space: Re: Experimental public branch for inline special blocks

On 02/03/2024 03:34, Juan Manuel Macías wrote: Finally, I have made public on GitLab my experimental branch for the new (possible) inline-special-block element: The new feature is promising as an alternative for U+200B zero width space as an

Re: noweb-start and noweb-end header args

Ihor Radchenko writes: > Amy Grinn writes: > >> How much does org mode modify the fontification for an indirect buffer? >> Without having looked into it, I assume not much or at all. >> ... I think >> that approach could be more complex, especially when dealing with a >> theoretically infinite

Re: smallcaps: Re: Experimental public branch for inline special blocks

Max Nikulin writes: > OK, just consider it as my dissenting opinion. I believe that it should > be possible for the same Org document > >#+options: inline-special-block-aliases:(("definition" :smallcaps t)) > >{Example} or &_[:smallcaps t]{ad-hoc} > > to export it as > >Example >

Re: Provide sane default for the @direntry

> The patches are against Emacs git repository, not against Org mode. May > your please port them? See attached. >> Subject: [PATCH 1/2] * lisp/org/ox-texinfo.el: Remove redundant `:group`s > By our convention, we drop leading * in the first line of the commit message. Done. >> *

cannot export asynchronously because of org-fold-core--update-buffer-folds

Hello, I’m trying to export a file asynchronously to beamer/pdf, and I have a strange error. Here is the contents of the *Org Export Process* buffer: Debugger entered--Lisp error: (void-function org-fold-core--update-buffer-folds) org-fold-core--update-buffer-folds() #f(compiled-function ()

Re: noweb-start and noweb-end header args

Amy Grinn writes: >> This sounds like XY problem then. >> If the real problem you want to solve is fontification, we may instead >> adjust Org mode fontification of source blocks to exclude noweb >> references. > > I see a problem with multiple possible solutions, some more involved > than

Re: Feature request: IDs for everything

Oh, that's great news! Will be very useful; thanks Ihor! Unfortunately life has come in the way so I haven't had the chance to pursue this further at the moment. All the best, Tor On Wed, 06/03/2024, Ihor Radchenko wrote: > Tor Erlend Fjelde writes: > >>> As an alternative option, we had a

Re: noweb-start and noweb-end header args

Ihor Radchenko writes: > Amy Grinn writes: > #+name: firewall #+begin_src sh :noweb yes :noweb-start <<< :noweb-end >>> >>> >>> May you please explain the use case when changing the default values >>> is useful? >> >> Of course! Changing the default values can be useful to prevent

Re: Feature request: IDs for everything

Tor Erlend Fjelde writes: >> As an alternative option, we had a proposal that extends id: links to >> have a search option: >> >> [[id:::search-string]] > ... > Indeed; I was actually about to have a go at implementing this because > I thought this would be the quickest way of adding support

Re: noweb-start and noweb-end header args

Amy Grinn writes: >>> #+name: firewall >>> #+begin_src sh :noweb yes :noweb-start <<< :noweb-end >>> >> >> May you please explain the use case when changing the default values >> is useful? > > Of course! Changing the default values can be useful to prevent syntax > highlighting errors in a

Re: noweb-start and noweb-end header args

Ihor Radchenko writes: > Amy Grinn writes: > >> I would like to add support for setting 'org-babel-noweb-wrap-start and >> 'org-babel-noweb-wrap-end for each src block individually using the >> header args :noweb-start and :noweb-end: >> ... >> #+name: firewall >> #+begin_src sh :noweb yes

Re: noweb-start and noweb-end header args

Amy Grinn writes: > I would like to add support for setting 'org-babel-noweb-wrap-start and > 'org-babel-noweb-wrap-end for each src block individually using the > header args :noweb-start and :noweb-end: > ... > #+name: firewall > #+begin_src sh :noweb yes :noweb-start <<< :noweb-end >>> May

Re: Provide sane default for the @direntry

Stefan Monnier writes: > New version of the patch, which I believe address your comments. Thanks! The patches are against Emacs git repository, not against Org mode. May your please port them? See some more minor comments inline. > Subject: [PATCH 1/2] * lisp/org/ox-texinfo.el: Remove

Re: R session error (org-babel)

hi Bill, I tried the =emacs -Q=, and still get the same problem. Before exporting the code, I ran this lisp from the scratch pad: ;; enable language support for R (org-babel-do-load-languages 'org-babel-load-languages '((R . t) (shell . t) (latex . t) (emacs-lisp . nil))) (setq

Re: smallcaps: Re: Experimental public branch for inline special blocks

On 06/03/2024 00:28, Juan Manuel Macías wrote: Max Nikulin escribió: I think that the current implementation is very flexible and gives rise to many possible variations, and the combination of direct formatting and styles to suit the user. OK, just consider it as my dissenting opinion. I

Re: naming: Re: Experimental public branch for inline special blocks

Max Nikulin writes: >> Custom inline markup. > > "Markup" is something abstract to my taste. I would prefer something > related to concrete instances of such objects. IMHO, the whole point of the discussed construct is exactly being abstract and multi-purpose. > Decorators sometimes stressed

Re: [FR] multiple column view definition

Slawomir Grochowski writes: >> It looks like you are asking for a way to choose between multiple column >> specs when building column view. And that you have a very specific idea >> how to implement it. However, the details of the idea are elusive to me. >> May you elaborate? > > Sure. > > We

Re: naming: Re: Experimental public branch for inline special blocks

On 05/03/2024 00:29, Ihor Radchenko wrote: Max Nikulin writes: Does anybody have an idea of a better name for a feature? Maybe something like inline custom objects, snippets. "Objects" are used to describe syntax, but not used in the manual though. Custom inline markup. "Markup" is

Re: org id link to arbitrary place in an org file

Samuel Wales writes: > i know we talked about something like this recently, perhaps related > to inline tasks, perhaps not. apologies redundancy. > > i'd like to have an org-id link to a place in a different file. a > paragraph or even more arbitrary. > > is this possible with current org

Re: R session error (org-babel)

Esteban Venialgo writes: > hi Org-people, > > I'm a newbie with org-babel, but I think I'm facing a bug for R code > execution. Basically, I have a simple code for testing: > ... > Debugger entered--Lisp error: (wrong-type-argument stringp nil) > org-babel-R-initiate-session... As William

Re: [BUG] org-mobile: Arguments of expand-file-name are flipped [9.6.20 ( @ /home/fb/.config/emacs/elpa/org-9.6.20/)]

Fabian Brosda writes: > just a very small issue I found, as I was wondering, why the agendas > file was included in the index, although it did not exist. > > The problem is in org-mobile.el in Line 473, as the arguments to > expand-file-name are in the wrong order: > > (when (file-exists-p

Re: nested blocks in org

mahmood sheikh writes: > with the given minimal example: > ``` > #+begin_parent > #+begin_child > #+end_child > #+end_parent > ``` > the code > ```lisp > (org-block-map (lambda () (message "elem: %s" (org-element-at-point > ``` > goes through only the parent element and doesnt run the lambda