[QUESTION] How to specific image size attributes under headline scope?

There is attributes setting above image link to specify image inline preview size. Like this: #+begin_src org ,#+ATTR_ORG: :width 500 ,#+ATTR_LATEX: :width 5.0in ,#+ATTR_HTML: :width 500px [[file:kk/88320740_p0.jpg]] #+end_src When I put it on beginning of org document, then preview inline

Re: Supported Emacs version

Hi Timothy, Timothy writes: > Personally I’m more inclined towards an all-or-nothing approach. I understand this inclination but I disagree. Org is made of many areas and partial backward-compatibility can still be useful. When people report compatibility problems with Emacs <26, we can

Re: Supported Emacs version

Hi Bastien, >> I’m tempted to make some patches to remove all the Emacs < 26 >> compatibility code if we no longer need it. What do you think? > > We should NOT remove this code: many people probably use/need it. > > Anything that helps keeping Org compatible with Emacs < 26 is > still useful,

Re: Supported Emacs version

Hi Timothy, Timothy writes: > I’m tempted to make some patches to remove all the Emacs < 26 > compatibility code if we no longer need it. What do you think? We should NOT remove this code: many people probably use/need it. Anything that helps keeping Org compatible with Emacs < 26 is still

Supported Emacs version (was: [PATCH] Fix window width when line numbers present)

Hi Bastien, > Our commitment is that the latest Org version is compatible with the > last three stable versions of Emacs. > > So when Emacs 28 and Org 9.6 are both out, we guarantee that Org is > compatible with Emacs 28, 27 and 26. > > Does that explain it better? Thanks for clarifying. That’s

Re: Dodgy Worg publishing?

Hi Bastien, > You can check the output of Worg publishing process here: > > Ah cool, thanks for pointing that out. > The latest build contains a line showing that library-of-babel.org > does not export: > >

Re: [PATCH] Fix window width when line numbers present

Hi Timothy, Timothy writes: > So I take this to mean that we will now assume that Org 9.6+ will target Emacs > 29? This seems reasonable to me, but doesn’t quite accord with how I read > . Our commitment is that the latest Org

Re: [PATCH] Fix window width when line numbers present

Hi Bastien, > We can safely assume that Org 9.6 will be released after Emacs 28, so > let’s use `line-number-display-width’ on main. So I take this to mean that we will now assume that Org 9.6+ will target Emacs 29? This seems reasonable to me, but doesn’t quite accord with how I read

[FR] org-babel-examplify-region does not add a newline for the example block end

Hello, I've been testing out org-babel-examplify-region in my bookshelf file to mark excerpts from books, but there's an issue I have encountered. If there is a #+end_example after the currently marked region, once you run org-babel-examplify-region, it does not create a #+end_example at the

Where does CDATA come from?

Hello, I am customizing my org-mode installation but there is something that I don't understand. When I execute the following statement: ``` (setq org-html-mathjax-template " MathJax.Hub.Config({ displayAlign: \"%ALIGN\", displayIndent: \"%INDENT\", \"HTML-CSS\": {

[FR] Expand functionality of org-hide-block-startup to add property drawer support

Hello, I recently came across the /hideblocks /and /nohideblocks/ startup variables for per-file configuration of org-hide-block-startup in the manual at 2.8 Blocks. I got it to work by using a header argument, but I think this would really benefit from being able to be set through a

Re: [PATCH] Fix window width when line numbers present

Hi Matt, Matt Huszagh writes: > Bastien writes: > >> See https://orgmode.org/worg/org-maintenance.html#emacs-compatibility > > Ah, my mistake. Thanks for pointing me to that. So does this stay on > some other branch until the Emacs official release is at 28? We can safely assume that Org 9.6

Re: Dodgy Worg publishing?

Hi Timothy and Thomas, Timothy writes: > Thanks for catching this problem. To me this looks more like a > problem with the worg publishing than an outdated link. I’ve cc’d > Bastien as he’s much more familiar with the Worg publish process > than I am. You can check the output of Worg

Re: Org ELPA: does not include 9.5 as expected, archives appear largely identical?

Hi Nicolas, Nicolas Goaziou writes: >> Org 9.5.1 is planned to be the last stable version before the final >> merge into the Emacs 28 branch, so I will ping the Emacs maintainers >> first -- thanks for the reminder! > > Another possibility is to release Org 9.5.1 and make Org 9.5.2 (or > 9.5.3,

Re: [PATCH] Fix window width when line numbers present

Nicolas Goaziou writes: > `line-number-display-width’ is Emacs 26+. So I guess it is unfortunately > not acceptable on main branch. Ooops, thanks for picking that up Nicolas. I see we actually have ┌ │ (if (fboundp 'line-number-display-width) │ (defalias 'org-line-number-display-width

Re: org-sort random

On 11/22/21 07:40:35 +0530, Vikas Rawal wrote: > I am trying to sort a sub-tree of headings randomly. But `C-c ^ f > random RET` asks for a "function for comparing keys". What am I > supposed to do? Here's the prompt: Function for comparing keys (empty for default `sort-subr' predicate): And

org-sort random

I am trying to sort a sub-tree of headings randomly. But `C-c ^ f random RET` asks for a "function for comparing keys". What am I supposed to do? Reference: https://lists.gnu.org/archive/html/emacs-orgmode/2011-02/msg00089.html I have also tried the custom function proposed in the previous

org-cite support merged for Doom biblio module

Just a head's up that org-cite support for the Doom Emacs biblio module is now merged. Currently works best with the new, and now default, vertico completion module, which uses my citar package. So basically, make sure the following are uncommented in your init.el file: - biblio - vertico - org

Re: [PATCH] Fix window width when line numbers present

Bastien writes: > See https://orgmode.org/worg/org-maintenance.html#emacs-compatibility Ah, my mistake. Thanks for pointing me to that. So does this stay on some other branch until the Emacs official release is at 28? Matt

Re: [PATCH] Fix window width when line numbers present

Hi Matt, Matt Huszagh writes: > Nicolas Goaziou writes: > >> `line-number-display-width' is Emacs 26+. So I guess it is unfortunately >> not acceptable on main branch. > > Does org-mode not require 26+ even though the Emacs official release is > on 27? See

Re: [PATCH] Fix window width when line numbers present

Nicolas Goaziou writes: > `line-number-display-width' is Emacs 26+. So I guess it is unfortunately > not acceptable on main branch. Does org-mode not require 26+ even though the Emacs official release is on 27? Matt

Re: [PATCH] Fix window width when line numbers present

Hello, Timothy writes: > Thanks for this patch. I wasn’t aware of `line-number-display-width' when I > wrote > that, but it looks like a better fit than my `(or ... 0)' statement. As such, > I’ve > just applied your patch as cd3e138, tweaking the commit message to no longer > go > over the

Re: [PATCH] Fix regex for determining image width from attribute

Timothy writes: > Once again, thank you for the patch. The fact that the current regexp matches > `#+attr_latex' and `#+attr_html' is in fact by design though*. This is > because I > consider it safe to assume that a `#+attr_*' which gives non-integer width > between > 0 and 2 can be safely

[BUG] org-element--cache: Cache corruption [9.5, (release_9.5-255-g54da1d @, c:/Users/micha/AppData/Roaming/.emacs.d/org-new/org-mode/lisp/)]

Error message: "Warning (emacs): org-element--cache: Cache corruption detected in emacs-config-prog-modes.org. Resetting.  The error was: (error "rx ‘**’ range error")  Backtrace: nil  Please report this to Org mode mailing list"" Done. mp Emacs  : GNU Emacs 29.0.50 (build 1,

Re: [PATCH] Fix regex for determining image width from attribute

Hi Matt, > A recent patch started computing the inline image width from any attr_ > line. This is incorrect, as it matches settings like attr_latex, or > attr_html. We only want to look for settings specifically for the org > buffer. This patch fixes that. Once again, thank you for the patch.

Re: [PATCH] Fix window width when line numbers present

Oops, I forgot to mark this patch as applied for updates.orgmode.org. Done in this message.

Re: [PATCH] Fix window width when line numbers present

Hi Matt, > This is a very small patch that I believe fixes a previous, incorrect > fix for computing the window text area when line numbers are > present. The previous fix seemed to assume that > display-line-numbers-width being nil meant that this means line numbers > are not present. However,

[PATCH] Fix regex for determining image width from attribute

Hi, A recent patch started computing the inline image width from any attr_ line. This is incorrect, as it matches settings like attr_latex, or attr_html. We only want to look for settings specifically for the org buffer. This patch fixes that. Thanks Matt >From

[PATCH] Fix window width when line numbers present

Hello, This is a very small patch that I believe fixes a previous, incorrect fix for computing the window text area when line numbers are present. The previous fix seemed to assume that display-line-numbers-width being nil meant that this means line numbers are not present. However, it can also

Re: c47b535bb origin/main org-element: Remove dependency on ‘org-emphasis-regexp-components’

On 21/11/2021 17:01, Ihor Radchenko wrote: Max Nikulin writes: My draft version is attached. Ihor, thank you for inspiration. Feel free to improve it. I hope, it makes problem more apparent to user who tries to customize markers. Have I missed some undesired side effects? Unfortunately with

org-critical-edition (new version)

Hi all, For philologists who might be interested, I have uploaded a new version of my package `org-critical-edition', with some new features, such as the ability to use multi-level nested critical notes: https://gitlab.com/maciaschain/org-critical-edition It occurred to me to write

Re: [PATCH] Accept more :tangle-mode specification forms

Hi Tim, Thanks for the way in which you’ve responded to my comments. I appreciate the effort you’ve gone to to explain your views as opposed to simply saying you disagree with some of my current thoughts :) Tim Cross writes: > My suggestion is simply to look at the value and if it is not a

Re: [PATCH] Accept more :tangle-mode specification forms

Timothy writes: > Hi Tim, > >>> The parsing of “555” to the integer 555 is done by >>> org-babel-parse-header-arguments, and so can’t really be changed. >> >> I don't understand this. Why can't it be changed? > > Well, it can't be changed without changing > org-babel-parse-header-arguments,

Re: A mobile clocking solution?

Hi Marcin, There's an open pull request on github that has a working implementation for clocking in and out. There's a few ui things to fix. I'm running that branch at the moment and it works quite well. -Dan On Sun, 21 Nov 2021, 12:17 Marcin Borkowski, wrote: > Hi all, > > AFAIK, there are a

Re: [PATCH] Fontification for inline src blocks

Hi All, Since the contentious component of my previous patches has been the `{{{results()}}}' prettification, I’ve prepared an alternate version that I’m hoping everybody will be fairly happy with (fingers crossed!) that tosses out the results prettification for now. I think Protesilaos’

Re: [BUG] error on org-element--cache-process-request when TAB indent region select properties drawer

Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> I can't reproduce it with clean Emacs config. And my option >> ~org-adapt-indentation~ is ~nil~. And this >> error is not raised every time. Just some org buffer and sometimes. Have not >> noticed some regular >> pattern of problem

[SOLVED] Re: [BUG] error on org-element--cache-process-request when TAB indent region select properties drawer

Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> I can't reproduce it with clean Emacs config. And my option >> ~org-adapt-indentation~ is ~nil~. And this >> error is not raised every time. Just some org buffer and sometimes. Have not >> noticed some regular >> pattern of problem

Re: Merging ox-texinfo+ into ox-texinfo

Hello, Jonas Bernoulli writes: > Of course. I probably used the separate keyword because all the entries > for ox-texinfo's :options-alist did that too, but if that's not how this > is usually done for booleans, then I see no reason not to change it. More precisely, there's an historical

Re: [BUG] org-agenda-get-scheduled in 2e99997 ignores org-todo-keywords [9.5 (release_9.5 @ /home/ning/.emacs.d/.local/straight/build-27.1/org-mode/)]

Dear Ihor, Sorry, please ignore my previous report. In a fresh install of emacs, I cannot replicate this bug in 2e7. Best regards, Ning Yuan On Sun, Nov 14, 2021 at 12:07 PM Ihor Radchenko wrote: > > - External Email - > > > > Ning Yuan writes: > > > A few days ago I updated

A mobile clocking solution?

Hi all, AFAIK, there are a few mobile Org-mode apps for Android (I know about organice and Orgzly). From a skim of their docs I think they don't support clocking. Is that correct? If so, are there any mobile apps supporting clocking on a phone? TIA, -- Marcin Borkowski http://mbork.pl

Re: Org ELPA: does not include 9.5 as expected, archives appear largely identical?

Hello, Bastien writes: > Org 9.5.1 is planned to be the last stable version before the final > merge into the Emacs 28 branch, so I will ping the Emacs maintainers > first -- thanks for the reminder! Another possibility is to release Org 9.5.1 and make Org 9.5.2 (or 9.5.3, or...) the last

Re: c47b535bb origin/main org-element: Remove dependency on ‘org-emphasis-regexp-components’

Max Nikulin writes: > My draft version is attached. Ihor, thank you for inspiration. Feel free > to improve it. I hope, it makes problem more apparent to user who tries > to customize markers. Have I missed some undesired side effects? Your version looks a lot better. Thanks! > Unfortunately

Re: [BUG] error on org-element--cache-process-request when TAB indent region select properties drawer

"Christopher M. Miles" writes: > I can't reproduce it with clean Emacs config. And my option > ~org-adapt-indentation~ is ~nil~. And this > error is not raised every time. Just some org buffer and sometimes. Have not > noticed some regular > pattern of problem reason yet. If I found any clue I

Re: [PATCH] Re: c47b535bb origin/main org-element: Remove dependency on ‘org-emphasis-regexp-components’

Nicolas Goaziou writes: > Thanks for the update, and apologies in advance for being bold, as > I have some additional comments about it. Constructive critics and suggestions are always welcome. And we do not have pressing deadlines here :) >> * doc/org-manual.org (Emphasis and Monospace):

Re: Is mouse necessary when working with PDF?

Ypo writes: > What tool do you use to highlight PDF? Do you copy your highlights to a > .org file? > > I use org-noter, but it seems the mouse is necessary to work with PDF. I haven't seen proper packages, but there is some custom code in

Re: table and Cyrillic characters: org-element--cache: Unregistered buffer modifications detected. Resetting

Max Nikulin writes: >>> By "|" I mean Shift+\ that inserts "/" with russian-computer input method. >> >> I pushed yet another workaround. >> >> That part of code is turning into one giant FIXME and I do not see >> anything better than patching Emacs itself. Hopefully, not many more >> built-in

Re: [BUG] C-c C-* causes "org-element--cache: Unregistered buffer modifications detected."

Max Nikulin writes: > Ihor, I am sorry, but I am still getting the error > > LANG=en_US.UTF-8 emacs -Q -L ~/src/emacs/org-mode/lisp/ new.org > > C-\ russian-computer RET > A > C-* > > Latin "A" to type Cyrillic "Ф" Apparently, C-* on > Ф Put cursor on this line and hit =C-c C-*= to make it a

Re: [BUG] error on org-element--cache-process-request when TAB indent region select properties drawer

Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> The bellowing error often raised when I region select multiple headlines >> which contains properties >> drawer >> >> #+begin_src org >> |*** headline 1 >> :PROPERTIES: >> :kkk: 2 >> :END: >> >> ,*** headline 2 >>

[ANSWERED] Re: [BUG] (org-element-context) on some link does not return search-option correctly

Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> When I put point on an custom org link: >> >> #+begin_src org >> [[pdf:~/Org/Wiki/Computer Technology/Programming/Programming >> Languages/Clojure/data/Books/Clojure >> 经典实例.pdf::40++0.00][Clojure经典实例.pdf: Page 40]] >> #+end_src >>

Re: clock doesn't respect org-id-link-to-org-use-id

Dave D writes: > I have :link t so that I can jump to a task directly from the clock > table. I have noticed that sometimes the link doesn't work because of > a heading having strange characters ( in my case my heading is > suffixed with date time). Thanks for reporting! Could you provide an

Re: Bug: Org Agenda [9.4.6 (9.4.6-gab9f2a @ /home/rh-2015/.emacs.d/elpa/org-9.4.6/)]

hellbru...@web.de (Reiner Hellbrück) writes: > A friendly hello, Also friendly, albeit delayed hello back :) > since the change to > > Org mode version 9.4.6 (9.4.6-gab9f2a @ > /home/rh-2015/.emacs.d/elpa/org-9.4.6/) > > the Org-Agenda is not produced. Let's say your org-file 'Test.org'