[feature request] make yank-media backed by `org--image-yank-media-handler` support hashing image in clipboard as filename

I hope the `yank-media` backed by `org--image-yank-media-handler` support hashing image in clipboard as filename, so that the function `org--image-yank-media-handler` can detect whether the clipboard image already exists. Here is my PoC which is not finished. Hope someone can complete it. ;;; Use

Re: [Feature Request] Adding custom indices for Texinfo export (and maybe unaffiliated dual-value keywords?)

Ihor Radchenko writes: > Rudolf, did you have a chance to look into this request? Sorry, I did not reply because I had nothing to add. The feature would be useful, and it all comes down to /not/ adding yet another snowflake to the already complicated Org syntax. Rudy -- "'Contrariwise,' conti

Re: [Feature Request] Adding custom indices for Texinfo export (and maybe unaffiliated dual-value keywords?)

Ihor Radchenko writes: >> Texinfo allows one to create new named indices using `@defindex NAME`, >> which can then be used via `@NAMEindex`. I have been experimenting with >> different ways of supporting this. > > Looks like a reasonable addition. > CCing the new ox-texinfo maintainer. He migh

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Thank you. On Sun, 30 Mar 2025, 00:59 Ihor Radchenko, wrote: > Daan Ro writes: > > >> Maybe we should use 'separator property in the proposed values? > > > > Added, I was just afraid that bit is more unstable than the variable > > name. > > Applied, onto main, with minor amendments to the commi

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

I defined org-cite-basic--crm-indicate-prompt, equivalent to "[list separated by ;;] %(prompt)" by default. Daanturo On Mar 29 2025, at 9:46 pm, Ihor Radchenko wrote: > Daan Ro writes: > > > Wait, Emacs 31 has added `crm-prompt' for CRM indication: > > > > https://yhetil.org/emacs/874j16hriz...

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: >> Maybe we should use 'separator property in the proposed values? > > Added, I was just afraid that bit is more unstable than the variable > name. Applied, onto main, with minor amendments to the commit message and changing (when (<= (length dyn-sep) (length (match-string 0)))

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

> Maybe we should use 'separator property in the proposed values? Added, I was just afraid that bit is more unstable than the variable name. > We can instead just check for (boundp 'crm-prompt) Admittedly specifying Emacs version out loud is not beautiful, but I thought what if in the future the

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: > I defined org-cite-basic--crm-indicate-prompt, equivalent to > "[list separated by ;;] %(prompt)" by default. Thanks! > + :type > + '(choice > +(const :tag "Use \";;\" as the separator." "[ \t]*;;[ \t]*") > +(const > + :tag > + "Dynamically compute \";\"+ with

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: > Wait, Emacs 31 has added `crm-prompt' for CRM indication: > > https://yhetil.org/emacs/874j16hriz@daniel-mendler.de/T/#m2b8290e24cd133171e143f93720384dab7b112ee > https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=a8a4c3a091bc6ebab40db3b33f4d15bb1040dbcb > Since having b

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Wait, Emacs 31 has added `crm-prompt' for CRM indication: https://yhetil.org/emacs/874j16hriz@daniel-mendler.de/T/#m2b8290e24cd133171e143f93720384dab7b112ee https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=a8a4c3a091bc6ebab40db3b33f4d15bb1040dbcb Since having both only leads to unessenti

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: >> (completing-read >> (concat >> (if negate "Negative filter" "Filter") >> " [+cat-tag<0:10-/regexp/]: ") >> #'org-agenda-filter-completion-function >> nil nil ff) >> > > Right. Is 'Keys [citation1 ;; citation2 ;; ...]: ' fine? Or an Yup. > + (`dynamic > +

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

> We need to indicate which separator is used somehow. > > For example, here is what `org-agenda-filter' does in similar situation: > > (completing-read > (concat > (if negate "Negative filter" "Filter") > " [+cat-tag<0:10-/regexp/]: ") > #'org-agenda-filter-completion-function > nil nil ff) > Rig

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: >> `string-match-p' matching the strings directly. > A candidate may have multiple appearances, like > "Author A ;; Author B ;;; ..." > `string-match-p' would only find the first ";;" and miss > ";;;". I thought s.el's `s-match-strings-all' should be more robust but > we can't use

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

> >> > + ;; Handle regexp separator? > >> > >> Is it a TODO? > > You missed this question. Previously I didn't think of handling regexp-based separator argument, but then since you said > regexp-opt will be safer if separator happens to be something like > ".". so I opted to always assume litera

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: >> Would you consider it? See >> https://orgmode.org/worg/org-contribute.html#copyright > > I have already done the copyright assignment. Oops. Right. I did not search by email, and you are listed under slightly different name there. >> > + (let* ((cands (hash-table-keys complet

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

> Would you consider it? See > https://orgmode.org/worg/org-contribute.html#copyright I have already done the copyright assignment. > Please add a proper commit message, if you can. > We also need an ORG-NEWS entry announcing the new customization. > "carefully set craft regexp..." reads as if Or

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

First of all, thanks for providing a patch! However, please note that I cannot accept patches exceeding 15-20LOC without copyright assignment. Would you consider it? See https://orgmode.org/worg/org-contribute.html#copyright Some comments on the patch below. > Subject: [PATCH] org-cite-basic-c

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

I've just recalled a limitation of CRM while testing: the separator must not be part of the completion candidate strings. "," and ";" are common in the authors field, other punctuations may appear in article names, too. Perhaps that's reason CRM wasn't used by oc-basic.el in the first place? Daant

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

> We can use something like ;; as a separator or even compute it > dynamically depending on the actual completion candidates (; if no > candidates contain ;, ;;, ;;;, etc) How does this look? I haven't known a function to reliably query all completion candidates from a completion table of regardle

Re: [Feature Request] Adding custom indices for Texinfo export (and maybe unaffiliated dual-value keywords?)

Okamsn via "General discussions about Org-mode." writes: > Texinfo allows one to create new named indices using `@defindex NAME`, > which can then be used via `@NAMEindex`. I have been experimenting with > different ways of supporting this. Looks like a reasonable addition. CCing the new ox-t

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

My apology for the late reply. > An alternative could be using `completing-read-multiple' where you can > enter, for example, comma-separated list of citations or a single > citation as you prefer. This is an improvement over ther current input loop, I think. > > In Latex, \cite is also more comm

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: > I've just recalled a limitation of CRM while testing: the separator must > not be part of the completion candidate strings. "," and ";" are common > in the authors field, other punctuations may appear in article names, > too. Perhaps that's reason CRM wasn't used by oc-basic.el

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

> How does \cites have anything to do with interactive selection of > multiple citations at once? An analogy, especially when exporting. Single selection of a citation -> \cite, multiple selections -> \cites. > That's what I am leaning to - modifying oc-basic.el rather than oc.el > itself. Thank

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: >> How does \cites have anything to do with interactive selection of >> multiple citations at once? > > An analogy, especially when exporting. Single selection of a citation > -> \cite, multiple selections -> \cites. This is a strange analogy. It is extremely common to cite multi

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: >> > In Latex, \cite is also more commonly used and more asked/documented >> > compared to \cites. I think org-cite's decision to make inserting >> > citation(s) multiple by default an odd choice. > >> May you elaborate? Are you talking about auctex? > \cites is just rarely used I

Re: [BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Daan Ro writes: > Currently org-cite-insert requires multiple to complete. When a > completion engine is enabled (likely the more common case), like vertico > or the built-in fido-mode, etc. we must also know how to exit > "abnormally", usually with "M-j": > https://github.com/minad/vertico/issu

[BUG] (Feature request) Allow org-cite-insert to completing-read-just-once [9.7.11]

Currently org-cite-insert requires multiple to complete. When a completion engine is enabled (likely the more common case), like vertico or the built-in fido-mode, etc. we must also know how to exit "abnormally", usually with "M-j": https://github.com/minad/vertico/issues/261, else the command wil

[Feature Request] Adding custom indices for Texinfo export (and maybe unaffiliated dual-value keywords?)

Hello, Texinfo allows one to create new named indices using `@defindex NAME`, which can then be used via `@NAMEindex`. I have been experimenting with different ways of supporting this. I have learned how to add an option `TEXINFO_ADDITIONAL_INDEXES` that can be used to create multiple uses of

Re: Feature request: Export to text file with no line wrapping

Ihor Radchenko writes: > Morten Kjeldgaard writes: > >> The subject says it, it would be very nice if there was an export option >> to export to text mode without wrapping paragraphs,so the resulting text >> file can be read with visual-line-mode on. > > See org-export-preserve-breaks. Does it

Re: Feature request: Export to text file with no line wrapping

Morten Kjeldgaard writes: > The subject says it, it would be very nice if there was an export option > to export to text mode without wrapping paragraphs,so the resulting text > file can be read with visual-line-mode on. See org-export-preserve-breaks. Does it do what you want? -- Ihor Radch

Feature request: Export to text file with no line wrapping

The subject says it, it would be very nice if there was an export option to export to text mode without wrapping paragraphs,so the resulting text file can be read with visual-line-mode on. At the moment I need to use pandoc to do this, using pandoc -f org -t plain --wrap=none file.org > fi

Re: [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]

Daan Ro writes: > I think this bug ticket can be closed. Ok. Canceled. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at

Re: [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]

-preview` asynchronous. First, that > > will definitely speedup opening org files with > > `org-startup-with-latex-preview` > > as Emacs doesn't freeze while generating images. Second, auto preview minor > > modes such as mine would be smoother. > > > > I have

Re: [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]

ugh idea of implementation by passing `org-place-formula-image` as > a > callback closure to `org-create-formula-image` and `org-compile-file`. Would > such a feature request/patch be accepted? See https://list.orgmode.org/87lek2up0w@tec.tecosaur.net/ -- Ihor Radchenko // yanta

Re: [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]

mage` as a callback closure to `org-create-formula-image` and `org-compile-file`. Would such a feature request/patch be accepted? Daanturo On Oct 12 2024, at 10:49 pm, Ihor Radchenko wrote: > Daan Ro writes: > > > [PATCH] org-latex-preview: add org-latex-preview-quiet customization &g

Re: [BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]

Daan Ro writes: > [PATCH] org-latex-preview: add org-latex-preview-quiet customization > > * lisp/org.el (org-latex-preview): define customizable boolean > org-latex-preview-quiet. Thanks for the patch, but may you please elaborate why you want the messages to be suppressed? And why in org-latex

[BUG] Patch: Add an option to silence org-latex-preview (also a feature request) [9.7.11 (release_9.7.11 @ /usr/local/share/emacs/30.0.91/lisp/org/)]

[PATCH] org-latex-preview: add org-latex-preview-quiet customization * lisp/org.el (org-latex-preview): define customizable boolean org-latex-preview-quiet. Emacs : GNU Emacs 30.0.91 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.43, cairo version 1.18.2) of 2024-09-30 Package: Org mode versio

Re: [PATCH] Re: [feature request] startup variable for link display

Ihor Radchenko writes: > Applied, onto main; after changing the terms to > literallinks/descriptivelinks as suggested. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=dd4fd0299 > Done. Thank you, Ihor! Rudy -- "I do not fear death. I had been dead for billions and billions o

Feature request: support sessions in ob-emacs-lisp via IELM

IELM (M-x ielm) derives from comint-mode and provides a convenient interactive environment for evaluating lisp expressions. Some of the conveniences such as automatically evaluating expressions can make iterative development easier. Currently, ob-emacs-lisp does not support sessions. It would be

Re: Feature request: exclude sub-trees by backend

Edgar Lux writes: > Hi, I had a need for this again (sorry for the necro-bump). One month is perfectly normal reply time by mailing list standards :) We just start questioning whether the discussion is active after one month. > On Feb 26, 2024 at 5:51 PM, Ihor Radchenko wrote: >> The suggestio

Re: Feature request: exclude sub-trees by backend

Hi, I had a need for this again (sorry for the necro-bump). On Feb 26, 2024 at 5:51 PM, Ihor Radchenko wrote: > The suggestions to use backend-specific export tag in the links are used > as ugly workarounds... Ok. It was just to show that there are other people who may use it :) . > As for igno

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 p

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 for

Re: Feature request: exclude sub-trees by backend

[ Adding Org mailing list back to CC. ] Edgar Lux writes: > ... >> I think that it would be ok to add such feature if multiple users are >> interested. > > Similar (and may be the ignore-heading from ox-extra should also become > standard, because I found it a lot): > > https://emacs.stackexcha

Re: Feature request: exclude sub-trees by backend

a thing is implemented for any backend. > So that :noexport_X: (where X is a backend) is excluded. Something like: > > * Not for html :noexport_html: > > * For HTML :noexport_latex: This is not a feature request I see often in the forums. It is also easy to implement. I th

Feature request: exclude sub-trees by backend

Hello! I am trying to exclude different sub-trees (a.k.a. headings or sections), depending on the exporter backend. I am familiar with =:noexport:= to exclude selected sections (disregarding the backend). I found a solution, but it is only intended for a specific backend: https://emacs.stackex

Re: [PATCH] Re: [feature request] startup variable for link display

Ihor Radchenko writes: > See the attached patch. Applied, onto main; after changing the terms to literallinks/descriptivelinks as suggested. https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=dd4fd0299 Done. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org

Re: Feature request: export form feed as page break

Timothy writes: >> This is a fork of the ODT exporter in Emacs Orgmode. > > Should I take this to mean that the ox-odt.el in org-mode is no longer > actively > maintained? ox-odt.el in Org mode does not currently have a dedicated maintainer. So, it is maintained just as any other library withou

Re: Feature request: export form feed as page break

Hi Jambunathan, > I am the original author of ox-odt.el. > > The page break feature is available as part of > > > This is a fork of the ODT exporter in Emacs Orgmode. Should I take this to mean that the ox-odt.el in org-mode is no longer actively

Re: [PATCH] Re: [feature request] startup variable for link display

Rudolf Adamkovič writes: >> #+startup: showlinks >> and >> #+startup: compresslinks > > Why not continue with established terminology? > > #+STARTUP: descriptivelinks > #+STARTUP: literallinks I do not have a strong opinion here. I used "show" following showstars/showeverything/etc and because i

Re: [PATCH] Re: [feature request] startup variable for link display

Ihor Radchenko writes: > #+startup: showlinks > and > #+startup: compresslinks Why not continue with established terminology? #+STARTUP: descriptivelinks #+STARTUP: literallinks Rudy -- "It is no paradox to say that in our most theoretical moods we may be nearest to our most practical applica

[PATCH] Re: [feature request] startup variable for link display

"Fraga, Eric" writes: > Assuming I have not missed something, is there a variable I can set on > visiting an org buffer/file that ensures that links are displayed fully? > > Once I've loaded an org file, I can > >M-x org-toggle-link-display RET. > > but I would like certain files to start up

Re: Feature request: IDs for everything

Max Nikulin writes: >> If we simply allow id: links to point to non-headings, it will be a >> major breaking change that may affect third-party packages. So, we >> need to design the extended ids carefully to avoid breakage. > > A defcusom user options whether id:UUID links for non-heading elemen

Re: Feature request: IDs for everything

On 21/10/2023 20:05, Ihor Radchenko wrote: Tor Erlend Fjelde writes: I was wondering if there's a reason why we couldn't have IDs a la org-id.el for everything? It seem to me that it would be useful to use something like `#+ID` in place of `#+NAME` for tables, blocks, etc. as well as headlines.

Re: Feature request: IDs for everything

Tor Erlend Fjelde writes: >> If we simply allow id: links to point to non-headings, it will be a >> major breaking change that may affect third-party packages. So, we >> need to design the extended ids carefully to avoid breakage. For >> example, `org-id-find' and other API function may need to w

Re: Feature request: IDs for everything

> Although we have at least one caveat that we need to consider - the > current users of the id: links blindly assume that they always link to > headings. This includes many third-party packages, like org-roam. > > If we simply allow id: links to point to non-headings, it will be a > major breaki

Re: Feature request: export form feed as page break

Am Sonntag, dem 22. Oktober 2023 schrieb Jambunathan K: > I am the original author of ox-odt.el. > > The page break feature is available as part of > https://github.com/kjambunathan/org-mode-ox-odt I took a look at https://github.com/kjambunathan/org-mode-ox-odt/blob/master/notes/SNIPPETS.org#imp

Re: Feature request: export form feed as page break

On 22/10/2023 16:00, Ihor Radchenko wrote: Max Nikulin writes: P.S. I am against using non-printable characters for markup. It might be an \... entity for page break inside a paragraph, "#+...:" keyword between block-level elements, etc. What about all the above? We may provide entity, keywor

Re: Feature request: export form feed as page break

>>> "JK" == Jambunathan K writes: > I am the original author of ox-odt.el. > The page break feature is available as part of > https://github.com/kjambunathan/org-mode-ox-odt > This is a fork of the ODT exporter in Emacs Orgmode. Hello Since I have used this exporter for some time now, I would

Re: Feature request: export form feed as page break

Max Nikulin writes: > P.S. I am against using non-printable characters for markup. It might be > an \... entity for page break inside a paragraph, "#+...:" keyword > between block-level elements, etc. What about all the above? We may provide entity, keyword, and also ^L. -- Ihor Radchenko //

Re: Feature request: export form feed as page break

Marvin Gülker writes: > ... > On the other hand, there are semantic page breaks. The page break I > described in the OP is of this kind – it has been added specifically to > hide the proposed solution from the first page and allow me to just > print page 1 and hand that one to the students. For t

Re: Feature request: export form feed as page break

Max Nikulin writes: > On 21/10/2023 16:19, Ihor Radchenko wrote: >> - page breaks location is very much backend-dependent; typographic >> detail https://list.orgmode.org/orgmode/875yhiyxnb.fsf@localhost > > Is the link correct? Indeed, it is not. The right link is: https://list.orgmode.org/o

Re: Feature request: export form feed as page break

, and I will be happy to share a recipe or improve the ODT exporter. For those who rely on ODT exporter--I know there aren't many--please consider switching to my repo. If you are going to ask for a feature request for ODT exporter in emacs-orgmode, you can get some lip-service, and low-e

Re: Feature request: export form feed as page break

Am Samstag, dem 21. Oktober 2023 schrieb Ihor Radchenko: > In general, adding page breaks can make sense. The main concern is that > the location of page breaks may or may not be export > backend-independent. In certain scenarios, you may need to put page > breaks in one place for odt export, but

Re: Feature request: export form feed as page break

Am Samstag, dem 21. Oktober 2023 schrieb Max Nikulin: > As a workaround you may define an Org macro that expands to > @@latex:\newpage@@ and appropriate XML element inside @@odt:…@@. Fair enough, this is possible, but then I have to consider each backend I may export to and read up on how the resp

Re: Feature request: export form feed as page break

On 21/10/2023 16:19, Ihor Radchenko wrote: - page breaks location is very much backend-dependent; typographic detail https://list.orgmode.org/orgmode/875yhiyxnb.fsf@localhost Is the link correct? Ihor Radchenko to emacs-orgmode… Re: FR: support hard-newlines [9.5.5 (release_9.5.5 @ /home

Re: Feature request: export form feed as page break

On 21/10/2023 14:42, Marvin Gülker wrote: However, for the page break I always need to write a literal \newpage into the document, which does work, but only in LaTeX. As a workaround you may define an Org macro that expands to @@latex:\newpage@@ and appropriate XML element inside @@odt:…@@.

Re: Feature request: IDs for everything

Tor Erlend Fjelde writes: > I was wondering if there's a reason why we couldn't have IDs a la > org-id.el for everything? It seem to me that it would be useful to use > something like `#+ID` in place of `#+NAME` for tables, blocks, etc. as > well as headlines. This has been discussed in the past

Re: Feature request: export form feed as page break

Marvin Gülker writes: > > To ease this process, I would like to request that the ASCII control > character U+000C FORM FEED (displayed by emacs as ^L and also known as > `\f' in C string notation) is recognised by exporters and translated to > the corresponding page break command, that is, i

Re: Feature request: IDs for everything

> What could be the added benefits of having such a header argument? I can > think of this benefit: #+NAME would be used for referencing them through a > human-friendly name and the name could change and the #+ID would be an UUID > that is not expected to change. This is indeed one use-case I h

Feature request: export form feed as page break

Dear list, I am creating training material for the education of German law students, which usually consists of a case story on one or two pages, followed by a page break after which a proposal for resolving the case is provided. The structure is like this because usually I provide the case story b

Re: Feature request: IDs for everything

Currently, headlines can have an ID (see minimal working example below): #+BEGIN_SRC org * My headline 1 * My headline 2 :PROPERTIES: :ID: e8745be0-906d-4e02-b427-d298f5751f6c :END: #+END_SRC Blocks can't have IDs, but you could use a UUID as the for blocks (see minimal working example below). Yo

Feature request: IDs for everything

Hi all, I was wondering if there's a reason why we couldn't have IDs a la org-id.el for everything? It seem to me that it would be useful to use something like `#+ID` in place of `#+NAME` for tables, blocks, etc. as well as headlines. Would this go against the intended design of org-id.el, or is

Re: [BUG] Feature request: Add group checks for manual tag setting (not just fast tags) [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Ihor Radchenko writes: > ... > In case of the default settings (org-use-fast-tag-selection = auto), the > interface is different - prompt will list all the tags already present > in the heading: > ... > In the above scenario, there is no non-ambiguous way to know which > exclusive tag is implied

Re: [BUG] Feature request: Add group checks for manual tag setting (not just fast tags) [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

sreenivas sumadithya writes: > Currently, tag groups/ mutually exclusive tags can be set when tags are set > manually (without shortcuts being assigned to the tags / fast tags). Need > the behavior seen in fast tags in manual tagging for tag groups. > > Reproduction: > - Create an org file > - "#

[BUG] Feature request: Add group checks for manual tag setting (not just fast tags) [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]

Currently, tag groups/ mutually exclusive tags can be set when tags are set manually (without shortcuts being assigned to the tags / fast tags). Need the behavior seen in fast tags in manual tagging for tag groups. Reproduction: - Create an org file - "#+tags: {dog cat} mat" - Save the file after

Re: [FEATURE REQUEST] Introduce support for FILETAGS in the org-set/toggle-tag function. [9.6.6 (release_9.6.6 @ /opt/homebrew/Cellar/emacs-head@30/30.0.50_1/share/emacs/30.0.50/lisp/org/)]

Tianshu Wang writes: > I am seeking this support because when adding Attachments to Org File > without Headlines, I get a user-error: Before first headline at position > 1 in buffer filename.org, even if the attachment has been successfully > added. I hope there are no errors, and the #+FILETAGS

[FEATURE REQUEST] Introduce support for FILETAGS in the org-set/toggle-tag function. [9.6.6 (release_9.6.6 @ /opt/homebrew/Cellar/emacs-head@30/30.0.50_1/share/emacs/30.0.50/lisp/org/)]

I am seeking this support because when adding Attachments to Org File without Headlines, I get a user-error: Before first headline at position 1 in buffer filename.org, even if the attachment has been successfully added. I hope there are no errors, and the #+FILETAGS of filename.org buffer has adde

Re: Feature request: Allow export to convert broken links to plain text

Ryan, > On Sep 9, 2023, at 9:13 PM, Ryan C. Thompson wrote: > > So, this isn't an ideal solution, since it requires me to prefix any > potential offending links with "maybe:". But it's good enough for me. > It is good that you have a solution, albeit with the caveat you mention above. A coup

Re: Feature request: kill-buffer for org-capture-finalize

On Sun, Sep 10, 2023 at 10:57:46AM +, Ihor Radchenko wrote: > Then, what you can do is > > (defun my-org-capture-finalize (arg) > "Like `org-capture-finalize', but kill Org buffer with double prefix arg." > (interactive "P") > (if (equal arg '(16)) > (save-excursion > (org-captur

Re: Feature request: kill-buffer for org-capture-finalize

Eduardo Suarez writes: > On Sun, Sep 10, 2023 at 08:19:25AM +, Ihor Radchenko wrote: >> (defun my-org-capture-kill-buffer () >> (when (equal current-prefix-arg '(16)) >> (save-excursion >> (org-capture-goto-last-stored) >> (kill-buffer > > Thanks for the propos

Re: Feature request: kill-buffer for org-capture-finalize

On Sun, Sep 10, 2023 at 08:19:25AM +, Ihor Radchenko wrote: > (defun my-org-capture-kill-buffer () > (when (equal current-prefix-arg '(16)) > (save-excursion > (org-capture-goto-last-stored) > (kill-buffer Thanks for the proposed solution. I have tried it and it

Re: Feature request: kill-buffer for org-capture-finalize

Eduardo Suarez writes: > I have tried something simple like > > (defun my-org-capture-kill-buffer () >(when (equal current-prefix-arg '(16)) > (kill-buffer))) > > as an after-finalize hook. It seems to recognize the 'current-prefix-arg' > variable. > > However, > > 1. it looks to me tha

Re: Feature request: Allow export to convert broken links to plain text

On 1/13/19 5:34 PM, Berry, Charles wrote: Looks like your original idea to revise `org-export-data' might be best. IIUC, you need to add the link text to the SIGNAL-DATA in each of the places where `org-export-resolve-*-link' functions call `signal', then modify `org-export-data' to ignore th

Re: Feature request: kill-buffer for org-capture-finalize

On Sat, Sep 09, 2023 at 09:18:27AM +, Ihor Radchenko wrote: > For personal use-case, you can utilize > `org-capture-after-finalize-hook', checking `current-prefix-arg' and > killing the target org buffer according to the prefix argument passed. > Then, for example, you can make C-u C-u C-c C-c

Re: Feature request: kill-buffer for org-capture-finalize

Eduardo Suarez-Santana writes: >> Or do you mean that you sometimes want to kill the target org buffer and >> sometimes not? > > Yes, I mean that I sometimes want to kill the target org buffer and sometimes > not. I don't want to kill the target buffer as the default behavior of my > capture temp

Re: Feature request: kill-buffer for org-capture-finalize

On Fri, Sep 08, 2023 at 12:38:07PM +, Ihor Radchenko wrote: > Did you consider :kill-buffer property in `org-capture-templates'? > > :kill-bufferIf the target file was not yet visited by a buffer when > capture was invoked, kill the buffer again after capture >

Re: Feature request: kill-buffer for org-capture-finalize

Eduardo Suarez-Santana writes: >> May you explain a bit more about the problem you are trying to solve? >> Isn't the temporary capture buffer killed after capture already? >> Or do you refer to the org buffer where the capture is recorded? > > Sorry about that. I refer to the org buffer where the

Re: Feature request: kill-buffer for org-capture-finalize

On Fri, Sep 08, 2023 at 12:10:23PM +, Ihor Radchenko wrote: > Eduardo Suarez writes: > > > The function org-capture-finalize allows an argument to 'jump-to-capture'. I > > think it may be a good idea to add a new argument to 'kill-buffer' after the > > capture is finalized. This would be usef

Re: Feature request: kill-buffer for org-capture-finalize

Eduardo Suarez writes: > The function org-capture-finalize allows an argument to 'jump-to-capture'. I > think it may be a good idea to add a new argument to 'kill-buffer' after the > capture is finalized. This would be useful to avoid having to kill the capture > buffer manually. I assume that if

Feature request: kill-buffer for org-capture-finalize

This is a feature request. The function org-capture-finalize allows an argument to 'jump-to-capture'. I think it may be a good idea to add a new argument to 'kill-buffer' after the capture is finalized. This would be useful to avoid having to kill the capture buffer manual

Re: Feature request: adjust ~org-agenda-format-item~ to let the user choose the first level included in breadcrumbs

"M. Pger" writes: > I understand better, thanks. Would be a good opportunity for me to (try to) > contribute; this weekend I will check carefully the link you've sent. I'll > keep you posted, your assistance would be more than welcome :) It has been a month since the last message in this threa

Re: [BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

Ah thanks for the info, I messed up by only looking at C-h f org-num-mode, and not looking at customize-group. Thank you :) On Mon, Jul 17, 2023 at 2:35 AM Ihor Radchenko wrote: > Ilja Kocken writes: > > > If I have a large org-file with many headings, sometimes it's useful to > > refer to the

Re: [BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

Ilja Kocken writes: > If I have a large org-file with many headings, sometimes it's useful to > refer to the heading number that people have commented on in the > exported PDF (e.g. for an academic paper). However, when I turn on > org-num-mode, this shows a continuous numbering for all the headl

[BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

Hi! If I have a large org-file with many headings, sometimes it's useful to refer to the heading number that people have commented on in the exported PDF (e.g. for an academic paper). However, when I turn on org-num-mode, this shows a continuous numbering for all the headlines in the file. I have

Re: [BUG] feature request: make org-num-mode not count headings that are COMMENTs or have an :ignore: tag [9.6.6 (release_9.6.6 @ /usr/share/emacs/30.0.50/lisp/org/)]

I think in the above I may have forgotten that at the bottom of [[ https://github.com/japhir/ArchConfigs/blob/master/myinit.org#reset-gc-cons-threshold][my config]] I had not uncommented the line that sets the gconf-threshold :O On Thu, Jul 13, 2023 at 3:43 PM Ilja Kocken wrote: > Hi! > > If I

Re: Feature request: adjust ~org-agenda-format-item~ to let the user choose the first level included in breadcrumbs

Hi, I understand better, thanks. Would be a good opportunity for me to (try to) contribute; this weekend I will check carefully the link you've sent. I'll keep you posted, your assistance would be more than welcome :) Best, MP Sent with Proton Mail secure email. --- Original Message -

Re: Feature request: adjust ~org-agenda-format-item~ to let the user choose the first level included in breadcrumbs

"M. Pger" writes: > Sorry for the possibly silly question, but by '+1', can I understand that you > will implement this feature because you think it is worth it? No, it just means that I think that this feature makes sense to be implemented. Basically, upvote. Whether I am going to implement i

Re: Feature request: adjust ~org-agenda-format-item~ to let the user choose the first level included in breadcrumbs

bound, but being able to truncate breadcrumbs from both sides would be even nicer^^ Best, MP --- Original Message --- On Tuesday, July 11th, 2023 at 11:30 AM, Ihor Radchenko wrote: > "M. Pger" mp...@protonmail.com writes: > > > Feature request: adjust ~org-age

Re: Feature request: adjust ~org-agenda-format-item~ to let the user choose the first level included in breadcrumbs

"M. Pger" writes: > Feature request: adjust ~org-agenda-format-item~ to let the user choose the > first level included in breadcrumbs +1 -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <https://orgmode.org/>. Support Org development at

  1   2   3   4   5   6   7   8   9   10   >