Re: Exporting Hyperlinks ?

[David Masterson]

Max Nikulin  writes:

> On 01/11/2023 11:24, David Masterson wrote:
>> In the Org Mode documentation, I see how hyperlinks are handled in HTML
>> export and how images are handled in Latex export, but is there a clear
>> description of how hyperlinks are handled across export engines
>> (particularly the standard ones)?
>
> Only the code may be more complete reference than backend-specific
> sections in the manual. There are some issues (e.g. cross-file id 
> links), but in general links should work.

Hmm. I'm using CUSTOM_ID links to make a rudimentary Contact DB.

>> I see that the PDF viewer is seeing
>> file links from exported PDFs from Latex as links, but it seems
>> incomplete (ie. link to a file, but not to a particular CUSTOM_ID in the
>> file).
>
> It seems ::search part is stripped. Perhaps ::#anchor should be
> exported as #anchor, however it is more tricky with line numbers or
> text search variants.

If I understand what you mean by "anchor", does Org create an anchor in
exporting to Latex when it sees a CUSTOM_ID property in an item?  Then,
would the search in the hyperlink reference the anchor?  Your examples
weren't precise enough for me to follow.

Thanks
-- 
David Masterson

Re: Preferred posting style

[David Masterson]

"Loris Bennett"  writes:

>  writes:
>
>> On Wed, Nov 01, 2023 at 08:32:44AM +0100, Loris Bennett wrote:
>>
>>> Assuming the quoting of previous postings works (above there seems to be
>>> a discrepancy between '>>' and '> >', although Gnus seems to handle
>>> that),  is there some sort of 'bottom-postify' command which would
>>> reorder the quotes?  I occasionally do this by hand if I find the text
>>> makes no sense to me otherwise.
>>
>> ISTR there was something, not in the Emacs context, alas, and before
>> the First Internet Supernova (aka roughly Y2K, when Google had the
>> choice to either go bust or go evil).
>>
>> I guess it won't work, since proper "bottom posting" is a bit more
>> than just putting the whole kaboodle above and your two lines below. 
>
> That maybe true.  However, it would probably cover well over 90% of my
> uses-cases.  Often someone sends me a message, I bottom-post an
> interleaved reply, and then the other person top-posts their answer.  In
> this case would be enough just to move the other person's singly quoted,
> non-interleaved text to the bottom.

Interesting idea, but the formats of "top posting" done by the various
mail readers is not uniform making rearragement difficult and often not
satisfying.

> However I should probably raise the topic on the Gnus list rather than
> discussing it any further here.

Probably true.  They might have some tricks.

-- 
David Masterson

Re: Regression in latex export of tables?

[Vikas Rawal]

On 01/11/2023 10:43, Vikas Rawal wrote:
> Both give this strage [0pt] at the end of every line of the table.
>
> ​​Is this by design? This seems to be something recent. Am I missing
> something.

If you believe that it is a regression then try to export something like

| (a,b) | open interval |
| [0,1] | closed interval |

https://list.orgmode.org/?q=%5B0pt%5D

 
I am sorry, but I do not understand what are you pointing at. This is what I 
get:


\begin{center}
\begin{tabular}{ll}
(a,b) & open interval\\[0pt]
[0,1] & closed interval\\[0pt]
\end{tabular}
\end{center}
\end{document}


What is this [0pt] at the end?

 

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

[Sławomir Grochowski]

I have found good explanation of 'tristate checkbox':
https://dequeuniversity.com/library/aria/checkbox-tri#:~:text=A%20tri%2Dstate%20checkbox%20can,parent%20checkbox%20is%20partially%20checked
.

"A tristate checkbox can be checked, not checked, or partially
checked. The condition of being partially checked is based on the
selection of child elements. If all child elements are selected, the
parent checkbox is checked. If some child elements are selected, the
parent checkbox is partially checked."

So as I understand it this is the same approach in org-mode.
But I'm using 'an intermediate state' to mark a checkbox that can't be
'done'.

Like, I planned to go to gym:
- [  ]  go to gym on 01.11.2023

But the time has passed and I didn't go to the gym on this precise day.
So I can't mark the checkbox as done, I can only leave it as it is.
But after a couple of days I'm not sure if I was at the gym that day and
maybe I just forgot to mark it as done.
So for this purpose I'm marking it as [ - ] that explicitly I can't do this
checkbox.
Maybe others use it the same way?
What do you think?

Regards,
Sławomir Grochowski



On Wed, Nov 1, 2023 at 5:39 PM Sławomir Grochowski <
slawomir.grochow...@gmail.com> wrote:

> Dear All,
>
> 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?
>
> Regards,
> Sławomir Grochowski
>
>

Re: [PATCH] Fix warning about using `eq' to compare strings.

[tomas]

On Wed, Nov 01, 2023 at 11:29:23AM -0500, Karl Fogel wrote:

> [...] (which I guess is better than licking my
> laurels and resting on my wounds).

Don't underestimate Medirerranean cooking. Laurels can be...
yummy :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Regression in latex export of tables?

[Max Nikulin]

On 01/11/2023 10:43, Vikas Rawal wrote:

Both give this strage [0pt] at the end of every line of the table.

​​Is this by design? This seems to be something recent. Am I missing 
something.


If you believe that it is a regression then try to export something like

| (a,b) | open interval   |
| [0,1] | closed interval |

https://list.orgmode.org/?q=%5B0pt%5D

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

[Sławomir Grochowski]

Dear All,

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?

Regards,
Sławomir Grochowski

Re: Exporting Hyperlinks ?

[Max Nikulin]

On 01/11/2023 11:24, David Masterson wrote:

In the Org Mode documentation, I see how hyperlinks are handled in HTML
export and how images are handled in Latex export, but is there a clear
description of how hyperlinks are handled across export engines
(particularly the standard ones)?


Only the code may be more complete reference than backend-specific 
sections in the manual. There are some issues (e.g. cross-file id 
links), but in general links should work.



I see that the PDF viewer is seeing
file links from exported PDFs from Latex as links, but it seems
incomplete (ie. link to a file, but not to a particular CUSTOM_ID in the
file).


It seems ::search part is stripped. Perhaps ::#anchor should be exported 
as #anchor, however it is more tricky with line numbers or text search 
variants.


I have tried

Par <> and [[#cust][link]]

* H1
:PROPERTIES:
:CUSTOM_ID: cust
:END:

[[file:t2.org::#anchor]] stripped.
[[file:t2.org#anchor]] retained.

[[label][link]]

and I get

Par \label{org59ae2bf} and \hyperref[sec:orgd12b09a]{link}
\section{H1}
\label{sec:orgd12b09a}
\url{t2.org} stripped.
\url{t2.org\#anchor} retained.

\hyperref[org59ae2bf]{link}


What about Beamer or ascii or Texinfo?


Beamer is derived from LaTeX. In ascii links to headings are supported, 
but <> have no obvious way for export. As to formatting, see 
the following recent thread:


Max Nikulin. [PATCH] ox-ascii.el: Consistently add brackets around links 
(was: Re: [RFC][PATCH] Allow to export to ascii custom link types as 
notes) Tue, 24 Oct 2023 22:06:05 +0700.

https://list.orgmode.org/uh8mgt$lpo$1...@ciao.gmane.io

Re: [PATCH] Fix warning about using `eq' to compare strings.

[Karl Fogel]

On 01 Nov 2023, Ihor Radchenko wrote:

Bastien  writes:

Karl Fogel  writes:

Hi, everyone.  Small fix attached -- it just makes a warning 
go

away.


Applied against the main branch, thanks!


Unfortunately, fixing this warning breaks org-table logic and 
tests.

See previous discussion in
https://list.orgmode.org/orgmode/20230827214320.46754-1-salu...@me.com/


Oh my goodness.  That is... sigh.  Wow.

This is now beyond the "trivial fix" level of effort that I was 
prepared to invest to make this warning go away.  Like Rudolf 
Adamkovič and others before him, I now retire to my country 
estate, to simultaneously lick my wounds and rest on my laurels 
(which I guess is better than licking my laurels and resting on my 
wounds).


Thank you for noticing, and for adding the FIXME later.

Best regards,
-Karl

Re: Preferred posting style

[Ihor Radchenko]

yaxp  writes:

> Which posting style is preferable in this list?

See https://orgmode.org/worg/org-mailing-list.html#org7b17a4c

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

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

[Kai Jenkins]

Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.  You don't know how to make a good report?  See

 https://orgmode.org/manual/Feedback.html#Feedback

Your bug report will be posted to the Org mailing list.


recipe to create bug:
- start 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 doesn't unfold the header that has the misspelled word (possible 
corrections
are shown in a ispell buffer 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)"

Emacs  : GNU Emacs 29.1 (build 1, x86_64-apple-darwin18.7.0, NS appkit-1671.60 
Version 10.14.6 (Build 18G9323))
of 2023-08-17
Package: Org mode version 9.6.6 (release_9.6.6 @ 
/Applications/Emacs.app/Contents/Resources/lisp/org/)

Re: [PATCH] Fix warning about using `eq' to compare strings.

[Bastien Guerry]

Ihor Radchenko  writes:

> I added a FIXME explaining the issue to make the problem more clear.

Good idea, thanks!

-- 
 Bastien Guerry

Re: [PATCH] Fix warning about using `eq' to compare strings.

[Ihor Radchenko]

Bastien  writes:

>> Unfortunately, fixing this warning breaks org-table logic and tests.
>> See previous discussion in
>> https://list.orgmode.org/orgmode/20230827214320.46754-1-salu...@me.com/
>
> Ouch. Reverted.

I added a FIXME explaining the issue to make the problem more clear. I
think this is the third attempted fix of this warning on the list :)

https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1ef9e144a

Canceled.

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

Re: [PATCH] Fix warning about using `eq' to compare strings.

[Bastien]

Ihor Radchenko  writes:

> Bastien  writes:
>
>> Karl Fogel  writes:
>>
>>> Hi, everyone.  Small fix attached -- it just makes a warning go
>>> away.
>>
>> Applied against the main branch, thanks!
>
> Unfortunately, fixing this warning breaks org-table logic and tests.
> See previous discussion in
> https://list.orgmode.org/orgmode/20230827214320.46754-1-salu...@me.com/

Ouch. Reverted.

I took back control over my zombie clone and put him back to sleep in
his coffin.

-- 
 Bastien

Re: [PATCH] Fix warning about using `eq' to compare strings.

[Ihor Radchenko]

Bastien  writes:

> Karl Fogel  writes:
>
>> Hi, everyone.  Small fix attached -- it just makes a warning go
>> away.
>
> Applied against the main branch, thanks!

Unfortunately, fixing this warning breaks org-table logic and tests.
See previous discussion in
https://list.orgmode.org/orgmode/20230827214320.46754-1-salu...@me.com/

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

Re: Preferred posting style

[Bastien]

Hi,

yaxp  writes:

> Which posting style is preferable in this list?

Interleaved and bottom posting are preferred.

Top posting should definitely be avoided.

-- 
 Bastien

Re: [PATCH] Fix warning about using `eq' to compare strings.

[Bastien]

Hi Karl,

Karl Fogel  writes:

> Hi, everyone.  Small fix attached -- it just makes a warning go
> away.

Applied against the main branch, thanks!

-- 
 Bastien

Re: Preferred posting style

[Loris Bennett]

 writes:

> On Wed, Nov 01, 2023 at 08:32:44AM +0100, Loris Bennett wrote:
>
> [...]
>
>> Assuming the quoting of previous postings works (above there seems to be
>> a discrepancy between '>>' and '> >', although Gnus seems to handle
>> that),  is there some sort of 'bottom-postify' command which would
>> reorder the quotes?  I occasionally do this by hand if I find the text
>> makes no sense to me otherwise.
>
> ISTR there was something, not in the Emacs context, alas, and before
> the First Internet Supernova (aka roughly Y2K, when Google had the
> choice to either go bust or go evil).
>
> I guess it won't work, since proper "bottom posting" is a bit more
> than just putting the whole kaboodle above and your two lines below. 

That maybe true.  However, it would probably cover well over 90% of my
uses-cases.  Often someone sends me a message, I bottom-post an
interleaved reply, and then the other person top-posts their answer.  In
this case would be enough just to move the other person's singly quoted,
non-interleaved text to the bottom.

> It takes some involvement on the responder's side to pick and choose
> the parts of the message she's addressing in the response.

Once the blunt bottomification has been done, I can always delete stuff
that isn't relevant, although usually I wouldn't need to do that. 

> Perhaps, with a large language model...

Maybe, but then I would probably wait until one is advanced enough can
answer all my mail and deal with all follow-ups entirely on its own :-)

> More seriously: those are simply different cultures. I strongly doubt
> you can bridge that with "just" a technical device (although it may
> help sometimes).

As I think you said, the mixture of top- and bottom posting is the
worst, so it would be nice to have something to fix at least the simple
cases.

However I should probably raise the topic on the Gnus list rather than
discussing it any further here.

Cheers,

Loris

-- 
This signature is currently under constuction.

Re: Preferred posting style

[tomas]

On Wed, Nov 01, 2023 at 08:32:44AM +0100, Loris Bennett wrote:

[...]

> Assuming the quoting of previous postings works (above there seems to be
> a discrepancy between '>>' and '> >', although Gnus seems to handle
> that),  is there some sort of 'bottom-postify' command which would
> reorder the quotes?  I occasionally do this by hand if I find the text
> makes no sense to me otherwise.

ISTR there was something, not in the Emacs context, alas, and before
the First Internet Supernova (aka roughly Y2K, when Google had the
choice to either go bust or go evil).

I guess it won't work, since proper "bottom posting" is a bit more
than just putting the whole kaboodle above and your two lines below. 

It takes some involvement on the responder's side to pick and choose
the parts of the message she's addressing in the response.

Perhaps, with a large language model...

More seriously: those are simply different cultures. I strongly doubt
you can bridge that with "just" a technical device (although it may
help sometimes).

Cheers
-- 



signature.asc
Description: PGP signature

Re: Regression in latex export of tables?

[Vikas Rawal]

I am seeing a peculiar problem, and I would appreciate if somebody could check 
whether this is a bug or I am missing something.

The following table exports with a [0pt] at the end of each line.I can confirm 
that the problem disappears if I move to the following version of org-mode:

commit bed47b437d8cde7a98bafdb07996e248b40f70e6 (HEAD -> main, origin/main)
Author: Rudolf Adamkovič 
Date:   Fri Oct 21 14:48:56 2022 +0200

Clearly, the problem has appeared more recently than this.

Vikas
 

Re: Preferred posting style

[Loris Bennett]

 writes:

> On Tue, Oct 31, 2023 at 08:58:32PM -0700, David Masterson wrote:
>> yaxp  writes:
>> 
>> > Hello,
>> >
>> > Which posting style is preferable in this list?
>> >
>> > Top or Bottom.
>> 
>> A decades old argument.  Top makes it easier for many mail readers to
>> slice off all the previous thread history (which the reader has in
>> previous messages).  Bottom makes it easier to have thread context in
>> the message,
>> 
>> Most Emacs related mailing lists / newsgroups prefer bottom.
>
> Let me add that top posting, while it might kind-of-work for personal
> mail breaks down spectacularly in mailing lists.
>
> A mixture of both is worse,of course :-)
>
> Cheers

Assuming the quoting of previous postings works (above there seems to be
a discrepancy between '>>' and '> >', although Gnus seems to handle
that),  is there some sort of 'bottom-postify' command which would
reorder the quotes?  I occasionally do this by hand if I find the text
makes no sense to me otherwise.

Cheers,

Loris
 
-- 
This signature is currently under constuction.

Re: Preferred posting style

[tomas]

On Tue, Oct 31, 2023 at 08:58:32PM -0700, David Masterson wrote:
> yaxp  writes:
> 
> > Hello,
> >
> > Which posting style is preferable in this list?
> >
> > Top or Bottom.
> 
> A decades old argument.  Top makes it easier for many mail readers to
> slice off all the previous thread history (which the reader has in
> previous messages).  Bottom makes it easier to have thread context in
> the message,
> 
> Most Emacs related mailing lists / newsgroups prefer bottom.

Let me add that top posting, while it might kind-of-work for personal
mail breaks down spectacularly in mailing lists.

A mixture of both is worse,of course :-)

Cheers
-- 
t


signature.asc
Description: PGP signature