Re: babel output seems to drop anything before % (in session)
Kaushal Modi writes: > Hello all, > > I am following up on this issue with ob-shell and sessions. > > I had posted the recipe to reproduce the issue few months back, and it > still applies; ref: > https://list.orgmode.org/CAFyQvY2AeToQc2G=e+de4votetfbkvisenipypw1y-feu1o...@mail.gmail.com/ FYI, I attempted to fix this several times, but the underlying code is not trivial. Hopefully someone™ more familiar with comint can make a working patch. If you encounter this issue frequently, you may be the most motivated person here to spend time studying the code. Ideas how to approach the problem would be appreciated. Best, Ihor
Re: [BUG] Org V 9.5 error when ~/.cache doesn't exist
Ihor Radchenko writes: > After second thought, I am not sure anymore if using XDG is a good idea. > Emacs itself only recently started supporting XDG and the support is > somewhat limited. Similar to the described case with non-existing .cache > directory, Emacs ignores non-existing .config/emacs folder for init.el. > Emacs never creates .config directory. Some more data: xdg.el is not (yet?) supported by Aquamacs [1]. While we do not officially support Aquamacs, it is probably best to avoid xdg.el if we can. Also, there is an ongoing discussion at emacs-devel about Emacs support for XDG specs and similar [2]. If the new user-directory library gets merged to Emacs, it may be the way to go (with proper back-compatibility aliases). [1] https://list.orgmode.org/cafqubhf+wpuneeapkcg94wjhfcrxvsf+j-7ut3b_romfkqc...@mail.gmail.com/T/#m99c63439a745c07fd7c30cde0b49b3d5bd1757f0 [2] https://lists.gnu.org/archive/html/emacs-devel/2021-11/msg00469.html Best, Ihor
Re: upgrade to 9.5 failed:
Pete Siemsen writes: > Thank you. That changed things, so I guess it's getting better. Now when I > do a TAB, I get > > Cannot open load file. No such file or directory, xdg Note that Org does not officially support Aquamacs. For now, I fixed this particular issue because it also affects Emacs 25. However, this part of Org is currently a subject of change. Feel free to join the discussion at https://list.orgmode.org/87ee7yaksm.fsf@localhost/ to make your voice (as Aquamacs user) heard. Best, Ihor
Re: babel output seems to drop anything before % (in session)
Hello all, I am following up on this issue with ob-shell and sessions. I had posted the recipe to reproduce the issue few months back, and it still applies; ref: https://list.orgmode.org/CAFyQvY2AeToQc2G=e+de4votetfbkvisenipypw1y-feu1o...@mail.gmail.com/ Thanks! -- Kaushal Modi
Merging ox-texinfo+ into ox-texinfo
Hello, In the olden days before Org's own manual was written using an org-mode file, I started doing just that for Magit. Because ox-texinfo.el wasn't quite there yet I wrote an extension, ox-texinfo+.el, to fill in the gaps. Since then I have written seven more manuals that use my extension. I recently talked to Bastien about this and he encouraged to bring up the possibility of merging ox-texinfo+.el into ox-texinfo.el. ox-texinfo+ (https://github.com/tarsius/ox-texinfo-plus) has several features but the one I would like to talk about now is the following. [If you want to look at the other features now, then please use the "next" branch as I am in the process of trimming some of them down or even removing them completely. The main feature is the same in the "master" and "next" branches.] Create `@deffn` and similar definition items by writing list items in Org that look similar to what they will look like in Info. To enable this, add: #+TEXINFO_DEFFN: t to your Org file. After doing that, you can create definition items like so: - Command: magit-section-show Show the body of the current section. - Function: magit-git-exit-code &rest args - Macro: magit-insert-section &rest args - Variable: magit-display-buffer-noselect - User Option: magit-display-buffer-function - Key: q, magit-mode-bury-buffer I propose that we add this as an optional feature to ox-texinfo.el itself. IMO the biggest advantage of this style is that it leads to a prettier org file, which is suitable for direct consumption by end-users. It is also easier to write in this style by package authors who might not want to fully familiarize themselves with all the peculiarities of writing an org file intended for export to texinfo. It is possible to mix the two styles; you can use the ox-texinfo+.el style for most or all definitions but use the additional flexibility of ox-texinfo.el, when that is needed. What do you think? Might this be something that could be merged? The reason I am bringing this up now after years of maintaining this as an extension is that I would like to finally stop checking in both the *.org and *.texi files into git. [Non]GNU Elpa already supports this and I plan to implement it for Melpa as well. It would be much nicer if the only additional requirement for an *elpa was to have a recent enough Org version installed, instead of that and also ox-texinfo+.el. Cheers, Jonas
Re: [PATCH] Bug: Unintended column added to table [9.4.6 (9.4.6-gab9f2a @ /home/user/.emacs.d/elpa/org-9.4.6/)]
I've had this happen in an earlier version of org and found if I get on the last record in a table at the beginning of the line and tab the number of columns in the table plus 1 I get a blank new record added to the table and the extra unintended column does not appear. In the earlier version of orgmode I use if I go down to the last record then tab once to get into the first column of the table and then start entering data and finish the data entry in that record or add more records, then the extra unintended column does appear. I only mention this behavior as confirmation of this behavior. On Tue, 9 Nov 2021, Spectira Chiando wrote: > Ihor, > > Patch is working great, have been using it heavily for the past month. Thanks > very much! > > Spectria > > Sent: Saturday, October 02, 2021 at 1:54 AM > From: "Ihor Radchenko" > To: spect...@mail.com > Cc: emacs-orgmode@gnu.org > Subject: [PATCH] Bug: Unintended column added to table [9.4.6 (9.4.6-gab9f2a > @ /home/user/.emacs.d/elpa/org-9.4.6/)] > Ihor Radchenko writes: > > > spect...@mail.com writes: > > > >> In a preexisting org table, hitting can add a new, unintended column > >> > >> Bug: After the 2nd iteration, org adds a unintended new column. Further > >> iteration adds more columns. > > > > Confirmed > > > > The problem appears somewhere inside org-table-justify-field-maybe > > And here is the fix. > > I am not familiar with org-table codebase, so feedback would be > appreciated. > > Best, > Ihor > > >
Re: upgrade to 9.5 failed:
Thank you. That changed things, so I guess it's getting better. Now when I do a TAB, I get Cannot open load file. No such file or directory, xdg -- Pete On Mon, Nov 8, 2021 at 5:43 PM Ihor Radchenko wrote: > Pete Siemsen writes: > > > I'm running Aquamacs 3.6 on a Mac running macOS 11.6. I've been happily > > running org-mode 9.1.14 for years. Today, for no particular reason, I > tried > > to upgrade to org-mode 9.5. I was able to upgrade, and org-version > changed > > to "9.5", but when I tried some simple commands in an org file, like > "TAB" > > to do an "org-cycle", I got > > > > cannot open load file, no such file or directory, backtrace > > Fixed now. > > Bes, > Ihor >
A function to include a PDF with LaTeX commands for specific pages
Hi,
Sometimes I need to include a pre-compiled PDF in my main document. Of
course, this can be done simply with the `pdfpages' LaTeX package. If we
want to insert a complete PDF, it would be enough to add:
#+latex:
\includepdf[pages=-,noautoscale=true,page-command={\thispagestyle(plain}]{file.pdf}
But the 'problem' arises when we want to add multiple page-commands such
as \label{...} and \index{...} to specific pages of the PDF. It would
have to be done explicitly by putting multiple lines of \includepdf{etc},
which can be a bit monotonous. To simplify that scenario it occurred to
me to write this function:
(my-org/insert-pdfpages PDF &optional PAGE-COMMANDS-ALL PAGE-COMMANDS-PER-PAGE)
PAGE-COMMANDS-ALL is the command that should be applied to all pages;
PAGE-COMMANDS-PER-PAGE must be a list, with the page number and the
commands for that page (a possible improvement could be to allow adding
page ranges...). For example:
#+LaTeX_Header: \usepackage{pdfpages}
#+begin_src emacs-lisp :exports results :results latex
(my-org/insert-pdfpages "file.pdf" "\\thispagestyle{plain}" '((2
"\\label{label1}")
(3
"\\label{label2}\\index{index1}")
(7
"\\label{label3}\\index{index2}")
(12
"\\index{index3}")))
#+end_src
Only tested on GNU/Linux; mupdf-tools is required, to be able to get the
number of pages of the PDF. And the function:
#+begin_src emacs-lisp
(defun my-org/insert-pdfpages (pdf &optional page-commands-all
page-commands-per-page)
(let ((pdfpages-result))
(setq pdfpages-result
(with-temp-buffer
(let ((counter 0)
(pags-pdf (shell-command-to-string
(format "mutool info %s | grep '^Pages' | cut -d
' ' -f 2"
pdf
(dotimes (num (string-to-number pags-pdf))
(insert (concat
"\n\\includepdf[pages={"
(number-to-string
(setf counter (+ counter 1)))
"},"
"noautoscale=true,"
(if page-commands-all
(format "pagecommand={%s}" page-commands-all) "")
"]{"
pdf
"}"
(if page-commands-per-page
(mapc (lambda (x)
(let ((pag (number-to-string (car x)))
(str (cadr x)))
(save-excursion
(goto-char (point-min))
(while (re-search-forward (concat "pages={" pag
"}") nil t)
(if (re-search-forward "\\(pagecommand={\\)")
(replace-match (concat "\\1" "\\" str ","))
(re-search-forward "\\(\\[\\)" nil t)
(replace-match (concat "\\1" "pagecommand={"
"\\" str "},")))
page-commands-per-page)
"")
(buffer-string)))
pdfpages-result))
#+end_src
Best regards,
Juan Manuel
Re: [PATCH] Bug: Unintended column added to table [9.4.6 (9.4.6-gab9f2a @ /home/user/.emacs.d/elpa/org-9.4.6/)]
Ihor, Patch is working great, have been using it heavily for the past month. Thanks very much! Spectria Sent: Saturday, October 02, 2021 at 1:54 AM From: "Ihor Radchenko" To: spect...@mail.com Cc: emacs-orgmode@gnu.org Subject: [PATCH] Bug: Unintended column added to table [9.4.6 (9.4.6-gab9f2a @ /home/user/.emacs.d/elpa/org-9.4.6/)] Ihor Radchenko writes: > spect...@mail.com writes: > >> In a preexisting org table, hitting can add a new, unintended column >> >> Bug: After the 2nd iteration, org adds a unintended new column. Further iteration adds more columns. > > Confirmed > > The problem appears somewhere inside org-table-justify-field-maybe And here is the fix. I am not familiar with org-table codebase, so feedback would be appreciated. Best, Ihor
Re: epresent font increase ?
No idea but you could always just create the face yourself and see what happens? This is *emacs* after all... -- : Eric S Fraga via Emacs 28.0.60, Org release_9.5-192-gd4e192 : Latest paper written in org: https://arxiv.org/abs/2106.05096
Re: epresent font increase ?
Jean-Christophe Helary writes: > I'm trying to increase the overall font for an epresent slide show > that I'm presenting in 37 minutes and I keep getting this > "face-attribute: Invalid face: epresent-content-face" message... > > My screen is a 15" and running that full screen makes the contents difficult > to read. > > Any solution ? Switch to the newer epresent at https://github.com/eschulte/epresent. Shooting into the dark, -- Marco
Re: epresent font increase ?
> On Nov 9, 2021, at 21:11, Marco Wahl wrote: > > Jean-Christophe Helary writes: > >> I'm trying to increase the overall font for an epresent slide show >> that I'm presenting in 37 minutes and I keep getting this >> "face-attribute: Invalid face: epresent-content-face" message... >> >> My screen is a 15" and running that full screen makes the contents difficult >> to read. >> >> Any solution ? > > Switch to the newer epresent at https://github.com/eschulte/epresent. Maybe there was an issue between me and the keyboard because it works now. -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/
Re: epresent font increase ?
> On Nov 9, 2021, at 21:10, Eric S Fraga wrote: > > No idea but you could always just create the face yourself and see what > happens? This is *emacs* after all... Indeed :-) > -- > : Eric S Fraga via Emacs 28.0.60, Org release_9.5-192-gd4e192 > : Latest paper written in org: https://arxiv.org/abs/2106.05096 -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/
Re: epresent font increase ?
> On Nov 9, 2021, at 21:16, Ihor Radchenko wrote: > > Jean-Christophe Helary writes: > >> I'm trying to increase the overall font for an epresent slide show that I'm >> presenting in 37 minutes and I keep getting this "face-attribute: Invalid >> face: epresent-content-face" message... >> >> My screen is a 15" and running that full screen makes the contents difficult >> to read. >> >> Any solution ? > > Your problem is related to third-party package (epresent). You may > better ask the package author. You're right. -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/
Re: epresent font increase ?
Jean-Christophe Helary writes: > I'm trying to increase the overall font for an epresent slide show that I'm > presenting in 37 minutes and I keep getting this "face-attribute: Invalid > face: epresent-content-face" message... > > My screen is a 15" and running that full screen makes the contents difficult > to read. > > Any solution ? Your problem is related to third-party package (epresent). You may better ask the package author. If things worked for you in the past and you updated the epresent package... I recommend avoiding updates right before you need to present something. Also, Emacs has built-in function text-scale-adjust to scale buffer font size. Best, Ihor
epresent font increase ?
I'm trying to increase the overall font for an epresent slide show that I'm presenting in 37 minutes and I keep getting this "face-attribute: Invalid face: epresent-content-face" message... My screen is a 15" and running that full screen makes the contents difficult to read. Any solution ? -- Jean-Christophe Helary @brandelune https://mac4translators.blogspot.com https://sr.ht/~brandelune/omegat-as-a-book/
Re: Incorrect link is stored (org-elements?)
Max Nikulin writes: > `org-store-link' under some conditions may pick a link to wrong heading. > Emacs-26.3, Org main~1. I can reproduce, though not exactly following your steps. Can you try the attached patch? Best, Ihor >From 6465741dff757af23b10d1f0a412eb41d05f4c75 Mon Sep 17 00:00:00 2001 Message-Id: <6465741dff757af23b10d1f0a412eb41d05f4c75.1636458311.git.yanta...@gmail.com> From: Ihor Radchenko Date: Tue, 9 Nov 2021 19:42:14 +0800 Subject: [PATCH] org-element-at-point: Fix breakage when called at the end of section * lisp/org-element.el (org-element-at-point): Do no unconditionally return first matching cached element when point is within blank lines after section element and CACHED-ONLY is non-nil. Fixes https://list.orgmode.org/smbl59$qjm$1...@ciao.gmane.io/T/#u --- lisp/org-element.el | 3 --- 1 file changed, 3 deletions(-) diff --git a/lisp/org-element.el b/lisp/org-element.el index 9ea13db9c..ad5c2bbd0 100644 --- a/lisp/org-element.el +++ b/lisp/org-element.el @@ -7510,9 +7510,6 @@ (defun org-element-at-point (&optional pom cached-only) (and (org-element-property :contents-begin element) (>= pom (org-element-property :begin element)) (< pom (org-element-property :contents-begin element))) - (and (org-element-property :contents-end element) -(< pom (org-element-property :end element)) -(>= pom (org-element-property :contents-end element))) (and (not (org-element-property :contents-end element)) (>= pom (org-element-property :begin element)) (< pom (org-element-property :end element))) -- 2.32.0
