unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Петров Андрей" <an.petrov@pay-lab.ru>
To: 55445@debbugs.gnu.org
Subject: bug#55445: 29.0.50; Org-mode to info export error
Date: Mon, 16 May 2022 08:44:27 +0000	[thread overview]
Message-ID: <c9639e12269b4c8b8c730aadd246b1aa@pay-lab.ru> (raw)

Hello, Team!

Please take a look at the following scenario:

1. Start `emacs -Q`, enable entering debugger on error
2. Create empty "1.org" file
    C-x b 1.org [RET]
    M-x org-mode [RET]
    C-x w 1.org [RET]
3. Export it to info file (directly, not through creating texinfo file)
    C-c C-e i i

Result:

Debugger entered--Lisp error: (wrong-type-argument listp 1000000000)
  seq-subseq((1652689971098490901 . 1000000000) 0 2)
  cl-subseq((1652689971098490901 . 1000000000) 0 2)
  org-file-newer-than-p("/home/andrey/1.info" (1652689970960239177 . 1000000000))
  org-compile-file("1.texi" ("makeinfo --no-split %f") "info" "See \"*Org INFO Texinfo Output*\" for details" #<buffer *Org INFO Texinfo Output*>)
  org-texinfo-compile("1.texi")
  org-export-to-file(texinfo "1.texi" nil nil nil nil nil org-texinfo-compile)
  org-texinfo-export-to-info(nil nil nil nil)
  org-export-dispatch(nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)
  command-execute(org-export-dispatch)

It seems that time format changes are not reflected in exporting code.


Please also try the following:

1. Create org-mode buffer not bound to any file
   C-x b 2.org [RET]
   M-x org-mode [RET]
2. Try exporting it inot info (the same way as above)
   C-c C-e i i

Results:

Debugger entered--Lisp error: (error "File \"/home/andrey/5/bug/4528/1.info\" wasn’t produ...")
  signal(error ("File \"/home/andrey/5/bug/4528/1.info\" wasn’t produ..."))
  error("File \"/home/andrey/5/bug/4528/1.info\" wasn't produ...")
  org-compile-file("~/5/bug/4528/1.texi" ("makeinfo --no-split %f") "info" "See \"*Org INFO Texinfo Output*\" for details" #<buffer *Org INFO Texinfo Output*>)
  org-texinfo-compile("~/5/bug/4528/1.texi")
  org-export-to-file(texinfo "~/5/bug/4528/1.texi" nil nil nil nil nil org-texinfo-compile)
  org-texinfo-export-to-info(nil nil nil nil)
  org-export-dispatch(nil)
  funcall-interactively(org-export-dispatch nil)
  call-interactively(org-export-dispatch nil nil)
  command-execute(org-export-dispatch)

And "*Org INFO Texinfo Output*" buffer contains:

unable to open ~/5/bug/4528/1.texi: No such file or directory







             reply	other threads:[~2022-05-16  8:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16  8:44 Петров Андрей [this message]
2022-05-16 12:30 ` bug#55445: 29.0.50; Org-mode to info export error Lars Ingebrigtsen
2022-05-16 14:41   ` Петров Андрей
2022-05-16 14:57     ` Петров Андрей
2022-05-17 17:37       ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c9639e12269b4c8b8c730aadd246b1aa@pay-lab.ru \
    --to=an.petrov@pay-lab.ru \
    --cc=55445@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).