Re: bug-tracker: How to response/subscribe to a bug-thread

[Kyle Meyer]

c.bu...@posteo.jp writes:

> Side question: I can I monitor that thread/bug without being subscribed 
> to the list? The "dashboard" seems not to have any subscribe, monitor or 
> feed mechanism. The "Atom" feed (https://list.orgmode.org/new.atom) is 
> only for complete list not for one thread.

You can get an atom feed for a single thread using the /t.atom endpoint
(documented in ).

Example:

  https://list.orgmode.org/orgmode/12368452.sVpYeFqCzH@pluto/t.atom

Re: bug-tracker: How to response/subscribe to a bug-thread

[Russell Adams]

On Wed, Mar 09, 2022 at 04:46:25PM +, c.bu...@posteo.jp wrote:
> Hello,
> I still try to become warm with the bug-tracking-system you are using.
>
> There is a known bug that is also tracked on the "dashboard"
> (https://updates.orgmode.org/) as "Inconsistent handling of id: links to
> other file during publish".
> https://list.orgmode.org/12368452.sVpYeFqCzH@pluto/
>
> I was not subscribed to the list when this thread comes up. So I have no
> mail here I can reply-to. I can I answer to that thread?

On that list page, the footer says you can either download an mbox
archive of the messages and reply inside your mail client, and it
provides a link where you can use a in-reply-to and subject header
which CC's the list.

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

mailto:inkbottle007%40gmail.com?In-Reply-To=%3C12368452.sVpYeFqCzH@pluto%3ECc=emacs-orgmode%40gnu.orgSubject=Re%3A%20Internal%20link%20broken%20when%20publishing%20%28was%20org-id%20with%20ox-html%29

> Side question: I can I monitor that thread/bug without being subscribed
> to the list? The "dashboard" seems not to have any subscribe, monitor or
> feed mechanism. The "Atom" feed (https://list.orgmode.org/new.atom) is
> only for complete list not for one thread.

The best way is to subscribe to the list.

--
Russell Adamsrlad...@adamsinfoserv.com

PGP Key ID: 0x1160DCB3   http://www.adamsinfoserv.com/

Fingerprint:1723 D8CA 4280 1EC9 557F  66E8 1154 E018 1160 DCB3

Re: Move or rename a file in a link

[João Pedro de Amorim Paula]

On 05 March 2022 19:58, Juan Manuel Macías  wrote:

Hello Juan!

> Hi all,
>
> I have written this simple function to move or rename a destination file
> in an external link at point. I share it here in case it is useful to
> someone.
>
> Best regards,
>
> Juan Manuel 
>
> #+begin_src emacs-lisp
> (defun my-org-replace-link-file (from to)
>   (save-excursion
> (goto-char (point-min))
> (while (re-search-forward org-bracket-link-regexp nil t)
>   (when (string-match-p from (match-string 1))
>   (replace-match (concat "[[file:" to "]]"))
>
> (defun my-org-rename-link-file-at-point ()
>   "Rename or move a file in an external link at point and
>   update the link path"
>   (interactive)
>   (let* ((curr-dir (abbreviate-file-name default-directory))
>(current-path (org-element-property :path (org-element-context)))
>(new-path (read-file-name "Rename file at point to: " current-path)))
> (rename-file current-path new-path)
> (message (concat "moved to: " new-path))
> (if (directory-name-p new-path)
>   (setq new-path (concat new-path (file-name-nondirectory current-path)))
>   (setq new-path new-path))
> (my-org-replace-link-file current-path
> (replace-regexp-in-string curr-dir "" new-path
>
> #+end_src
>

Thanks for sharing! It'd be great if it worked for attachments as well,
but that is a whole can of worms.

Cheers,

-- 
João Pedro de Amorim Paula
IT undergraduate at Universidade Federal do Rio Grande do Norte (UFRN)

Re: Cannot link to files with no extension

[Colin Baxter]

Hello, Bhavin,
> Bhavin Gandhi  writes:

> Hello Colin,
> On Wed, 9 Mar 2022 at 02:24, Colin Baxter  wrote:
>> Org-mode cannot link to files without an extension. I therefore
>> cannot use org-store-link for org-journal files, etc.

> I'm not able to reproduce this on the latest main branch. I tried
> this with Emacs 28.0.91:

> Opened the COPYING file from org-mode repository.  Executed M-x
> org-store-link Created test.org and did C-c C-l.

> I was able to create a link and open it with C-c C-o.

> Can you add more details like version, and steps to reproduce with
> emacs -Q?

> -- Regards, Bhavin Gandhi (bhavin192) | https://geeksocket.in

Thanks for your reply.

1. Touch two files in some directory:
   touch a.org , touch z 

2. emacs -Q 

3. C-x f a.org  and C-x f z 

4. Write some text in each file
   (I suppose this is not really necessary).

5. Close the buffer z.

6. In a.org enter [[file:./z][This is file z]] and save.

7. Click on the link.

8. Message "Running less in /path/to/z ... done", but link does not
   open.

9. I get the same if I use C-c C-o.

10. Copy z to z.org.

11. In a.org enter [[file:./z.org][This is file z.org]] and save.

12. Link now opens if it's clicked or C-c C-o is used.

This test was done with emacs-29.0.50 and org-version 9.52. I'm on
Debian 4.9.290-1.

I hope this helps.

Best wishes,

Colin.

Re: Cannot link to files with no extension

[Bhavin Gandhi]

Hello Colin,

On Wed, 9 Mar 2022 at 02:24, Colin Baxter  wrote:
> Org-mode cannot link to files without an extension. I therefore cannot
> use org-store-link for org-journal files, etc.

I'm not able to reproduce this on the latest main branch. I tried this with
Emacs 28.0.91:

Opened the COPYING file from org-mode repository.
Executed M-x org-store-link
Created test.org and did C-c C-l.

I was able to create a link and open it with C-c C-o.

Can you add more details like version, and steps to reproduce with
emacs -Q?

-- 
Regards,
Bhavin Gandhi (bhavin192) | https://geeksocket.in

bug-tracker: How to response/subscribe to a bug-thread

[c . buhtz]

Hello,
I still try to become warm with the bug-tracking-system you are using.

There is a known bug that is also tracked on the "dashboard" 
(https://updates.orgmode.org/) as "Inconsistent handling of id: links to 
other file during publish".

https://list.orgmode.org/12368452.sVpYeFqCzH@pluto/

I was not subscribed to the list when this thread comes up. So I have no 
mail here I can reply-to. I can I answer to that thread?


Side question: I can I monitor that thread/bug without being subscribed 
to the list? The "dashboard" seems not to have any subscribe, monitor or 
feed mechanism. The "Atom" feed (https://list.orgmode.org/new.atom) is 
only for complete list not for one thread.


Kind
Christian

Re: ox-publish: Some starting problems

[c . buhtz]

Dear Max,

thank's a lot for your help and your patience with a newbie.

Am 09.03.2022 16:32 schrieb Max Nikulin:

3.
I use (setq org-export-with-broken-links t) with and without 
":with-broken-links "mark"" to prevend ox-publish stopping when there 
are broken links. I swear and I also checked that there are only a few 
of them. But in the HTML output all links are gone. No links. No text 
for the links.


If you insist on setq than try
   (setq org-export-with-broken-links 'mark)
without :with-broken-links. You can get correct value using easy
customization interface. It does not matter for
`org-export-with-broken-links', but some custom variables have :set
property, so the following may be generally better
   (custom-set-variables
'(org-export-with-broken-links 'mark))


Do you mean that (setq org-export-with-broken-links 'mark) is the same 
as :with-broken-links mark? This are just two different ways to set the 
same thing?

How do I know as a newbie? ;)

Why using custom-set variables here? Is there something wrong with just 
doing

(org-export-with-broken-links t)
?

I tried to reproduce this in a minimal example with two new nodes. But 
for them the links are generated.


It seems, changing project options or global variables does not lead
to updating of the files if the sources have not modified.


I do not understand. Do you a see a solution for the problem?


There is a known problem with id links. They may be broken if they
lead to another file:
inkbottle. org-id with ox-html. Sat, 14 Aug 2021 00:28:35 +0200
https://list.orgmode.org/4617246.m1MCmUpgFQ@pluto/


Great to know. Is there a way to monitor (subscribe) to the "dashboard"? 
A bugtracker where I can not track a bug is not a bugtracker. :D
OK, bugs going to the mailing list. But am I allowed to attach extra 
files (zip) to my mails to the mailinglist? Some bug reports need 
attached files. But I learned and agree that it is rude to attach files 
to a mailing list.


Back to the bug.
The bug-thread is hard for me to understand because of a lot of internal 
details. What is the current essence? Currently there is no way to use 
ox-publish with org-roam-v2 generated org files which use IDs as links?

But as I told sometimes the links are generated.

Btw: Also in my minimal working example I was not able to surly 
reproduce the problem. Sometimes it works sometimes not. I also deleted 
~/.emacs.d/org-roam.db, ~/.org-timestamps and ~/.emacs-d/.orgid-indexes 
(I forget the correct name for the latter).



org-mode is a mode, ox-publish maybe a package (actually unsure).
I thought it was a separate thing because of "(require ox-publish)". 
Again: How do I as a newbie know?



That page specifies related global variable, so you can try
`describe-variable' C-h v with the related name.


I know that and I did. But this is waste of time when I have to do this 
for each of the variable in that big list.



6.
Is there a way to integrated backlinks into output?


Do you mean something specific to org-roam?


I am not sure but maybe yes. ;)
I can do C-c n l which invokes org-roam-buffer-toogle and shows me an 
extra buffer with a list of all nodes (org-files?) which are linking to 
the current open node.

Re: ox-publish: Some starting problems

[Max Nikulin]

On 09/03/2022 16:41, c.bu...@posteo.jp wrote:
Should I then open a bug report? Do I understand 
https://orgmode.org/worg/org-issues.html correct that there is no 
"usual" bug tracker but just he mailing list where I have to post bugs?


There is a kind of dashboard at https://updates.orgmode.org Someone need 
to confirm the bug report before it will appear there.


Accordingly to https://orgmode.org/org.html#Feedback
you may use
   M-x org-submit-bug-report 
or just to send description of the problem to this list.

There is a subpackage for Org Mode at https://debbugs.gnu.org, but the 
message will be anyway redirected to this mail list. Bugs reported 
against Emacs instead of Org Mode have greater chance to remain 
unnoticed for some period of time. Answers sent to the mail list 
directly instead of the bug email address will not appear in debbugs 
archives. Notice the following as well:


https://list.orgmode.org/87v9kavoms@gnu.org/
Bastien. Re: issue tracker? Mon, 01 Jun 2020 16:36:59 +0200
> I'd like to keep this mailing list as the central place to discuss
> everything about Org, including bug reports.

Re: ox-publish: Some starting problems

[Max Nikulin]

On 09/03/2022 15:55, c.buhtz wrote:


1.
Is this mailing list the right place to discuss ox-publish related 
topics? The ox-publish.el only contains two e-mail addresses?


ox-publish.el belongs to the "core" part of Org mode, so this mail list 
is an appropriate place. There is a chance to get response from the Org 
maintainers. I do not follow stackexchange and reddit topics so I can 
tell nothing concerning probability to get some answer there.



3.
I use (setq org-export-with-broken-links t) with and without 
":with-broken-links "mark"" to prevend ox-publish stopping when there 
are broken links. I swear and I also checked that there are only a few 
of them. But in the HTML output all links are gone. No links. No text 
for the links.


If you insist on setq than try
   (setq org-export-with-broken-links 'mark)
without :with-broken-links. You can get correct value using easy 
customization interface. It does not matter for 
`org-export-with-broken-links', but some custom variables have :set 
property, so the following may be generally better

   (custom-set-variables
'(org-export-with-broken-links 'mark))

When specifying the publish project option, do not add quotes around 
"mark", the string (unlike the symbol) is considered as t. Unfortunately 
no warning is issued.


I tried to reproduce this in a minimal example with two new nodes. But 
for them the links are generated.


It seems, changing project options or global variables does not lead to 
updating of the files if the sources have not modified.


First I thought ox-publish has a problem with org-roam-v2 id-links. But 
the two new created nodes just for testing where working well. The older 
nodes (just 2 months old) also using id-links and where created with the 
same Emacs and org-roam version.


There is a known problem with id links. They may be broken if they lead 
to another file:

inkbottle. org-id with ox-html. Sat, 14 Aug 2021 00:28:35 +0200
https://list.orgmode.org/4617246.m1MCmUpgFQ@pluto/


4.
ox-publish ignores newlines. Two short lines in the org-file becomes one 
line in the HTML content.


I suppose, it is unrelated to ox-publish, it is behavior of ox 
(org-export) and org-element parser. Paragraphs are separated by empty 
lines. Likely you need some markup, e.g.

   #+begin_example
   ...
   #+end_example
block.


5.
I am not totally new to Emacs but quit fresh. So I have two questions 
about how to handle the documentation and help informations here.
a) I tried to "descrbie" the mode "ox-publish". But Emacs only offers me 
an "describe-mode" which describe all currently existing nodes. There is 
nothing like "describe-mode MODENAME". How can I handle that?


org-mode is a mode, ox-publish maybe a package (actually unsure). 
Unfortunately e.g. `describe-package' C-h P org shows built-in version 
of org for me even though git main HEAD is actually loaded. It extracts 
some comments from the top of the source file.


b) I another thread I was pointed to 
https://orgmode.org/manual/Publishing-options.html . There is no 
description about the options they are only listed. This does not help 
me. Maybe there are some useful options that could solve some of my 
problems. But without description I am not able to decide or know.


That page specifies related global variable, so you can try 
`describe-variable' C-h v with the related name.


I do not know if you are familiar with GNU "info" 
https://www.gnu.org/software/emacs/manual/html_node/info/ that allows to 
read e.g. Org Manual in Emacs. There is a variable index 
https://orgmode.org/manual/Variable-Index.html but this case the entry 
leads to the "Export Settings" section already known to you.


Sometimes it is more convenient to search in the manual variant exported 
as a single HTML page https://orgmode.org/org.html


The last resort is reading source files.


6.
Is there a way to integrated backlinks into output?


Do you mean something specific to org-roam?

Re: [PATCH] lisp/ox.el: Add Persian/Farsi to org-export

[Max Nikulin]

On 04/03/2022 22:30, shosseinib wrote:

* Add Persian/Farsi translation to the org-export-dictionary variable at 
lisp/ox.el.
- Persian/Farsi is a native language to ~ 110 million speakers around the world 
(mostly in Iran, Afghanistan, Tajiskistan, Uzbekistan, and Iraq).
- "fa" abbreviation stands for "farsi" according to [[ISO 
639-1][https://en.wikipedia.org/wiki/ISO_639-1]].


Thank you for contributing. Your patch is tracked on 
https://updates.orgmode.org/ Some patches are committed before a major 
release, so it may take months to complete.


Unfortunately your first message did not get any response:
https://list.orgmode.org/fdfdadd20b2b145c8cf507787cf3e...@ut.ac.ir
It seems, nobody on the mail list can independently confirm that the 
suggested change has no typos and follows established practice. It seems 
quotes are consistent with ones specified in the Common Locale Data 
Repository https://cldr.unicode.org/ but it is difficult for me to check 
if more strings that might be available there are consistent.


I do not see your name in the list of contributor who have signed the 
FSF copyright form, maintainers may have a fresher version of the list. 
I am not sure but your patch may exceed the limit for TINYCHANGE, so 
some paperwork may be required before it will be possible to accept the 
patch. For details see https://orgmode.org/worg/org-contribute.html and 
https://www.gnu.org/software/emacs/CONTRIBUTE

Re: ox-publish: Some starting problems

[c . buhtz]

Some additional information.

Am 09.03.2022 09:55 schrieb c.bu...@posteo.jp:

2.
Because ox-publish is skipping "unmodified files"
[..]
nothing is generated anymore.


Doing this forces ox-publish to generated everything
M: (org-publish "projectname" t)



3.
[..]
in the HTML output all links are gone. No links. No text
for the links.
I tried to reproduce this in a minimal example with two new nodes. But
for them the links are generated.
[..]


I need to correct myself here. After forcing new generation of HTML 
content the links in the new test nodes also gone.
I am confused. I need to do further investigation here and create a 
minimal reproducible setup to find out the steps to reproduce this 
behavior.
Should I then open a bug report? Do I understand 
https://orgmode.org/worg/org-issues.html correct that there is no 
"usual" bug tracker but just he mailing list where I have to post bugs?



4.
ox-publish ignores newlines. Two short lines in the org-file becomes
one line in the HTML content.


I am still not sure but it looks like that this does fix that problem.
(setq org-export-preserve-breaks t)

ox-publish: Some starting problems

[c . buhtz]

Hello together,

I was able to generate HTML files of my org-roam (v2) nodes. But I have 
some problems and need to be pointed into the right direction.


1.
Is this mailing list the right place to discuss ox-publish related 
topics? The ox-publish.el only contains two e-mail addresses?


2.
Because ox-publish is skipping "unmodified files" I deleted all HTML 
files between the publish-runs just to be sure that there are no side 
effects. But now when my output directory is totally empty ox-publish 
still keeps saying that it is skipping the unmodified files. So nothing 
is generated anymore. How can I handle that? Maybe resetting the 
"unmodified" flag somewhere? Or shouldn't ox-publish not only check for 
modifications but if there is something earlier generated content exist?


3.
I use (setq org-export-with-broken-links t) with and without 
":with-broken-links "mark"" to prevend ox-publish stopping when there 
are broken links. I swear and I also checked that there are only a few 
of them. But in the HTML output all links are gone. No links. No text 
for the links.
I tried to reproduce this in a minimal example with two new nodes. But 
for them the links are generated.

The links (of all nodes!) are working very well inside of org-roam.
Any idea how could go on with diagnosis here?
First I thought ox-publish has a problem with org-roam-v2 id-links. But 
the two new created nodes just for testing where working well. The older 
nodes (just 2 months old) also using id-links and where created with the 
same Emacs and org-roam version.


4.
ox-publish ignores newlines. Two short lines in the org-file becomes one 
line in the HTML content.


5.
I am not totally new to Emacs but quit fresh. So I have two questions 
about how to handle the documentation and help informations here.
a) I tried to "descrbie" the mode "ox-publish". But Emacs only offers me 
an "describe-mode" which describe all currently existing nodes. There is 
nothing like "describe-mode MODENAME". How can I handle that?
b) I another thread I was pointed to 
https://orgmode.org/manual/Publishing-options.html . There is no 
description about the options they are only listed. This does not help 
me. Maybe there are some useful options that could solve some of my 
problems. But without description I am not able to decide or know.


6.
Is there a way to integrated backlinks into output?