[Help] org-capture: How to capitalize the text entered from the "nth prompt"
Hi
Could it be possible, in org-capture, to capitalize the text entered
from a previous prompt?
Example:
I have this part of an org-capture template:
* %^{CLIENT} _%^{Project}_ /%^{Description}/
:PROPERTIES:
:DIR: z:/! 2023/%\\1-%\\2-%\\3
:END:
I would like to know if it is possible to “capitalize” the used data
that I entered before. For example, instead of this:
** Client _Project Number_ /Project description/
:PROPERTIES:
:DIR: z:/! 2023/Client-Project Number-Project description
:END:
Could it be possible to get this? (The 3rd line is “capitalized”):
** Client _Project Number_ /Project description/
:PROPERTIES:
:DIR: z:/! 2023/CLIENT-PROJECT NUMBER-PROJECT DESCRIPTION
:END:
Best regards
What do you recommend for acronyms in org-mode?
I would like to know what do you use for acronyms, glossaries, etc for using inside org-mode? Not for exportation, just to use them inside Emacs. Maybe radio links, or the package org-glossary? org-ref? Best regards
Re: What do you recommend for acronyms in org-mode?
Hi John! I was using org-ref some time ago, but it seemed to get emacs slower, in my low resources PC. Would you give me some tips to make org-ref lighter? Best regards 27 ago 2023 2:33:05 John Kitchin : > You can see how these work in org-ref in this video: > https://www.youtube.com/watch?v=sebs2vSIEk4&list=PL0sMmOaE_gs3E0OjExoI7vlCAVygj6S4I&index=13. > > On Sat, Aug 26, 2023 at 1:21 PM Maske wrote: >> >> I would like to know what do you use for acronyms, glossaries, etc for using >> inside org-mode? Not for exportation, just to use them inside Emacs. >> >> Maybe radio links, or the package org-glossary? org-ref? >> >> Best regards >> > > > -- > John > > --- > Professor John Kitchin (he/his) > Doherty Hall A207F > Department of Chemical Engineering > Carnegie Mellon University > Pittsburgh, PA 15213 > 412-268-7803 > https://kitchingroup.cheme.cmu.edu[https://kitchingroup.cheme.cmu.edu/] > https://pointbreezepubs.gumroad.com/ pycse bookstore
[FR] Aligning paragraphs in lists
Could be used M-right or M-left to align paragraphs which are immediately below a list? In a list, if pressing Enter, the next paragraph is aligned below the item of the list: + Item 1 Text indented, belongs to Item 1. If there are subitems, the text could be needed to be aligned below a superior item, and this must be done in a manual way: + Item 1 Text indented, belongs to Item 1. - Item 2 Text indented, belongs to Item 2. This paragraph is aligned below Item 1, but I think there is too much "friction" to achieve this. And the alignment would be different if the bullet was "1)" Best regards
[DISCUSSION] Re-design of inlinetasks
Hi I am sorry, I don't know the appropriate terminology. Could be used *** END or a different special string, to end any headline scope? Like an "end parenthesis" for the headline just above it. Maybe in this way, all headlines would be the same: if the special string appears, the headline scope ends there (inlinetask). If no special string, the scope would end before the next headline (or at the end of the document).
Erratum in "The Org Manual" 9.6
There are some links, that I am afraid don't work: 17.14.1 Packages that Org cooperates with ‘calc.el’ by Dave Gillespie [...] See Section “Embedded Mode” in calc. # that link doesn't work, it seems it tries to open the file calc.pdf ‘constants.el’ by Carsten Dominik [...] http://www.astro.uva.nl/~dominik/Tools. # That link is dead. Maybe this would be the correct one: https://staff.fnwi.uva.nl/c.dominik/#orgf869524 Best regards
[FR] A more general case than footnotes
Hi Could exist a more general case than footnotes? A kind of footnotes that work between different files? Maybe the syntax could be [n:LABEL@ID] Where the ID would be the unique ID of the heading. Example: ** Reference :PROPERTIES: :ID: 978-84-362-7195-9 :END: A “comment line” starts with a hash character (#) [n:102@978-84-362-7195-9] and either a whitespace character or the immediate end of the line. ... ** Notes [n:102@978-84-362-7195-9] The hash character is important in orgmode.
Re: [FR] A more general case than footnotes
Hi Ihor The headings could be in different files, yes. AFAIK, citations don't link two exact points. Footnotes do. I don't understand the option of "include", but I think it wouldn't be the case. I really think footnotes would be a particular case of this option. ** Reference in file A :PROPERTIES: :ID: 978-84-362-7195-9 :END: ... A “comment line” starts with a hash character (#) *[n:102@978-84-362-7195-9]* and either a whitespace character or the immediate end of the line. ... ** Notes in file B *[n:102@978-84-362-7195-9]* The hash character is important in orgmode. Thanks for reading On 07/10/2023 13:12, Ihor Radchenko wrote: Maske writes: Could exist a more general case than footnotes? A kind of footnotes that work between different files? Maybe the syntax could be [n:LABEL@ID] Where the ID would be the unique ID of the heading. Example: ** Reference :PROPERTIES: :ID: 978-84-362-7195-9 :END: A “comment line” starts with a hash character (#) [n:102@978-84-362-7195-9] and either a whitespace character or the immediate end of the line. ... ** Notes [n:102@978-84-362-7195-9] The hash character is important in orgmode. I am not sure if I understand. Is the above in different files? Random suggestions: 1. Use citations 2. Use a normal footnote and #+include statement in its definition to incorporate a text from a different file during export.
Re: [FR] A more general case than footnotes
On 07/10/2023 15:21, Ihor Radchenko wrote: Maske writes: The headings could be in different files, yes. AFAIK, citations don't link two exact points. Footnotes do. Do you mean that you also want to jump back-and-forth between footnote definition in the another file and its footnote references? Right: With C-c. And maybe there could work directly commands like "org-footnote-action", being unneeded to create new commands like "org-note-action" with almost the same functionality. I don't understand the option of "include", but I think it wouldn't be the case. Seehttps://orgmode.org/manual/Include-Files.html Thanks, I save it. I really think footnotes would be a particular case of this option. ** Reference in file A :PROPERTIES: :ID: 978-84-362-7195-9 :END: ... A “comment line” starts with a hash character (#) *[n:102@978-84-362-7195-9]* and either a whitespace character or the immediate end of the line. ... ** Notes in file B *[n:102@978-84-362-7195-9]* The hash character is important in orgmode. May you explain the purpose of @978-84-... part? You seem to assume that a footnote always has a single reference, which may or may not be the case in practice. If there would be more than one reference, a behavior like that of footnotes would be appropriate? The purpose of the @978-84-... part: @978-84-362-7195-9 would work like the ID for internal links: [[id:978-84-362-7195-9]]. That would allow jumping to the correct heading from any file. I am not a programmer, so the syntax I am sure could be more solid. Example: ** Reference in file A :PROPERTIES: :ID: 978-84-362-7195-9 :END: ... A “comment line” starts with a hash character (#) [n:102@978-84-362-7195-9] and either a whitespace character or the immediate end of the line. ... ** Notes in file B [[id:978-84-362-7195-9]]: Link to heading in file A [n:102@978-84-362-7195-9]: Link to an exact point in file A. Where the point is defined by the LABEL 102, and the file can be find thanks to the ID 978-84-362-7195-9
Re: [FR] A more general case than footnotes
Hi, Ihor I overlooked the aspect of exporting. I propose links to arbitrary points in different files. Furthermore, I think it would be a very nice new feature, probably more opinions than mine should be heard. Thanks On 08/10/2023 11:18, Ihor Radchenko wrote: Maske writes: *[n:102@978-84-362-7195-9]* The hash character is important in orgmode. May you explain the purpose of @978-84-... part? You seem to assume that a footnote always has a single reference, which may or may not be the case in practice. If there would be more than one reference, a behavior like that of footnotes would be appropriate? If this was a question to me, I do not fully understand it. The purpose of the @978-84-... part: @978-84-362-7195-9 would work like the ID for internal links: [[id:978-84-362-7195-9]]. That would allow jumping to the correct heading from any file. I am not a programmer, so the syntax I am sure could be more solid. Example: ** Reference in file A :PROPERTIES: :ID: 978-84-362-7195-9 :END: ... A “comment line” starts with a hash character (#) [n:102@978-84-362-7195-9] and either a whitespace character or the immediate end of the line. ... ** Notes in file B [[id:978-84-362-7195-9]]: Link to heading in file A [n:102@978-84-362-7195-9]: Link to an exact point in file A. Where the point is defined by the LABEL 102, and the file can be find thanks to the ID 978-84-362-7195-9 I am a bit confused. Do you propose footnotes to have definition in different file? Or do you want a link to arbitrary point in different file? For footnotes, we will need to arrange export to search the definition and include it into the exported file, while links have different set of requirements. I propose
[FR] A more general case than footnotes
Hi Ihor It seems Rick gave a step towards the direction of links to points? It would seem that if the Search Option would be available for internal links, it would work. Then maybe we would just miss a convenient way for generating unique <>. Bests. On 09/10/2023 13:24, Ihor Radchenko wrote: Maske writes: See: - - - The idea is not new, but we need someone to implement it one way or another. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <>. Support Org development at <>, or support my work at <> https://list.orgmode.org/orgmode/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail.com/ <https://list.orgmode.org/orgmode/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail.com/> Rick is suggesting the use of internal links with the search option of file links. I believe this would be a positive step towards improving the linking ecosystem. By relying on unique IDs rather than file names, these links would remain functional even if headings are refiled or files are moved. However, I don't see the need for ID inheritance. https://list.orgmode.org/orgmode/cajniy+ovd0ncwzztpit5t7wvsblbgllxzmpub5tgq3gshsg...@mail.gmail.com/ <https://list.orgmode.org/orgmode/cajniy+ovd0ncwzztpit5t7wvsblbgllxzmpub5tgq3gshsg...@mail.gmail.com/> Hello Alan. It is possible to achieve this by utilizing the Search Option of file links. For instance, you can link to the point <<20231014T033851.173165>> from any other file using the following format: [[file:~/xx.org::20231014T033851.173165]] https://list.orgmode.org/orgmode/CAJcAo8s=cjNY-7-mA1zQk3R9HEWYreTatdVeHfJ39ccM9=k...@mail.gmail.com/ <https://list.orgmode.org/orgmode/CAJcAo8s=cjNY-7-mA1zQk3R9HEWYreTatdVeHfJ39ccM9=k...@mail.gmail.com/> Hi, Samuel. A similar approach is feasible, but it involves using file links instead of internal links. I propose links to arbitrary points in different files. > > Furthermore, I think it would be a very nice new feature, probably more > opinions than mine should be heard. Link <https://list.orgmode.org/orgmode/87bkd8m41s.fsf@localhost/>
Re: [FR] A more general case than footnotes
Hi Ihor It seems Rick gave a step towards the direction of links to points? It would seem that if the Search Option would be available for internal links, it would work. Then maybe we would just miss a convenient way for generating unique <>. Bests. On 09/10/2023 13:24, Ihor Radchenko wrote: Maske writes: See: - - - The idea is not new, but we need someone to implement it one way or another. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at <>. Support Org development at <>, or support my work at <> https://list.orgmode.org/orgmode/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail.com/ <https://list.orgmode.org/orgmode/118435e8-0b20-46fd-af6a-88de8e19f...@app.fastmail.com/> Rick is suggesting the use of internal links with the search option of file links. I believe this would be a positive step towards improving the linking ecosystem. By relying on unique IDs rather than file names, these links would remain functional even if headings are refiled or files are moved. However, I don't see the need for ID inheritance. https://list.orgmode.org/orgmode/cajniy+ovd0ncwzztpit5t7wvsblbgllxzmpub5tgq3gshsg...@mail.gmail.com/ <https://list.orgmode.org/orgmode/cajniy+ovd0ncwzztpit5t7wvsblbgllxzmpub5tgq3gshsg...@mail.gmail.com/> Hello Alan. It is possible to achieve this by utilizing the Search Option of file links. For instance, you can link to the point <<20231014T033851.173165>> from any other file using the following format: [[file:~/xx.org::20231014T033851.173165]] https://list.orgmode.org/orgmode/CAJcAo8s=cjNY-7-mA1zQk3R9HEWYreTatdVeHfJ39ccM9=k...@mail.gmail.com/ <https://list.orgmode.org/orgmode/CAJcAo8s=cjNY-7-mA1zQk3R9HEWYreTatdVeHfJ39ccM9=k...@mail.gmail.com/> Hi, Samuel. A similar approach is feasible, but it involves using file links instead of internal links. I propose links to arbitrary points in different files. > > Furthermore, I think it would be a very nice new feature, probably more > opinions than mine should be heard. Link <https://list.orgmode.org/orgmode/87bkd8m41s.fsf@localhost/>
[FR] org-num-mode inverse defaults
Hi From the first day, I liked org-num-mode, but I think that its default which numbers all headlines could be problematic. Right now it only has the options to exclude headlines from being numbered, so it could be necessary to modify a big amount of headlines, for numbering just a tree. I think it would be helpful to have a "positive" way to numbering headlines, for example "NUMBERED" keyword, while all the other headlines stay unnumbered. Bests
Re: [FR] org-num-mode inverse defaults
Hi Ihor
I added: (setq org-global-properties '(("UNNUMBERED" . "t")))
But it doesn't work, every headline is numbered. (Not tried in emacs -q).
Bests
On 15/10/2023 14:40, Ihor Radchenko wrote:
Maske writes:
From the first day, I liked org-num-mode, but I think that its default
which numbers all headlines could be problematic.
Right now it only has the options to exclude headlines from being
numbered, so it could be necessary to modify a big amount of headlines,
for numbering just a tree.
I think it would be helpful to have a "positive" way to numbering
headlines, for example "NUMBERED" keyword, while all the other headlines
stay unnumbered.
You can simply set UNNUMBERED property to t for the whole document via
#+PROPERTY keyword or by customizing `org-global-properties'. Then, the
headings that should be numbered should have their UNNUMBERED set to nil.
Faces for org blocks that are not "src"
Is it possible to change the face of org blocks that don't start by "src"?
For example:
'(org-src-block-faces '(("ai" variable-pitch)))
I think it should affect to:
#+begin_ai blocks, but it doesn't seem to work for me.
Best regards
Re: [FR] org-num-mode inverse defaults
Hi, Ihor
My config, not working yet, everything is numbered with org-num-mode:
(setq org-num-skip-unnumbered 't)
(setq org-use-property-inheritance '("UNNUMBERED"))
(setq org-global-properties '(("DIR" . "data/") ("UNNUMBERED" . "t")))
Maske
On 15/10/2023 14:40, Ihor Radchenko wrote:
Maske writes:
From the first day, I liked org-num-mode, but I think that its default
which numbers all headlines could be problematic.
Right now it only has the options to exclude headlines from being
numbered, so it could be necessary to modify a big amount of headlines,
for numbering just a tree.
I think it would be helpful to have a "positive" way to numbering
headlines, for example "NUMBERED" keyword, while all the other headlines
stay unnumbered.
You can simply set UNNUMBERED property to t for the whole document via
#+PROPERTY keyword or by customizing `org-global-properties'. Then, the
headings that should be numbered should have their UNNUMBERED set to nil.
