[O] #+attr_odt: not working
Hello all, I'm on 9.1.14. No matter what I do I can't seem to get anything related to #+attr_odt to work! I've tried custom styles.xml, the default, different block types, etc, etc. All I want is a very simple odt paragraph style with no first-line indent (for paragraphs following block quotes): ``` #+begin_quote To be or not to be #+end_quote #+ATTR_ODT: :style Text_20_Body_20_left That is the question. ``` I've made the style in my odt template. But #+attr_odt has no effect. I've tried other ":style " values as well. Any help would be greatly appreciated!
[O] Org mode fontification broken
Since upgrading from Fedora 27 to Fedora 28, Emacs 26.1-3.fc28.x86_64, links and other fontified text in Org files appear as the underlying plain text. A few of them look correct, and deleting a marker character (e.g. square bracket) and reinserting it makes the link appear correctly for a while. The Messages buffer is full of things like this: Error during redisplay: (jit-lock-function 501) signaled (wrong-type-argument listp org-level-4) Error during redisplay: (jit-lock-function 1001) signaled (wrong-type-argument listp org-level-4) Error during redisplay: (jit-lock-function 1501) signaled (wrong-type-argument listp org-level-3) Error during redisplay: (jit-lock-function 2001) signaled (wrong-type-argument listp org-level-3) Error during redisplay: (jit-lock-function 1152403) signaled (wrong-type-argument listp org-level-2) I've attempted to set jit-lock-mode to nil in .emacs, with no success. This Emacs has a built-in version of Org, 9.1.14, and I've tried 20181125 installed through Melpa. Nothing makes a difference. Any ideas? Peter.
[O] Bug: "file:" protocol link with "#anchor" bad HTML export [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/)]
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. I add into Worg file "worg-faq.org" a hyperlink using the "file:" protocol, linking to a sub-heading in Worg file "worg-git.org". Exact syntax quoted below, from an email thread with Bastien. Expected behavior: I expect the HTML exporter automatically used by Worg to generate an "https:" protocol hyperlink which links to a specific, existing HTML anchor ID in file "worg-git.html". Actual behavior: The exporter generates an "https:" protocol hyperlink that points to a non-existent anchor ID in file "worg-git.html". I have left the mis-generated link in place on Worg for the time being. (My previous push included a correct, explicit "https:" protocol link; I can revert and push again at any time). You can examine it at: https://orgmode.org/worg/org-faq.html#keeping-current-with-Org-mode-development at the bottom of list item 2. See below for the exact syntax of the Org link. Emacs : GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of 2017-09-12 on hullmann, modified by Debian Package: Org mode version 9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/) -- Forwarded message - From: Bastien Date: Mon, 12 Nov 2018 at 06:19 Subject: Re: Worg commit privs To: Philip Hudson Hi Philip, Philip Hudson writes: > Doesn't look right. The generated link points to a non-existent id: > > https://orgmode.org/worg/worg-git.html#org2c2081f > > This is the link in the Org source, created using "C-c l" followed by "C-c > C-l": > > file:worg-git.org::*The%20first%20time%20you%20contribute%20to%20Worg It looks like a bug. The section has a CUSTOM_ID property, and the value of this property is used as the HTML anchor, but the stored link uses another method when exporting to HTML, hence the bug. Could you report it to the mailing list? Don't forget to mention your Org version and a minimal recipe on how to reproduce the bug. It is important enough to block the release of Org 9.2. I won't have time to look at it before nov. 19th, though. I hope Nicolas or someone else can have a look. Thanks! -- Bastien -- Phil Hudson http://hudson-it.ddns.net Pretty Good Privacy (PGP) ID: 0x4E482F85
Re: [O] Sum clocks into a custom property
On 2018-11-12, at 11:35, Leo Alekseyev wrote: > I am using org-invoice.el, which expects either CLOCKSUM or WORK properties > to exist in an item; these properties contain some time duration record in > HH:MM format. > > I can't figure out how to generate those properties from a series of clock > entries with any built-in user-facing functions, so I want to do it > programmatically -- I can get the sum of the clock entries > via (org-clock-sum-current-item), but how do I convert them to HH:MM format > and insert it as a property? For converting to hh:mm format, see the `format-seconds' function (built into Emacs). Hth, -- Marcin Borkowski http://mbork.pl
[O] Sum clocks into a custom property
I am using org-invoice.el, which expects either CLOCKSUM or WORK properties to exist in an item; these properties contain some time duration record in HH:MM format. I can't figure out how to generate those properties from a series of clock entries with any built-in user-facing functions, so I want to do it programmatically -- I can get the sum of the clock entries via (org-clock-sum-current-item), but how do I convert them to HH:MM format and insert it as a property?
[O] Latex export from org-download images with spaces fails
Hello mailing list, when I use org-download to take a screenshot and automatically import the image into my org document it often contains spaces (because the overlying headline contains spaces and the image gets saved in a folder with the same name). org-download seems to use URL encoding when storing the link in the org file so these spaces get converted to "%20". Org-mode seems to be fine with this and calling org-toggle-inline-images the image as shown as expected. However, when exporting to LaTex, the images are not shown in the resulting PDF file (which can recovered by changing the URL encoded spaces to real spaces). I now wonder which module is the problem here: - Should LaTex be able to understand URL encoded paths? - Are URL encoded links normal/encourged in org-mode? - Should org-download use normal spaces instead of URL encoding? I'm happy for any suggestion you have on how to workarround this and on where I should file a bug report. I started at org-download ( https://github.com/abo-abo/org-download/issues/84) Thanks for your help
Re: [O] creating new #+KEYWORD: variables
Hi Nicolas, Thank you for this pointer! I have modified my own leanpub-multifile backend (derived from leanpub) to use this instead of manually extracting the keywords. In case anyone is interested, my code is here: https://github.com/zzamboni/dot-emacs/blob/master/init.org#publishing-to-leanpub Best, --Diego On Sat, Nov 10, 2018 at 8:22 AM Nicolas Goaziou wrote: > Hello, > > Matt Price writes: > > > I am writing this interface to my university's learning management > system: > > > https://github.com/titaniumbones/Org-Marking-Mode/tree/use-structured-course-def > . > > I am only using hte exporting system tangentially and I have not defined > a > > new exporter. However, I would really like to be able to set some > variable > > values in the header section of hte document, e.g.: > > > > #+ORG_LMS_COURSE: becomingmodern > > You can add keywords specific to a given export back-end in its > definition, more precisely in :options-alist value. For example, in > "ox-texinfo", there is > > (org-export-define-backend 'texinfo > '((bold . org-texinfo-bold)) > ... > :options-alist > '((:texinfo-filename "TEXINFO_FILENAME" nil nil t) > ...)) > > which means `texinfo' back-end should recognize the "#+TEXINFO_FILENAME" > keyword, and store its value in the :texinfo-filename property from > "info" paramater, which is passed to each function. > > You can write a derived back-end using this new keyword, along with > a template function that actually uses it. Look at the definition of > `beamer' back-end for an example. > > HTH, > > -- > Nicolas Goaziou > >
