Re: [BUG] Got error opening existing org file in emacs 30.1 [9.7.11 (release_9.7.11 @ /usr/share/emacs/30.1/lisp/org/)]

2025-02-28 Thread Rohit Patnaik
I tried opening the linked file with the latest org-mode from git, as of commit
53cd3f83c96728 and I was not able to reproduce the issue. I was able to open the
file, move around in it, make edits, etc. without any problems.

However, I am using Emacs 29.4, not 30.1. Could that have something to do with
it as well?

Thanks,
Rohit



[BUG] Got error opening existing org file in emacs 30.1 [9.7.11 (release_9.7.11 @ /usr/share/emacs/30.1/lisp/org/)]

2025-02-28 Thread Steinar Bang


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.


Got an error opening this file 
https://github.com/steinarb/bang-bompom/blob/master/README.org

Emacs  : GNU Emacs 30.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.38, 
cairo version 1.16.0)
 of 2025-02-27, modified by Debian
Package: Org mode version 9.7.11 (release_9.7.11 @ 
/usr/share/emacs/30.1/lisp/org/)

current state:
==
(setq
 org-yank-image-file-name-function 'org-yank-image-autogen-filename
 org-persist-before-write-hook '(org-element--cache-persist-before-write)
 org-html-format-headline-function 'org-html-format-headline-default-function
 org-html-format-drawer-function #[514 "\207" [] 3 
("/usr/share/emacs/30.1/lisp/org/ox-html.elc" . 22502)]
 org-log-into-drawer t
 org-latex-format-inlinetask-function 
'org-latex-format-inlinetask-default-function
 org-structure-template-alist '(("w" . "WP") ("a" . "export ascii") ("c" . 
"center") ("C" . "comment") ("e" . "example") ("E" . "export") ("h" . "export 
html") ("l" . "export latex")
("q" . "quote") ("s" . "src") ("v" . "verse"))
 org-speed-command-hook '(org-speed-command-activate 
org-babel-speed-command-activate)
 org-persist-after-read-hook '(org-element--cache-persist-after-read)
 org-confirm-elisp-link-function 'yes-or-no-p
 org-latex-format-headline-function 'org-latex-format-headline-default-function
 org-latex-format-drawer-function #[514 "\207" [] 3 
("/usr/share/emacs/30.1/lisp/org/ox-latex.elc" . 36340)]
 org-mode-hook '(#[0 "\301\211\207" [imenu-create-index-function 
org-imenu-get-tree] 2] turn-on-visual-line-mode turn-off-auto-fill 
turn-on-font-lock
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-fold-show-all append local] 5]
 #[0 "\300\301\302\303\304$\207" [add-hook 
change-major-mode-hook org-babel-show-result-all append local] 5] 
org-babel-result-hide-spec org-babel-hide-all-hashes)
 org-load-hook '(#[nil
   ((add-to-list 'auto-mode-alist '("\\.org\\'" . org-mode)) 
(setq org-clock-into-drawer "CLOCK") (setq org-cycle-include-plain-lists 
'integrate)
(setq org-export-backends '(ascii html icalendar latex md 
odt)) (setq org-export-with-drawers '("LOGBOOK")) (setq org-log-into-drawer t) 
(setq org-startup-folded t)
(global-set-key "l" 'org-store-link) (global-set-key "a" 
'org-agenda) (global-set-key "b" 'org-iswitchb) (add-hook 'org-mode-hook 
'turn-on-font-lock)
(add-hook 'org-mode-hook 'turn-off-auto-fill) (add-hook 
'org-mode-hook 'turn-on-visual-line-mode))
   nil]
 )
 org-confirm-shell-link-function 'yes-or-no-p
 org-odt-format-headline-function 'org-odt-format-headline-default-function
 org-archive-hook '(org-attach-archive-delete-maybe)
 org-metaup-hook '(org-babel-load-in-session-maybe)
 org-occur-hook '(org-first-headline-recenter)
 org-html-format-inlinetask-function 
'org-html-format-inlinetask-default-function
 org-ascii-format-drawer-function #[771 "\207" [] 4 
("/usr/share/emacs/30.1/lisp/org/ox-ascii.elc" . 11828)]
 org-link-from-user-regexp "|\\"
 org-bibtex-headline-format-function 'org-bibtex-headline-format-default
 org-link-parameters '(("eww" :follow org-eww-open :store org-eww-store-link) 
("rmail" :follow org-rmail-open :store org-rmail-store-link)
   ("mhe" :follow org-mhe-open :store org-mhe-store-link) 
("irc" :follow org-irc-visit :store org-irc-store-link :export org-irc-export)
   ("info" :follow org-info-open :export org-info-export 
:store org-info-store-link :insert-description org-info-description-as-command)
   ("gnus" :follow org-gnus-open :store 
org-gnus-store-link) ("docview" :follow org-docview-open :export 
org-docview-export :store org-docview-store-link)
   ("bibtex" :follow org-bibtex-open :store 
org-bibtex-store-link)
   ("bbdb" :follow org-bbdb-open :export org-bbdb-export 
:complete org-bbdb-complete-link :store org-bbdb-store-link) ("w3m" :store 
org-w3m-store-link)
   ("doi" :follow org-link-doi-open :export 
org-link-doi-export) ("attachment" :follow org-attach-follow :complete 
org-attach-complete-link)
   ("id" :follow org-id-open :store 
org-id-store-link-maybe) ("file+sys") ("file+emacs") ("shell" :follow 
org-link--open-shell)
   ("news" :follow #[514 "\301\300\302Q\"\207" ["news" 
browse-url ":"] 6 ("/usr/share/emacs/30.1/lisp/org/ol.elc" . 51215)])
   ("mailto" :follow #[514 "\301\300\302Q\"\207" ["mailto" 
browse-url ":"] 6 ("/usr/share/emacs/30.1/lisp/o

Org Agenda errors if agenda file is in column view

2025-02-28 Thread Rens Oliemans
I'm not sure if this is a bug, but it feels like one and I don't see this
behaviour documented anywhere.

The "problem": If an agenda file is in column view (and therefore read-only),
contains a date for the current week, and you open the agenda view for the
current week, the agenda fails with the error string:

   Text is read-only: #("Type 'e' to edit property" ...)

For more information, check the attached file, which will reproduce the error
with emacs -Q. I tested this on current main and on release_9.6.15.

If this is not a bug but a misconception on my part, please let me know! This
errors the Org agenda and I therefore have to exit that, quit column view in the
corresponding agenda file, and re-open Org agenda again, so I'd like to prevent
this in the future. If it is a bug, I'd be happy to try and fix it, but I would
need some pointers on where to start.

Best,
Rens

* hello <2025-02-28 vr>

#+begin_src elisp
  (org-columns)
  (org-agenda-file-to-front)
  (org-agenda nil "a")
#+end_src


Re: Org Agenda errors if agenda file is in column view

2025-02-28 Thread Rick Lupton
I have also come across this but not reported it yet (thanks for doing so!)

I suspect the read only property could be removed in 
org-agenda-finalize-entries, which already does some modifications of the text 
properties. 

On Fri, 28 Feb 2025, at 11:05 AM, Rens Oliemans wrote:
> I'm not sure if this is a bug, but it feels like one and I don't see this
> behaviour documented anywhere.
>
> The "problem": If an agenda file is in column view (and therefore read-only),
> contains a date for the current week, and you open the agenda view for the
> current week, the agenda fails with the error string:
>
>Text is read-only: #("Type 'e' to edit property" ...)
>
> For more information, check the attached file, which will reproduce the error
> with emacs -Q. I tested this on current main and on release_9.6.15.
>
> If this is not a bug but a misconception on my part, please let me know! This
> errors the Org agenda and I therefore have to exit that, quit column view in 
> the
> corresponding agenda file, and re-open Org agenda again, so I'd like to 
> prevent
> this in the future. If it is a bug, I'd be happy to try and fix it, but I 
> would
> need some pointers on where to start.
>
> Best,
> Rens
>
>
> Attachments:
> * test.org



Re: [BUG] Incorrect LaTeX export when using images in a table to display them side-by-side. [9.7.5 (release_9.7.5 @ /home/dadinn/.emacs.d/straight/build/org/)]

2025-02-28 Thread Ihor Radchenko
Pedro Andres Aranda Gutierrez  writes:

> Thanks!
> I see that the list of possibilities growing quite quickly.. Could we
> please start by defining the possible cases?
>
> 1. Image embedded in  text in a paragraph
>
> This file:image.png could be an emoticon
>
> 2. Images in a plain table
>
> | file:image1.png | file:image2.png |
>
> 3. Images in a table controlled with attributes (your example)
>
> #+ATTR_LATEX: :environment longtable :align l|lp{3cm}r|l
> | file:image1.png | file:image2.png |
>
> Any more?

I think that the most important special case we need to consider is when
the image is "standalone" - image being a single object in paragraph:

file:image.png

or

#+attr_latex: :width 300px
file:image.png

Such images are currently handled specially by ox-html, for example (see
`org-html-standalone-image-p').

We can also safely assume that all the affiliated keywords apply to such
standalone images.

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



Re: Org Crypt problems

2025-02-28 Thread Leo Butler
On Thu, Feb 27 2025, David Masterson  wrote:

> Leo Butler  writes:
>
>> On Tue, Feb 25 2025, David Masterson  wrote:
>>
>>> 1.   If you enter a bad password (even a blank password) to
>>>  org-decrypt-ent*, how do you tell Emacs to forget the password so
>>>  that you can enter the right one?
>>
>> Does
>>
>> M-x auth-source-forget-all-cached RET
>>
>> work for you?
>
> Hmm.
>
> This would work for me, but what about people who might encrypt
> different entries in Org with different passwords (or, for that matter,
> people using gpg elsewhere as well)?  It seems to hit a little nail with
> a big sledgehammer.
>
> I'll have to look at org-crypt.el some more.

Is the issue in org-crypt.el?

auth-source.el defines only that one command to remove cached data,
although there are functions to remove specific cached data.

Leo


Re: [PATCH] Sanitize links in headings to avoid broken Texinfo menus

2025-02-28 Thread Ihor Radchenko
Rudolf Adamkovič  writes:

> BTW, speaking of multi-page HTML exports, I suggest that, in the first
> version, instead of inventing side bars and what not, we match Texinfo
> exports, where at a certain level, headings become separate HTML pages
> with TOC for deeper levels.  That would also make the system usable for
> manuals, out of the box, sans the outstanding Org markup deficiencies.

May you share this in the relevant thread? Then, the patch author can
have a chance to see your idea.

> Well, then perhaps I could become a maintainer, in the meantime, if that
> helps, as I have a website generated with the Texinfo exporter, which I
> update on a daily basis, so I can spot problems early, etc.

Thanks! That would indeed help.
To become a maintainer, you will need to get write access to savannah by
creating account there and joining Emacs group. See
https://orgmode.org/worg/org-contribute.html#devs

Also, check out https://orgmode.org/worg/org-maintenance.html with some
useful information about maintenance.

And let me know when you finish registering - I will need to contact
Emacs maintainers to approve your write access.

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



Re: Select a region and yank a URL to create a link

2025-02-28 Thread jman

Ryan Prior via "General discussions about Org-mode."  
writes:

Lately I've noticed more applications supporting a method of creating a link by pasting a URL. The 
flow works like this:

1. write some text
2. select the text you want to linkify
3. paste a URL to turn the selected text into a named link


Just to be sure I understand: you are suggesting an alternate way to linkify a selected region of 
text, currently supported by the `*-insert-link` functions (bound to `C-c C-l`), correct?


Or is it something slightly different?

Cheers,



Re: Select a region and yank a URL to create a link

2025-02-28 Thread Rudolf Adamkovič
Ryan Prior via "General discussions about Org-mode."
 writes:

> Lately I've noticed more applications supporting a method of creating
> a link by pasting a URL. The flow works like this: [...]

What a smart, simple yet impactful, QOL improvement!  TIL.

> What do you think about adding this capability to org-mode? Since many
> plain-text writing interfaces are offering it, I'm sure other users
> will appreciate if Emacs does the same.

I would appreciate it and start using it right away.

Rudy
-- 
"The introduction of suitable abstractions is our only mental aid to
organize and master complexity."
--- Edsger Wybe Dijkstra, 1930-2002

Rudolf Adamkovič  [he/him]
http://adamkovic.org



Re: [PATCH] Sanitize links in headings to avoid broken Texinfo menus

2025-02-28 Thread Rudolf Adamkovič
Ihor Radchenko  writes:

> I'd love someone to revive the discussion on multipage export with
> more ideas on integration with ox.el. I myself plan to go back to it
> once I finally finish my backlog back from Aug. But my time is much
> more limited now.

BTW, speaking of multi-page HTML exports, I suggest that, in the first
version, instead of inventing side bars and what not, we match Texinfo
exports, where at a certain level, headings become separate HTML pages
with TOC for deeper levels.  That would also make the system usable for
manuals, out of the box, sans the outstanding Org markup deficiencies.

> For new LaTeX subsystem (Timothy's and Karthik's effort), it is not
> completely frozen, but, AFAIK, Timothy also has much less time these
> days. So, timeline is not short.

Bummer!

Well, then perhaps I could become a maintainer, in the meantime, if that
helps, as I have a website generated with the Texinfo exporter, which I
update on a daily basis, so I can spot problems early, etc.

Rudy
-- 
"All of humanity's problems stem from man's inability to sit quietly in
a room alone."  --- Blaise Pascal, Pensées, 1670

Rudolf Adamkovič  [he/him]
http://adamkovic.org