GNU bug report logs - #78823
[BUG] 31.0.50; org-babel-execute-src-block: Wrong type argument: integer-or-marker-p, nil

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 78823 in the body.
You can then email your comments to 78823 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Antero Mejr <mail <at> antr.me>
To: bug-gnu-emacs <at> gnu.org,emacs-orgmode <at> gnu.org
Subject: [BUG] 31.0.50; org-babel-execute-src-block: Wrong type argument:
 integer-or-marker-p, nil
Date: Wed, 18 Jun 2025 03:31:17 +0000

When exporting this Org buffer with org-html-export-to-html:

#+begin_src emacs-lisp :exports results
  (org-table-convert-region
   (point)
   (+ (point) (cadr (insert-file-contents "my-table.csv"))))
#+end_src

The export operation fails with a type error:

org-babel-execute-src-block: Wrong type argument: integer-or-marker-p, nil

The expected behavior is that the converted table will be inserted into
the document and exported by the backend.

While trying to debug this, I noticed that when
org-babel-execute-src-block is executed with the cursor inside the
#+begin_src block, the snippet runs and inserts the text content as
expected. However, when org-babel-execute-src-block is run with the
cursor just before the #+begin_src block, the same type error occurs.
That was also unexpected.





In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
 3.24.33, cairo version 1.16.0) of 2025-05-04 built on pop-os
Repository revision: 159e3a981ed5482393182b036e38818d42405c90
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.12101004
System Description: Pop!_OS 22.04 LTS

Configured features:
ACL CAIRO DBUS FREETYPE GIF GLIB GMP GNUTLS GPM GSETTINGS HARFBUZZ JPEG
LCMS2 LIBOTF LIBSELINUX LIBSYSTEMD LIBXML2 M17N_FLT MODULES NOTIFY
INOTIFY PDUMPER PNG RSVG SECCOMP SOUND THREADS TIFF TOOLKIT_SCROLL_BARS
X11 XDBE XIM XINERAMA XINPUT2 XPM XRANDR GTK3 ZLIB

Important settings:
  value of $LANG: en_US.UTF-8
  value of $XMODIFIERS: @im=ibus
  locale-coding-system: utf-8-unix

Major mode: Messages

Minor modes in effect:
  pixel-scroll-precision-mode: t
  global-auto-revert-mode: t
  server-mode: t
  global-hide-mode-line-mode: t
  hide-mode-line-mode: t
  hexl-follow-ascii: t
  csv-field-index-mode: t
  override-global-mode: t
  global-eldoc-mode: t
  eldoc-mode: t
  show-paren-mode: t
  electric-indent-mode: t
  mouse-wheel-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  font-lock-mode: t
  minibuffer-regexp-mode: t
  buffer-read-only: t
  column-number-mode: t
  line-number-mode: t
  transient-mark-mode: t
  auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t

Load-path shadows:
None found.

Features:
(shadow mail-extr emacsbug lisp-mnt vc-git diff-mode track-changes
vc-dispatcher oc-basic ol-eww eww vtable mule-util url-queue mm-url
ol-rmail ol-mhe ol-irc ol-info ol-gnus nnselect gnus-art mm-uu mml2015
mm-view mml-smime smime dig gnus-sum shr pixel-fill kinsoku url-file svg
dom gnus-demon nntp gnus-group gnus-undo gnus-start gnus-dbus dbus xml
gnus-cloud nnimap nnmail mail-source utf7 gnus-spec gnus-win nnoo
gnus-int gnus-range message sendmail yank-media rfc822 mml mml-sec epa
derived epg rfc6068 epg-config mm-decode mm-bodies mm-encode mail-parse
rfc2231 rfc2047 rfc2045 ietf-drums mailabbrev gmm-utils mailheader gnus
nnheader gnus-util mail-utils range mm-util mail-prsvr wid-edit
ol-docview doc-view jka-compr image-mode exif dired dired-loaddefs
ol-bibtex bibtex ol-bbdb ol-w3m ol-doi org-link-doi em-unix em-term term
disp-table ehelp em-script em-prompt em-pred em-ls em-hist em-glob
em-extpipe em-cmpl em-dirs em-basic em-banner em-alias em-tramp tramp
trampver tramp-integration tramp-message tramp-compat shell parse-time
iso8601 tramp-loaddefs esh-mode esh-var eshell esh-cmd esh-ext esh-proc
esh-opt esh-io esh-arg esh-module esh-module-loaddefs esh-util files-x
display-fill-column-indicator exwm exwm-input xcb-keysyms xcb-xkb
exwm-manage exwm-floating xcb-cursor xcb-render exwm-layout
exwm-workspace exwm-core xcb-ewmh xcb-icccm xcb xcb-xproto xcb-types
xcb-debug kmacro compat pixel-scroll cua-base advice autorevert
filenotify pcase server ox-man ox-odt rng-loc rng-uri rng-parse
rng-match rng-dt rng-util rng-pttrn nxml-parse nxml-ns nxml-enc xmltok
nxml-util ox-latex ox-icalendar org-agenda ox-html table ox-ascii
ox-publish ox org-attach org-element org-persist org-id org-refile
org-element-ast inline org ob ob-tangle ob-ref ob-lob ob-table org-macro
org-src sh-script treesit executable ob-comint org-pcomplete pcomplete
org-list org-footnote org-faces org-entities time-date org-version
ob-emacs-lisp org-table org-keys org-loaddefs find-func cal-menu
calendar cal-loaddefs avl-tree generator ol oc ob-exp ob-core org-cycle
org-fold org-fold-core org-compat ob-eval org-macs format-spec
hide-mode-line org-present visual-fill-column sml-mode compile
text-property-search comint ansi-osc ansi-color ring smie proof-general
totp hexl gnutls puny bindat markdown-mode rx color thingatpt noutline
outline csv-mode sort cl-extra help-mode use-package use-package-ensure
use-package-delight use-package-diminish use-package-bind-key bind-key
easy-mmode use-package-core finder-inf csv-mode-autoloads exwm-autoloads
hide-mode-line-autoloads markdown-mode-autoloads org-present-autoloads
info proof-general-autoloads proof-site proof-autoloads
sml-mode-autoloads totp-autoloads visual-fill-column-autoloads
xelb-autoloads package browse-url xdg url url-proxy url-privacy
url-expand url-methods url-history url-cookie generate-lisp-file
url-domsuf url-util mailcap url-handlers url-parse auth-source cl-seq
eieio eieio-core cl-macs icons password-cache json subr-x map byte-opt
gv bytecomp byte-compile url-vars cl-loaddefs cl-lib rmc iso-transl
tooltip cconv eldoc paren electric uniquify ediff-hook vc-hooks
lisp-float-type elisp-mode mwheel term/x-win x-win term/common-win x-dnd
touch-screen tool-bar dnd fontset image regexp-opt fringe tabulated-list
replace newcomment text-mode lisp-mode prog-mode register page tab-bar
menu-bar rfn-eshadow isearch easymenu timer select scroll-bar mouse
jit-lock font-lock syntax font-core term/tty-colors frame minibuffer
nadvice seq simple cl-generic indonesian philippine cham georgian
utf-8-lang misc-lang vietnamese tibetan thai tai-viet lao korean
japanese eucjp-ms cp51932 hebrew greek romanian slovak czech european
ethiopic indian cyrillic chinese composite emoji-zwj charscript charprop
case-table epa-hook jka-cmpr-hook help abbrev obarray oclosure
cl-preloaded button loaddefs theme-loaddefs faces cus-face macroexp
files window text-properties overlay sha1 md5 base64 format env
code-pages mule custom widget keymap hashtable-print-readable backquote
threads dbusbind inotify lcms2 dynamic-setting system-font-setting
font-render-setting cairo gtk x-toolkit xinput2 x multi-tty move-toolbar
make-network-process tty-child-frames emacs)

Memory information:
((conses 16 561181 53214) (symbols 48 44667 1) (strings 32 194210 2237)
 (string-bytes 1 4770369) (vectors 16 78918) (vector-slots 8 712653 11540)
 (floats 8 531 77) (intervals 56 466 0) (buffers 984 15))

Message #8 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Antero Mejr <mail <at> antr.me>
Cc: 78823 <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50;
 org-babel-execute-src-block: Wrong type argument:
 integer-or-marker-p, nil
Date: Wed, 18 Jun 2025 14:58:44 +0300

> From: Antero Mejr <mail <at> antr.me>
> Date: Wed, 18 Jun 2025 03:31:17 +0000
> 
> When exporting this Org buffer with org-html-export-to-html:
> 
> #+begin_src emacs-lisp :exports results
>   (org-table-convert-region
>    (point)
>    (+ (point) (cadr (insert-file-contents "my-table.csv"))))
> #+end_src
> 
> The export operation fails with a type error:
> 
> org-babel-execute-src-block: Wrong type argument: integer-or-marker-p, nil
> 
> The expected behavior is that the converted table will be inserted into
> the document and exported by the backend.
> 
> While trying to debug this, I noticed that when
> org-babel-execute-src-block is executed with the cursor inside the
> #+begin_src block, the snippet runs and inserts the text content as
> expected. However, when org-babel-execute-src-block is run with the
> cursor just before the #+begin_src block, the same type error occurs.
> That was also unexpected.

Thanks, but please report this to the Org developers first.

Message #11 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Antero Mejr <mail <at> antr.me>, 78823 <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Thu, 19 Jun 2025 06:02:29 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

> Thanks, but please report this to the Org developers first.

To be fair, Antero reported the bug _both_ to debbugs and Org mailing
list (in CC). So, it has been received on Org list.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Message #14 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Thu, 19 Jun 2025 09:31:40 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Antero Mejr <mail <at> antr.me>, 78823 <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
> Date: Thu, 19 Jun 2025 06:02:29 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > Thanks, but please report this to the Org developers first.
> 
> To be fair, Antero reported the bug _both_ to debbugs and Org mailing
> list (in CC). So, it has been received on Org list.

I've seen that, but TBH I don't understand the purpose of this
duplicate reporting.

Should I close this bug?

Message #17 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Thu, 19 Jun 2025 06:42:57 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

> I've seen that, but TBH I don't understand the purpose of this
> duplicate reporting.

I suspect that it is the usual confusion on where to send bug reports -
to Org ML or to Emacs bugs. This time, Antero played it safe and did
both, which is understandable.

> Should I close this bug?

Feel free for debbugs. The bug is already tracked on Org side.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Message #22 received at 78823-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: mail <at> antr.me, 78823-done <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Thu, 19 Jun 2025 10:10:52 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, emacs-orgmode <at> gnu.org
> Date: Thu, 19 Jun 2025 06:42:57 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > I've seen that, but TBH I don't understand the purpose of this
> > duplicate reporting.
> 
> I suspect that it is the usual confusion on where to send bug reports -
> to Org ML or to Emacs bugs. This time, Antero played it safe and did
> both, which is understandable.

What can we do to avoid such confusion?

> > Should I close this bug?
> 
> Feel free for debbugs. The bug is already tracked on Org side.

Thanks, done.  We can reopen if it turns out to be an Emacs core bug.

Message #25 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Richard Stallman <rms <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, eliz <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50;
 org-babel-execute-src-block: Wrong type argument:
 integer-or-marker-p, nil
Date: Sun, 22 Jun 2025 22:22:11 -0400

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > I suspect that it is the usual confusion on where to send bug reports -
  > > to Org ML or to Emacs bugs. This time, Antero played it safe and did
  > > both, which is understandable.

  > What can we do to avoid such confusion?

1. It is not a disaster.

2, We cn more clearl state wat to do at the op of each source file of Org.
A couple of lines, the same in each file, should do it.


-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)

Message #28 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: rms <at> gnu.org
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50;
 org-babel-execute-src-block: Wrong type argument:
 integer-or-marker-p, nil
Date: Mon, 23 Jun 2025 14:28:56 +0300

> From: Richard Stallman <rms <at> gnu.org>
> Cc: 78823 <at> debbugs.gnu.org, eliz <at> gnu.org, mail <at> antr.me
> Date: Sun, 22 Jun 2025 22:22:11 -0400
> 
>   > > I suspect that it is the usual confusion on where to send bug reports -
>   > > to Org ML or to Emacs bugs. This time, Antero played it safe and did
>   > > both, which is understandable.
> 
>   > What can we do to avoid such confusion?
> 
> 1. It is not a disaster.
> 
> 2, We cn more clearl state wat to do at the op of each source file of Org.
> A couple of lines, the same in each file, should do it.

I'd prefer the report-emacs-bug command itself look at the text of the
report and intuit that it might be about Org, then ask the user.  This
is more easily discoverable, and probably also more reliable.

Message #31 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Antero Mejr <mail <at> antr.me>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Mon, 23 Jun 2025 22:02:16 +0000

[Message part 1 (text/plain, inline)]

Eli Zaretskii <eliz <at> gnu.org> writes:
>
> I'd prefer the report-emacs-bug command itself look at the text of the
> report and intuit that it might be about Org, then ask the user.  This
> is more easily discoverable, and probably also more reliable.

I think adding a command "report-org-bug" that is an alias for
"org-submit-bug-report" may also be helpful. I looked for that before
submitting but couldn't find the right command name. I can submit a
patch to Org to add it if you want.

I also attached a patch with a regex to report-emacs-bug-hook to check
for Org stuff.

Sorry about the mix up.

[0001-Check-for-text-about-Org-mode-when-submitting-emacs-.patch (text/x-diff, attachment)]

Message #34 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Antero Mejr <mail <at> antr.me>, Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 28 Jun 2025 12:57:29 +0300

> From: Antero Mejr <mail <at> antr.me>
> Cc: rms <at> gnu.org,  78823 <at> debbugs.gnu.org
> Date: Mon, 23 Jun 2025 22:02:16 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> >
> > I'd prefer the report-emacs-bug command itself look at the text of the
> > report and intuit that it might be about Org, then ask the user.  This
> > is more easily discoverable, and probably also more reliable.
> 
> I think adding a command "report-org-bug" that is an alias for
> "org-submit-bug-report" may also be helpful. I looked for that before
> submitting but couldn't find the right command name. I can submit a
> patch to Org to add it if you want.
> 
> I also attached a patch with a regex to report-emacs-bug-hook to check
> for Org stuff.
> 
> Sorry about the mix up.

Thanks.

Ihor, any comments to these changes?

Message #37 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Antero Mejr <mail <at> antr.me>, 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 28 Jun 2025 10:02:50 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> I also attached a patch with a regex to report-emacs-bug-hook to check
>> for Org stuff.
>> 
> ...
> Ihor, any comments to these changes?

Should it also cover other packages where the bug reports should go to
dedicated mailing list?

We had a similar discussion in the past about making report-org-bug an
alias to org-submit-bug-report, and did not do it because it is awkward
when only Org mode is doing it, but not other packages.
See https://list.orgmode.org/orgmode/874kw7o4ry.fsf <at> gnu.org/

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Message #40 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 28 Jun 2025 13:43:49 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: Antero Mejr <mail <at> antr.me>, rms <at> gnu.org, 78823 <at> debbugs.gnu.org
> Date: Sat, 28 Jun 2025 10:02:50 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> I also attached a patch with a regex to report-emacs-bug-hook to check
> >> for Org stuff.
> >> 
> > ...
> > Ihor, any comments to these changes?
> 
> Should it also cover other packages where the bug reports should go to
> dedicated mailing list?

Which ones?

And in any case, we don't need to wait with this patch until we also
have similar patches for other packages.  These issues could be
handled piecemeal.

> We had a similar discussion in the past about making report-org-bug an
> alias to org-submit-bug-report, and did not do it because it is awkward
> when only Org mode is doing it, but not other packages.
> See https://list.orgmode.org/orgmode/874kw7o4ry.fsf <at> gnu.org/

That part is up to you.

Message #43 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 28 Jun 2025 15:31:16 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Should it also cover other packages where the bug reports should go to
>> dedicated mailing list?
>
> Which ones?

TRAMP (tramp-submit-bug), maybe also CC mode and modus themes.

> And in any case, we don't need to wait with this patch until we also
> have similar patches for other packages.  These issues could be
> handled piecemeal.

You decide.

>> We had a similar discussion in the past about making report-org-bug an
>> alias to org-submit-bug-report, and did not do it because it is awkward
>> when only Org mode is doing it, but not other packages.
>> See https://list.orgmode.org/orgmode/874kw7o4ry.fsf <at> gnu.org/
>
> That part is up to you.

Sure, but if you think that such an alias would be helpful, it would be
better to do it for all externally maintained packages, not just Emacs.
Should I start a new thread and include TRAMP/CC mode/etc maintainers?

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Message #46 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 28 Jun 2025 22:04:52 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: mail <at> antr.me, rms <at> gnu.org, 78823 <at> debbugs.gnu.org
> Date: Sat, 28 Jun 2025 15:31:16 +0000
> 
> >> We had a similar discussion in the past about making report-org-bug an
> >> alias to org-submit-bug-report, and did not do it because it is awkward
> >> when only Org mode is doing it, but not other packages.
> >> See https://list.orgmode.org/orgmode/874kw7o4ry.fsf <at> gnu.org/
> >
> > That part is up to you.
> 
> Sure, but if you think that such an alias would be helpful, it would be
> better to do it for all externally maintained packages, not just Emacs.
> Should I start a new thread and include TRAMP/CC mode/etc maintainers?

Yes, please.

Message #49 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Antero Mejr <mail <at> antr.me>
Cc: 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 05 Jul 2025 10:41:21 +0300

> From: Antero Mejr <mail <at> antr.me>
> Cc: rms <at> gnu.org,  78823 <at> debbugs.gnu.org
> Date: Mon, 23 Jun 2025 22:02:16 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> >
> > I'd prefer the report-emacs-bug command itself look at the text of the
> > report and intuit that it might be about Org, then ask the user.  This
> > is more easily discoverable, and probably also more reliable.
> 
> I think adding a command "report-org-bug" that is an alias for
> "org-submit-bug-report" may also be helpful. I looked for that before
> submitting but couldn't find the right command name. I can submit a
> patch to Org to add it if you want.

This is up to Ihor.

> I also attached a patch with a regex to report-emacs-bug-hook to check
> for Org stuff.

Thanks, now installed on the master branch.

Message #52 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sat, 12 Jul 2025 17:47:12 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> >> We had a similar discussion in the past about making report-org-bug an
>> >> alias to org-submit-bug-report, and did not do it because it is awkward
>> >> when only Org mode is doing it, but not other packages.
>> >> See https://list.orgmode.org/orgmode/874kw7o4ry.fsf <at> gnu.org/
>> >
>> > That part is up to you.
>> 
>> Sure, but if you think that such an alias would be helpful, it would be
>> better to do it for all externally maintained packages, not just Emacs.
>> Should I start a new thread and include TRAMP/CC mode/etc maintainers?
>
> Yes, please.

I am looking into this again, and I stumbled upon `package-report-bug'.
I am wondering if it can be used as a centralized command to submit bug
reports + provide an API for package to plug into.
This kind of idea sounds better than creating aliases outside the
package namespace.


-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Message #55 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>,
 Philip Kaludercic <philipk <at> posteo.net>,
 Michael Albinus <michael.albinus <at> gmx.de>
Cc: mail <at> antr.me, 78823 <at> debbugs.gnu.org, rms <at> gnu.org
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sun, 13 Jul 2025 07:47:40 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: mail <at> antr.me, rms <at> gnu.org, 78823 <at> debbugs.gnu.org
> Date: Sat, 12 Jul 2025 17:47:12 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> >> We had a similar discussion in the past about making report-org-bug an
> >> >> alias to org-submit-bug-report, and did not do it because it is awkward
> >> >> when only Org mode is doing it, but not other packages.
> >> >> See https://list.orgmode.org/orgmode/874kw7o4ry.fsf <at> gnu.org/
> >> >
> >> > That part is up to you.
> >> 
> >> Sure, but if you think that such an alias would be helpful, it would be
> >> better to do it for all externally maintained packages, not just Emacs.
> >> Should I start a new thread and include TRAMP/CC mode/etc maintainers?
> >
> > Yes, please.
> 
> I am looking into this again, and I stumbled upon `package-report-bug'.
> I am wondering if it can be used as a centralized command to submit bug
> reports + provide an API for package to plug into.
> This kind of idea sounds better than creating aliases outside the
> package namespace.

I don't mind, but let's hear from the other interested parties.

Message #58 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Ihor Radchenko <yantar92 <at> posteo.net>, rms <at> gnu.org, mail <at> antr.me,
 Philip Kaludercic <philipk <at> posteo.net>, 78823 <at> debbugs.gnu.org,
 Michael Albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sun, 13 Jul 2025 10:39:36 -0400

>> I am looking into this again, and I stumbled upon `package-report-bug'.
>> I am wondering if it can be used as a centralized command to submit bug
>> reports + provide an API for package to plug into.
>> This kind of idea sounds better than creating aliases outside the
>> package namespace.

+1


        Stefan

Message #61 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: yantar92 <at> posteo.net, rms <at> gnu.org, mail <at> antr.me, philipk <at> posteo.net,
 78823 <at> debbugs.gnu.org, michael.albinus <at> gmx.de
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sun, 13 Jul 2025 18:28:33 +0300

> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
> Cc: Ihor Radchenko <yantar92 <at> posteo.net>,  Philip Kaludercic
>  <philipk <at> posteo.net>,  Michael Albinus <michael.albinus <at> gmx.de>,
>   mail <at> antr.me,  rms <at> gnu.org,  78823 <at> debbugs.gnu.org
> Date: Sun, 13 Jul 2025 10:39:36 -0400
> 
> >> I am looking into this again, and I stumbled upon `package-report-bug'.
> >> I am wondering if it can be used as a centralized command to submit bug
> >> reports + provide an API for package to plug into.
> >> This kind of idea sounds better than creating aliases outside the
> >> package namespace.
> 
> +1

FWIW, I don't think a hook is a proper solution here.  Hooks are local
to buffers and set up by major modes (otherwise a package-specific
hook makes no sense), but no one said that a user will want to invoke
the bug-reporting command from a buffer under that package's mode.
And then there are packages that provide only minor modes if at all,
and packages that provide a very long list of modes, etc.

So on balance, I'd go with a command that asks the user about what
package he/she wants to submit a bug report.  If we can intelligently
guess the package, we can offer that as the default.  More automation
should only be considered after we have enough experience.

Message #64 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Philip Kaludercic <philipk <at> posteo.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: yantar92 <at> posteo.net, rms <at> gnu.org, mail <at> antr.me, 78823 <at> debbugs.gnu.org,
 michael.albinus <at> gmx.de, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sun, 13 Jul 2025 19:08:18 +0000

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Stefan Monnier <monnier <at> iro.umontreal.ca>
>> Cc: Ihor Radchenko <yantar92 <at> posteo.net>,  Philip Kaludercic
>>  <philipk <at> posteo.net>,  Michael Albinus <michael.albinus <at> gmx.de>,
>>   mail <at> antr.me,  rms <at> gnu.org,  78823 <at> debbugs.gnu.org
>> Date: Sun, 13 Jul 2025 10:39:36 -0400
>> 
>> >> I am looking into this again, and I stumbled upon `package-report-bug'.
>> >> I am wondering if it can be used as a centralized command to submit bug
>> >> reports + provide an API for package to plug into.
>> >> This kind of idea sounds better than creating aliases outside the
>> >> package namespace.

In my eyes, that was the intention of that command.  By API you probably
mean that packages can support collecting and aggravating custom data?

My instinctual solution would be to use the package symbol and add a
property that may contain a function we can invoke (probably without any
arguments) to generate a part of the bug report.  The simplest solution
would just be to pass that function to the post-hooks argument of
`reporter-submit-bug-report'.

>> +1
>
> FWIW, I don't think a hook is a proper solution here.  Hooks are local
> to buffers and set up by major modes (otherwise a package-specific
> hook makes no sense), but no one said that a user will want to invoke
> the bug-reporting command from a buffer under that package's mode.
> And then there are packages that provide only minor modes if at all,
> and packages that provide a very long list of modes, etc.
>
> So on balance, I'd go with a command that asks the user about what
> package he/she wants to submit a bug report.  If we can intelligently
> guess the package, we can offer that as the default.  More automation
> should only be considered after we have enough experience.

Sounds good.

Message #67 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: yantar92 <at> posteo.net, rms <at> gnu.org, mail <at> antr.me, 78823 <at> debbugs.gnu.org,
 michael.albinus <at> gmx.de, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Sun, 13 Jul 2025 18:52:27 -0400

>> FWIW, I don't think a hook is a proper solution here.  Hooks are local
>> to buffers and set up by major modes (otherwise a package-specific
>> hook makes no sense), but no one said that a user will want to invoke
>> the bug-reporting command from a buffer under that package's mode.
>> And then there are packages that provide only minor modes if at all,
>> and packages that provide a very long list of modes, etc.
>>
>> So on balance, I'd go with a command that asks the user about what
>> package he/she wants to submit a bug report.  If we can intelligently
>> guess the package, we can offer that as the default.  More automation
>> should only be considered after we have enough experience.
>
> Sounds good.

+1


        Stefan

Message #70 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: philipk <at> posteo.net, rms <at> gnu.org, mail <at> antr.me, yantar92 <at> posteo.net,
 78823 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Mon, 14 Jul 2025 08:39:53 +0200

Eli Zaretskii <eliz <at> gnu.org> writes:

Hi Eli,

> So on balance, I'd go with a command that asks the user about what
> package he/she wants to submit a bug report.  If we can intelligently
> guess the package, we can offer that as the default.  More automation
> should only be considered after we have enough experience.

FTR: Tramp doesn't see too many bug reports. And there are not so many
people working on them. So I don't care too much whatever mechanism is
decided; I'll follow.

Best regards, Michael.

Message #73 received at 78823 <at> debbugs.gnu.org (full text, mbox):

From: Ihor Radchenko <yantar92 <at> posteo.net>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: rms <at> gnu.org, mail <at> antr.me, 78823 <at> debbugs.gnu.org, michael.albinus <at> gmx.de,
 Stefan Monnier <monnier <at> iro.umontreal.ca>, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#78823: [BUG] 31.0.50; org-babel-execute-src-block: Wrong
 type argument: integer-or-marker-p, nil
Date: Mon, 14 Jul 2025 19:24:17 +0000

Philip Kaludercic <philipk <at> posteo.net> writes:

>>> >> I am looking into this again, and I stumbled upon `package-report-bug'.
>>> >> I am wondering if it can be used as a centralized command to submit bug
>>> >> reports + provide an API for package to plug into.
>>> >> This kind of idea sounds better than creating aliases outside the
>>> >> package namespace.
>
> In my eyes, that was the intention of that command.  By API you probably
> mean that packages can support collecting and aggravating custom data?

Not only. `org-submit-bug-report' also asks additional queries to user,
and changes the text in the email template.

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.