Re: Exporting Hyperlinks ?

[David Masterson]

Ihor Radchenko  writes:

> Max Nikulin  writes:
>
>> Human-readable link targets are susceptible to collisions. So ox-latex 
>> should support links to particular locations in the specified files, 
>> either an Org one or inside external PDF files. Code from ox-html should 
>> be adapted for ox-latex.
>>
>> [[file:test.pdf::#anchor][Another document]]
>>-> \href{test.pdf\#anchor}{Another document}
>
> AFAIK, this kind of URL cannot be opened except when opening pdf in
> browser.

What else is there?  PDFviewer?  What is the standard for Latex?

>> [[file:test.org::#anchor][Another document]]
>> Either for xr-hyper
>>   -> Another document \ref{f1-orgabc123}
>> with \label{orgabc123} in test.tex
>> or with redefined \label to generate additional \hypertarget
>>   -> \href{test.pdf\#anchor}{Another document}
>
> And this does not fit into single-document exports. We must export
> multiple files via ox-publish. ...and ox-publish does not support pdf
> export.

org-latex-publish-to-pdf ??  Oh, you mean that it has to go through
Latex to get to PDF. 

-- 
David Masterson

Re: [BUG] [PATCH] Add yank-media and DND handler [9.6.7 (9.6.7-g6eb773 @ /home/viz/lib/emacs/straight/build/org/)]

[Visuwesh]

[ஞாயிறு நவம்பர் 05, 2023] Ihor Radchenko wrote:

> Po Lu  writes:
>
>> I have now installed an interface to this end into Emacs 30.  The
>> pertinent documentation is under the ``Drag and Drop'' node in the Lisp
>> reference manual.
> [...]
> Visuwesh, do you want to update your patch accordingly?

Yes, I intend to.  But this might not happen until December since I am
busy with the end of my semester.

Re: [FR] 'org-columns-next-allowed-value' for 'summary-checkbox'es functions should have 'intermediate state' '[-]'

[Ihor Radchenko]

Sławomir Grochowski  writes:

> But why is it allowed in '(org-toggle-checkbox  TOGGLE-PRESENCE)'.
> To set a normal checkbox to 'partial state'?
> Description from function: 'With a double prefix argument, set the checkbox
> to "[-]".'
>
> Probably it should not be allowed for normal checkbox only for parent
> checkbox, which have children.
>
> What do you think?

This requires explicit user action (passing C-u C-u prefix argument).
So, I do not see any problem. At the end, nothing stops users from
editing the checkbox manually as plain text.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Org site is down

[Bastien Guerry]

Bastien  writes:

> https://tracker.orgmode.org is back too but tracking new emails will
> not work for the next two hours or so.  I'll confirm when it's back.

It should be back now, please report any problem you may notice.

-- 
 Bastien

Re: [FR] 'org-columns-next-allowed-value' for 'summary-checkbox'es functions should have 'intermediate state' '[-]'

[Sławomir Grochowski]

Yes. You are right.
After thinking about it I think the same.

But why is it allowed in '(org-toggle-checkbox  TOGGLE-PRESENCE)'.
To set a normal checkbox to 'partial state'?
Description from function: 'With a double prefix argument, set the checkbox
to "[-]".'

Probably it should not be allowed for normal checkbox only for parent
checkbox, which have children.

What do you think?

Regards,
Sławomir Grochowski






On Sun, Nov 5, 2023 at 1:25 PM Ihor Radchenko  wrote:

> Sławomir Grochowski  writes:
>
> > I was wondering how many states a checkbox has.
> > Based on https://orgmode.org/manual/Checkboxes.html I conclude that
> there
> > are 3 states:
> > 1. [   ] - not done
> > 2. [ - ] - an intermediate state
> > 3. [X] - done
> >
> > So I think all 3 states should be available to choose from in the
> function
> > 'org-columns-next-allowed-value''
> > for functions that use checkboxes.
> > In code this is a line
> >
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/lisp/org-colview.el#n754
> >
> > So I would change it from this:
> > -  (`(,_ ,_ ,_ ,(or "X" "X/" "X%") ,_) '("[ ]" "[X]")))
> > to that:
> > + (`(,_ ,_ ,_ ,(or "X" "X/" "X%") ,_) '("[ ]" "[-]" "[X]")))
> >
> > What do you think?
>
> I think that your use-case is not necessarily common enough to change
> the defaults. But we can introduce a defcustom here. Patches welcome!
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at .
> Support Org development at ,
> or support my work at 
>

Re: Org site is down

[Bastien]

Ihor Radchenko  writes:

> Daniel Fleischer  writes:
>
>> Orgmode.org appears to be down.
>
> Working on my side.

Yes, the web part of the maintenance is over, the website is back.

https://tracker.orgmode.org is back too but tracking new emails will
not work for the next two hours or so.  I'll confirm when it's back.

-- 
 Bastien

orgmode.org down for maintenance

[Bastien]

https://orgmode.org is temporarily down for maintenance.

I expect the serveur to be up and running in less than two hours.

-- 
 Bastien

Re: Org site is down

[Bastien]

Daniel Fleischer  writes:

> Orgmode.org appears to be down.

Yes, see my message: it should come back in two hours.

-- 
 Bastien

Re: Org site is down

[Ihor Radchenko]

Daniel Fleischer  writes:

> Orgmode.org appears to be down.

Working on my side.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Org site is down

[Daniel Fleischer]

Orgmode.org appears to be down.

Re: Exporting Hyperlinks ?

[Ihor Radchenko]

Max Nikulin  writes:

> Human-readable link targets are susceptible to collisions. So ox-latex 
> should support links to particular locations in the specified files, 
> either an Org one or inside external PDF files. Code from ox-html should 
> be adapted for ox-latex.
>
> [[file:test.pdf::#anchor][Another document]]
>-> \href{test.pdf\#anchor}{Another document}

AFAIK, this kind of URL cannot be opened except when opening pdf in
browser.

> [[file:test.org::#anchor][Another document]]
> Either for xr-hyper
>   -> Another document \ref{f1-orgabc123}
> with \label{orgabc123} in test.tex
> or with redefined \label to generate additional \hypertarget
>   -> \href{test.pdf\#anchor}{Another document}

And this does not fit into single-document exports. We must export
multiple files via ox-publish. ...and ox-publish does not support pdf
export.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [PATCH] org-id: allow using parent's existing id in links to headlines

[Ihor Radchenko]

"Rick Lupton"  writes:

> My previous patch changes the behaviour when `org-id-link-to-org-use-id` has 
> a new value (`inherit`) in two ways:
>
> (a) org-ids from parent headings are considered when choosing the ID to link 
> to, and 
> (b) search strings are added to the link
>
> But these are actually two independent things. So my question is: should 
> search strings be added to all org-id links?

> This would make org-id links more powerful/precise (because you can link to 
> more precise locations within the subtree), and simplifies the code in 
> `org-store-link` in my patch (because point [b] above would apply to all 
> org-id links, not just the new 'inherit ones), but it could change the 
> behaviour when calling `org-store-link` with an active region or when point 
> is on a named element.

Sounds as a reasonable default, but users should have an option to
revert to previous behaviour with heading id being stored.
Otherwise, we may break the muscle memory for people used to what
happens now.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [FR] 'org-columns-next-allowed-value' for 'summary-checkbox'es functions should have 'intermediate state' '[-]'

[Ihor Radchenko]

Sławomir Grochowski  writes:

> I was wondering how many states a checkbox has.
> Based on https://orgmode.org/manual/Checkboxes.html I conclude that there
> are 3 states:
> 1. [   ] - not done
> 2. [ - ] - an intermediate state
> 3. [X] - done
>
> So I think all 3 states should be available to choose from in the function
> 'org-columns-next-allowed-value''
> for functions that use checkboxes.
> In code this is a line
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/lisp/org-colview.el#n754
>
> So I would change it from this:
> -  (`(,_ ,_ ,_ ,(or "X" "X/" "X%") ,_) '("[ ]" "[X]")))
> to that:
> + (`(,_ ,_ ,_ ,(or "X" "X/" "X%") ,_) '("[ ]" "[-]" "[X]")))
>
> What do you think?

I think that your use-case is not necessarily common enough to change
the defaults. But we can introduce a defcustom here. Patches welcome!

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: man pages references (Re: [PATCH] ox-ascii.el: Consistently add brackets around links)

[Ihor Radchenko]

Max Nikulin  writes:

>>> Side note: it should be either just "man(1)" or "man(8)" without any URL
>>> for plain text export, but it is another story.
>> 
>> I would not say "should". May? Yes. URL also makes sense in some
>> scenarios (when the intended reader is not on Linux).
>
> URL makes sense when it is particular version or a page generated 
> without intermediate roff format, but this case it is https:, not man: 
> link. Compare (sorry, man.he.net is terribly obsolete)
> http://storaged.org/doc/udisks2-api/latest/udisks.8.html#id-1.2.4.7
> that has more links than the page generated from man page (debiman still 
> recognizes much more cross-references than emacs man buffers)
> https://manpages.debian.org/bookworm/udisks2/udisks.8.en.html#DEVICE_INFORMATION

I do not see why man.he.net is obsolete - it does not look like it is
unmaintained. That said, feel free to submit a patch with online man
pages website being customizeable.

> "man(1)" references were used in paper documents when internet was not 
> always available. In books references may be emphasized by italics or 
> fixed width font.
>
> I like formatting similar to "systemd-resolved(8) § /ETC/RESOLV.CONF"
> https://wiki.archlinux.org/title/Systemd-resolved
> It makes clear that links point to man pages and precise enough since 
> specific sections are provided.

I have no objections about having this export style as a user option.
Again, patches welcome.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: Gantt Chart with org-mode

[Christophe Schockaert]

On 2023-11-04 13:30, Heime wrote:

Can one construct a Gantt Chart with org-mode ?


Although I didn’t try it yet, there is Elgantt hat caught my eyes : 
https://github.com/legalnonsense/elgantt


Have a good day and nice Org discoveries,
Christophe

Re: [BUG] [PATCH] Add yank-media and DND handler [9.6.7 (9.6.7-g6eb773 @ /home/viz/lib/emacs/straight/build/org/)]

[Ihor Radchenko]

Po Lu  writes:

> I have now installed an interface to this end into Emacs 30.  The
> pertinent documentation is under the ``Drag and Drop'' node in the Lisp
> reference manual.

Thanks!

AFAIU, the relevant paragraph is

@cindex dnd-multiple-handler, a symbol property
If a handler function is a symbol whose @code{dnd-multiple-handler}
property (@pxref{Symbol Properties}) is set, then upon a drop it is
given a list of every URL that matches its regexp; absent this
property, it is called once for each of those URLs.  Following this
first argument is one of the symbols @code{copy}, @code{move},
@code{link}, @code{private} or @code{ask} identifying the action to be
taken.

Visuwesh, do you want to update your patch accordingly?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

Re: [BUG] org, ispell [9.6.6 (release_9.6.6 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]

[Ihor Radchenko]

Kai Jenkins  writes:

> recipe to create bug:
> - starting emacs (via. emacs -Q)
> - open a new org file
> - create a heading (eg. * test)
> - write some text under the heading that contains a spelling mistake
> - fold the heading with tab
> - run M-x ispell
>
> the bug:
> - ispell doesnt unfold the header that has the bug (possible corrections
> are shown so it is finding the incorrect word)
> - when you exit ispell with C-g the heading is now stuck and will not unfold 
> with tab
> - in the buffer theres a message "SUBTREE (NO CHILDREN)"

Confirmed.

At this point, I feel that supporting isearch + text properties is an
uphill battle. I was hoping to contribute isearch.el patch upstream, but
apparently numerous other libraries (ispell, regexp-search, evil,
swiper) are relying upon invisibility being handled in very specific
way, using overlays. Considering that using overlays is no longer slower
compared to text properties in Emacs 29+, I am thinking of slowly
switching back to using overlays for folding for newer Emacs versions.

For your problem, just add (setq org-fold-core-style 'overlays) early in
your config. It should fix the issue.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at 

[TASK] Re: Link translation & relative path export_file_name

[Ihor Radchenko]

Psionic K  writes:

> When using an +#export_file_name directive, is it possible to have links
> translated to match the directory offset of the target?
> ...
> The links in the org document are correct.  The links in the resulting
> markdown are not translated, and break.

You can use a custom filter.
Unfortunately, adding such filter universally is tricky - when
publishing, relative links to files are currently expected to remain
valid as the publishing also moves the referenced files to the publishing
directory. If we update the relative links according to the exported
file location, this behaviour will be broken.

I think that the right approach will be updating the file links during
ordinary export and then handling the updated links specially during
publishing. Patches welcome.

> The manual has a slightly different problem.  I need to translate it as if
> it will be exported to the root directory even though it's always in the
> doc directory.  The links don't seem useful, and turning them off may be
> more correct.  I haven't gotten a lot of experience with drafting texinfo
> yet.

You may consider using ox-publish - it is designed with multiple files
being exported in mind and allows setting target directory where the
necessary files will be copied over.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at .
Support Org development at ,
or support my work at