Re: Replace Org's C-TAB with C-M-TAB - objection?

2020-05-26 Thread Vladimir Nikishkin
I'd rather support this change, as I don't have TAB on my keyboard, I use C-i instead of TAB OTOH, C-M-i , which is essentially M-TAB, and essentially what the changes is supposed to be, if flyspell-auto-correct-word (found in flyspell-mode-map) So, if this change is made, and flyspell is turned

Re: Bug: why does org-goto call org-latex-preview?

2020-05-26 Thread Kyle Meyer
Ihor Radchenko writes: >> It looks like an oversight to me. I think >> org-startup-with-latex-preview should be let-bound to nil around >> org-goto-location's call to org-mode. Likewise, I'd say that >> org-startup-with-inline-images and org-startup-shrink-all-tables should >> be let-bound to

Re: Bug: why does org-goto call org-latex-preview?

2020-05-26 Thread Ihor Radchenko
> It looks like an oversight to me. I think > org-startup-with-latex-preview should be let-bound to nil around > org-goto-location's call to org-mode. Likewise, I'd say that > org-startup-with-inline-images and org-startup-shrink-all-tables should > be let-bound to nil. Is there even a need to

Re: Bug: why does org-goto call org-latex-preview?

2020-05-26 Thread Kyle Meyer
Vladimir Nikishkin writes: > Why is it that org-goto enforces the regeneration of previews in a buffer? It looks like an oversight to me. I think org-startup-with-latex-preview should be let-bound to nil around org-goto-location's call to org-mode. Likewise, I'd say that

Re: org-babel block with :exports code that gets evaluated on export

2020-05-26 Thread Matthew Lundin
S├ębastien Miquel writes: > Is there a way to have an org-babel block which only exports its code > but still gets evaluated when exporting ? I think you can do something like this: #+begin_src emacs-lisp :exports both :results none (setq my-variable t) #+end_src Or, if you want to

Bug: why does org-goto call org-latex-preview?

2020-05-26 Thread Vladimir Nikishkin
Hello, everyone! Below is an excerpt of the profiler report after typing C-c C-j: - command-execute2385 76% - call-interactively2385 76% - funcall-interactively

Re: [PATCH] test-ob-tangle.el: Fix dirty repo state caused by testing

2020-05-26 Thread Kyle Meyer
Kevin Foley writes: > The attached patch kills the buffer of the file modified > during testing to prevent leaving the repo in a dirty state. Thanks. I applied it in 7a2b785d6 with a small tweak so that a buffer rather than a buffer name is passed to kill-buffer. In the context of the tests,

[PATCH] test-ob-tangle.el: Fix dirty repo state caused by testing

2020-05-26 Thread Kevin Foley
The attached patch kills the buffer of the file modified during testing to prevent leaving the repo in a dirty state. Thanks to Kyle for seeing this and providing guidance on how to address. Thanks, Kevin >From 46dd1cf3c34a372612e4a67a79afd84ca3317500 Mon Sep 17 00:00:00 2001 From: "Kevin J.

Re: ISSUE: org publish document processor silently inserts licensed content into targets by default

2020-05-26 Thread Anthony Carrico
On 5/22/20 11:10 AM, Bastien wrote: > If you think it is useful as a patch against Org, not just as a way to > customize a setup, can you send a patch? > > See https://orgmode.org/worg/org-contribute.html on how to contribute. Ok, it is on my list, thanks. -- Anthony Carrico

Re: Migrating from HUGO to org-publish

2020-05-26 Thread James R Miller
Alejandro, Have you tried ox-hugo? There's an org exporter to Hugo. I use it and it works pretty much flawlessly. -- James Miller james.ryland.mil...@gmail.com

Re: org-archive-all-matches doesn't use org-archive-default-command

2020-05-26 Thread Matthew Lundin
Hi Thomas, Thomas Schaper writes: > When playing around with org-archive, I noticed that the function > org-archive-all-matches doesn't use org-archive-default-command but > calls org-archive-subtree directly. Is there any reason for this, or is > it simply a small bug/missing feature? I think

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread Nicolas Goaziou
Hello, TEC writes: > Ok, I think this is everything except for except putting (length > contents) in a let binding. I don't mind if you edit a let binding > into the patch, I'm just struggling to overcome a feeling that it's > a bit silly adding a binding for a short, simple function called >

Re: issue tracker?

2020-05-26 Thread Matthew Lundin
Anthony Carrico writes: > Given that the mailing list holds the issues, it would be nice if you > could import the mailing list into your client as a lump (maildir/mbox). > Currently you can only download it chunk by chunk, so it isn't really > practical for a newcomer to import the whole

Re: [PATCH] ob-plantuml: Support for plantuml as well as the current java+jar solution

2020-05-26 Thread Terje Larsen
Hello Bastien, I have now signed the FSF papers. Here is the updated patch on top of current master. Let me know if all looks good or if I need to make further changes or need to provide something else. Best regards, Terje On Mon, Feb 17, 2020 at 12:29 AM Bastien wrote: > > Hi Terje, > >

Re: issue tracker?

2020-05-26 Thread Matthew Lundin
Detlef Steuer writes: > How to add more now? Same here. Mail is functionally superior to a lot > of modern solutions. > > A Bugtracker you do not use on a regular basis often is a horrible time sink. > Plus, most of the time you need just another account for a site you > never wanted an account

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread John Kitchin
Timothy writes: > Nicolas Goaziou writes: > >> Thank you. It looks fine, I will only be nitpicking. > > Nitpick away :D > >>> +(defun org-edit-latex-fragment () >>> + "Edit LaTeX fragment at point." >>> + (interactive) >>> + (let* ((context (org-element-context)) >>> +(_ (unless (and

Re: [bug] Should #+attr_latex affect image display within the org buffer itself?

2020-05-26 Thread John Kitchin
I think another way to do it is to have an #+attr_org: :width as the first attribute. Vladimir Nikishkin writes: > At the moment, I'm working around this by setting the width in "TeX points": > > #+attr_latex: :width 224pt > > The exported image becomes 224 points wide (roughly 8 cm), and the

Re: ical2org.awk

2020-05-26 Thread Eric S Fraga
On Friday, 22 May 2020 at 16:14, Bastien wrote: > I see there is > https://github.com/msherry/ical2org/blob/master/ical2org.awk Interesting. I hadn't been aware of that fork. > so perhaps hosting the code on worg/code/ is not so useful > anymore? I don't really have a strong opinion about

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread TEC
Ok, I think this is everything except for except putting (length contents) in a let binding. I don't mind if you edit a let binding into the patch, I'm just struggling to overcome a feeling that it's a bit silly adding a binding for a short, simple function called twice. Let me know if

Re: issue tracker?

2020-05-26 Thread Robert Pluim
> On Mon, 25 May 2020 13:20:30 +0200, Roland Everaert > said: Roland> No, I was not aware of it. Yet, if I understand the objective of the Emacs Roland> ML and Debbugs, it is for, when you have a crash with emacs or, at least, Roland> an error stack trace when evaluating

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread TEC
Nicolas Goaziou writes: Without hesitation, the first form is nicer. The second one is just abusing let-binding. I die a little just by looking at it. I'll make an attempt to avoid killing you then :P See `rx' macro. S-exp regexps are usually easier to read (after an initial struggle),

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread Nicolas Goaziou
Timothy writes: > I had a look at that, to me this was cleaner than using multiple let > bindings, like so > > (let ((context ...)) > (unless ... user error) > (let* ((contents ...) > (delim-length ...)) >... > > vs. > > (let* ((context ...) >(_ (unless ... user error))

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread Timothy
Nicolas Goaziou writes: > Thank you. It looks fine, I will only be nitpicking. Nitpick away :D >> +(defun org-edit-latex-fragment () >> + "Edit LaTeX fragment at point." >> + (interactive) >> + (let* ((context (org-element-context)) >> + (_ (unless (and (eq (org-element-type context)

Re: [patch suggestion] Mitigating the poor Emacs performance on huge org files: Do not use overlays for PROPERTY and LOGBOOK drawers

2020-05-26 Thread Nicolas Goaziou
Hello, Ihor Radchenko writes: > I have five updates from the previous version of the patch: Thank you. > 1. I implemented a simplified version of element parsing to detect > changes in folded drawers or blocks. No computationally expensive calls > of org-element-at-point or

Re: (Feature Request) have org-edit-special work inside non-environment LaTeX blocks, i.e. \( \) and \[ \]

2020-05-26 Thread Nicolas Goaziou
Hello, TEC writes: > --- > lisp/org-src.el | 45 + > lisp/org.el | 1 + > 2 files changed, 46 insertions(+) Thank you. It looks fine, I will only be nitpicking. > +(defun org-edit-latex-fragment () > + "Edit LaTeX fragment at point." > +

Using font-lock to align tags in org buffers

2020-05-26 Thread Ihor Radchenko
Hello, Currently, org does tag alignment by adding a number of spaces before the tags. This becomes messy when one changes the window size and turns off line truncation. I came up with an experimental code utilising 'display text property and font-lock to align tags dynamically, as you resize