Re: Planning links to tasks

Eduardo Suarez writes: > Hi, I have just implemented an approach to creating a hierarchy of links to > tasks, so the hierarchy can be thought of a dependency tree (something like a > Gantt but with no dates). This approach may be suitable if your org hierarchy > is not already based on todo

Re: [PATCH 2-v4] New: auto display inline images under subtree when `org-cycle'.

Finally finished and passed the test. Here I attached the new patch. From c36122f818289cbd26026ae75ce480b03e03f61a Mon Sep 17 00:00:00 2001 From: stardiviner Date: Wed, 28 Sep 2022 20:46:52 +0800 Subject: [PATCH] org.el: Support auto display inline images when cycling * lisp/org.el

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

Max Nikulin writes: > On 02/10/2022 11:59, Ihor Radchenko wrote: >> Can you please illustrate how to use the described AST markup for the >> following Texinfo snippet: >> >> By convention, the dynamic library for @var{language} is >>

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

Juan Manuel Macías writes: > And how about this: > > %_name{} > %_name{{}} <--- extra {} is added as needed for escaping > %_name[:key value ...]{} > > or any other symbol instead of "%" ? > > N.B.: I must admit this is more for an "aesthetic" reason. Although > perhaps it can be useful to

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

Max Nikulin writes: > On 01/10/2022 11:08, Ihor Radchenko wrote: >> In particular, I suggest to (1) extend the existing special block elements >> with Elisp-configurable :export settings; (2) add special block >> equivalent object. > > While I do not mind to have flexible generic inline objects,

Re: Some links in online manual do not work

Tim Cross writes: > I wonder if it would be worthwhile adding an option to HTML export which > would force all link targets and exported filenames to lower case, > thereby avoiding issues on platforms and with web servers which have > different positions wrt case sensitivity? Could you please

Re: [HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files))

Tim Cross writes: > I had a very similar idea wrt lint like functionality to alert user to > possible 'stylistic' and/or other problems in exported content. Adding > accessibility to that would then be the next step. > > I'm very much against enforcing standards. Experience has taught me that >

Re: [PATCH 2-v3] New: auto display inline images under subtree when `org-cycle'.

"Christopher M. Miles" writes: > +*** New ~org-cycle-hook~ function ~org-cycle-display-inline-images~ for auto > displaying subtree inline images > + > +This behavior is toggled by custom option ~org-cycle-inline-images-display~. > + I'd be a bit more direct. Something like "Outline cycling

Re: [BUG] org-timer-start doesn't seem to take the timer string at point [9.5.5 (release_9.5.5 @ z:/emacs-i686/share/emacs/28.2/lisp/org/)]

Ypo writes: > Oh! Thanks > > I didn't understand. Maybe this would be more understandable?: > >> When called with a ‘C-u’ prefix, prompt the user for a starting >> offset or, if there is a timer string at point, this is taken as the >> default, ... > Or: > >> When called with a

Re: Issue with export of inlinetasks

Michael Dauer writes: > org-version reports the same version, but now the same code (posted before) > works. So it's fixed. > > But shouldn't org-version report 9.5.5 instead of 9.5? It should. The latest stable version of Org is 9.5.5. The latest development version is 9.6-pre. If you get

Re: Some links in online manual do not work

Tim Landscheidt writes: > Hi, > > at https://orgmode.org/manual/HTML-Export.html, the links > for the first five (5) and the last two (2) subsections > work, the links for: > > - "Headlines in HTML export" > (https://orgmode.org/manual/Headlines-in-HTML-export.html) > - "Links in HTML

Re: [HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files))

Ihor Radchenko writes: > Tim Cross writes: > >> From an org-mode perspective, the key things which need to be maintained >> (and which perhaps we could make even easier or possibly have >> 'defaults') is the ability to add the alt attribute to any non-text >> element. For example, images,

Some links in online manual do not work

Hi, at https://orgmode.org/manual/HTML-Export.html, the links for the first five (5) and the last two (2) subsections work, the links for: - "Headlines in HTML export" (https://orgmode.org/manual/Headlines-in-HTML-export.html) - "Links in HTML export"

Planning links to tasks

This mail is related to 'Manual Ordering and Dynamic Priority' thread. https://lists.gnu.org/archive/html/emacs-orgmode/2022-09/msg00091.html Hi, I have just implemented an approach to creating a hierarchy of links to tasks, so the hierarchy can be thought of a dependency tree (something like a

Re: Markup page 404

kalathilvish...@gmail.com writes: > Update the page on Literal Examples also 404s. > https://orgmode.org/guide/Literal-Examples.html Fixed too, thanks! -- Bastien

Re: Markup page 404

Hi Vishal, thanks for reporting this, this is fixed now. Best, -- Bastien

Markup page 404

Hello, This is regarding the compact orgmode guide. The 11th unit's main page (Markup for Rich Contents) 404s. The page at https://orgmode.org/guide/Markup.html#Markup does not exist. However all the pages under it, i.e. 11.1, 11.2, etc all seem to work. Hopefully you can fix this minor

Re: Markup page 404

Update the page on Literal Examples also 404s. https://orgmode.org/guide/Literal-Examples.html On Sun, Oct 2 2022 at 06:05:16 PM +05:30:00 +05:30:00, kalathilvish...@gmail.com wrote: Hello, This is regarding the compact orgmode guide. The 11th unit's main page (Markup for Rich Contents)

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

On 02/10/2022 11:59, Ihor Radchenko wrote: Max Nikulin writes: This can help with escaping syntax and spaces in verbatim. It should be enough to create nested "code" or "verbatim" inline objects with some attribute like :class file, :class var, :class dfn, etc. Export backend may interpret

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

Eli Zaretskii writes: >> From: "Christopher M. Miles" >> Cc: numbch...@gmail.com, yanta...@gmail.com, emacs-de...@gnu.org, >> emacs-orgmode@gnu.org >> Date: Sun, 02 Oct 2022 18:45:41 +0800 >> >> I hate to rewrite those steps more than 3 times. > > The problem is, I've read the correspondence

[BUG] org-timer-start doesn't seem to take the timer string at point [9.5.5 (release_9.5.5 @ z:/emacs-i686/share/emacs/28.2/lisp/org/)]

In the manual, it says: C-c C-x 0 (|org-timer-start|) ... If there is a timer string at point, this is taken as the default, providing a convenient way to restart taking notes after a break in the process... https://orgmode.org/manual/Timers.html I am trying it, but the

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

Ihor Radchenko writes: > _name{} > _name{{}} <--- extra {} is added as needed for escaping > _name[:key value ...]{} > > The syntax idea is to follow the relevance between [[links]] and > [cite:citations] > but here we have src_name[...]{...} and _name[...]{} instead. And how about this:

Re: [BUG] org-timer-start doesn't seem to take the timer string at point [9.5.5 (release_9.5.5 @ z:/emacs-i686/share/emacs/28.2/lisp/org/)]

Oh! Thanks I didn't understand. Maybe this would be more understandable?: When called with a ‘C-u’ prefix, prompt the user for a starting offset or, if there is a timer string at point, this is taken as the default, ... Or: When called with a ‘C-u’ prefix, there are 2 options:

Re: [BUG] org-timer-start doesn't seem to take the timer string at point [9.5.5 (release_9.5.5 @ z:/emacs-i686/share/emacs/28.2/lisp/org/)]

Ypo writes: > In the manual, it says: > >> C-c C-x 0 (|org-timer-start|) >> >> ... If there is a timer string at point, this is taken as the >> default, providing a convenient way to restart taking notes after >> a break in the process... >> https://orgmode.org/manual/Timers.html

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

On Sunday, 2 Oct 2022 at 21:02, Ihor Radchenko wrote: > > _name{} > _name{{}} <--- extra {} is added as needed for escaping > _name[:key value ...]{} I'd be okay with this as well. -- : Eric S Fraga, with org release_9.5.5-851-ge9781f in Emacs 29.0.50

Re: Issue with export of inlinetasks

org-version reports the same version, but now the same code (posted before) works. So it's fixed. But shouldn't org-version report 9.5.5 instead of 9.5? Ihor Radchenko schrieb am Fr., 30. Sep. 2022, 10:22: > Michael Dauer writes: > > > This is the latest commit on main, isn't it? > > Head:

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

"Fraga, Eric" writes: > I like the idea of inline special blocks. Given that we have recently > introduced [cite:...] as new syntax, could we generalise this and allow > any xxx in [xxx:...]? This syntax will make it difficult to pass optional arguments, like in @abbr{FSF, Free Software

Re: Code block syntax highlighting in async export

On 02/10/2022 14:24, Ihor Radchenko wrote: David Lukeš writes: I get different syntax highlighting in code blocks when using async export: no colors, just bold, italics and underlines. Is this expected, and if so, is there maybe an easy fix I just don’t know about? Could you please provide

Re: Test email

Hi Org ML folks, As you may have guessed, I’m currently tweaking the email setup I have for interacting with the Org ML, and the “testing” email is an accidental consequence of that. Clearly the “Automatically set `To:' on all emails to emacs-orgmode@gnu” hook has to go . Hopefully this will

Re: Test email

Hi me, Testing a tweaked signature: All the best, Timothy -- Timothy (`tecosaur'/`TEC'), Org mode contributor. Learn more about Org mode at . Support Org development at , or support my work at .

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

> > This is because of the ":ascent 'center" part, isn't it? > I guess so. The image bottom is below the text baseline and thus the underline cuts through the image. > What would you want Emacs to do instead in this case? > I do understand how Emacs renders what we get here from the perspective

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

> From: Ihor Radchenko > Date: Sun, 2 Oct 2022 18:57:56 +0800 > Cc: Eli Zaretskii , emacs-de...@gnu.org, emacs-orgmode@gnu.org > > 1. find an image file in your system > 2. emacs -Q > 3. M-: (erase-buffer) > 4. Insert "askdjaklsdj lasasd" > 5. M-: (require 'org) > 6. M-x font-lock-mode > 7. M-:

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

> From: "Christopher M. Miles" > Cc: numbch...@gmail.com, yanta...@gmail.com, emacs-de...@gnu.org, > emacs-orgmode@gnu.org > Date: Sun, 02 Oct 2022 18:45:41 +0800 > > I hate to rewrite those steps more than 3 times. The problem is, I've read the correspondence on the Org list, and I still

Re: Apology [

Dear Tim, thank you very much for the long email. It is very helpful, at least for me, to have a much better understanding of accessibility issues. And, by the way, I did not think you had been overly negative and definitely no apology was required. take care, eric -- : Eric S Fraga, with

Re: [CLOSED] text-property displayed image has a center-line when the text face has underline attribute

On Sun, Oct 2, 2022 at 6:51 PM Christopher M. Miles wrote: > > I hate to rewrite those steps more than 3 times. But I also know Emacs > contributors should not be forced to fix bug for me. Also I can't fix > this bug by myself. So I think it's not a bug, I can tolerate this > center line. Maybe

[CLOSED] text-property displayed image has a center-line when the text face has underline attribute

I hate to rewrite those steps more than 3 times. But I also know Emacs contributors should not be forced to fix bug for me. Also I can't fix this bug by myself. So I think it's not a bug, I can tolerate this center line. Maybe I mastered skill for modify code in Emacs, I might come back to fix

Re: [HELP] Fwd: Org format as a new standard source format for GNU manuals

Hello all, I like the idea of inline special blocks. Given that we have recently introduced [cite:...] as new syntax, could we generalise this and allow any xxx in [xxx:...]? With this, the example Max gave from texinfo: > By convention, the dynamic library for @var{language} is >

[HELP] Help implementing org-lint/warnings buffer during export (was: Org HTML export accessibility (was: org exported pdf files))

Tim Cross writes: > From an org-mode perspective, the key things which need to be maintained > (and which perhaps we could make even easier or possibly have > 'defaults') is the ability to add the alt attribute to any non-text > element. For example, images, videos, sound files etc. All such

[PATCH v4] [BUG] org-attach-id-ts-folder-format fails on customized IDs [9.6 (9.6-??-2e9999783)]

Ihor Radchenko writes: > Max Nikulin writes: > >>> I do not think that it is a good idea. We currently promise to use the >>> first function in the list to generate the IDs. Other functions are >>> mostly a fallback to catch the existing attach dirs created in the past >>> using different ID

Re: Fwd: [BUG] text-property displayed image has a center-line when the text face has underline attribute

> From: "Christopher M. Miles" > Cc: "Christopher M. Miles" , Org Mode > > Date: Sun, 02 Oct 2022 15:03:26 +0800 > > Ihor Radchenko writes: > > > "Christopher M. Miles" writes: > > > >> I replaced step 5 with step 6 by extracting the logic code of > >> org-link-beautify, but I found it does

Re: [PATCH] Unit-test for Please add support for dlangs packagemanager to ob-C.el

Max Nikulin writes: > I am unsure concerning general policy related to org-babel test, so the > following is rather discussion than a direct request to change the test. > > Is there a way to avoid dependency on remote resources? My concern is > test results affected by network issues. In

Re: [PATCH] ox-odt: Prevent auto-formatting in export buffers

David Lukes writes: > * lisp/ox-odt.el (org-odt-template, org-odt--export-wrap): > `write-region' instead of `save-buffer'. Let us know when you manage to get the FSF assignment. -- Ihor Radchenko, Org mode contributor, Learn more about Org mode at https://orgmode.org/. Support Org

Re: Code block syntax highlighting in async export

David Lukeš writes: > I get different syntax highlighting in code blocks when using async > export: no colors, just bold, italics and underlines. Is this expected, > and if so, is there maybe an easy fix I just don’t know about? Could you please provide an example? See

Fwd: [BUG] text-property displayed image has a center-line when the text face has underline attribute

Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> I replaced step 5 with step 6 by extracting the logic code of >> org-link-beautify, but I found it does not have center-line. That's >> really weird. >> ... >>(put-text-property >> start end >> 'display

[BUG] Storing multiple log notes recursively only keeps the last note (was: Tracking todo state changes AND automatically change to done when all children are done)

Ihor Radchenko writes: >> To reproduce this curious behavior, you only need this configuration: > > Confirmed. > > Something inside `org-todo' call in the hook triggers recursive-edit > that, in turn, triggers premature call to post-command-hook containing > note saving function. I was wrong.