[O] Klipse change removed line breaks in html export of code blocks
Hi, I noticed that at some point source code blocks lost the line breaks in the html export. Closer investigation revealed that the reason was the change ( https://www.mail-archive.com/emacs-orgmode@gnu.org/msg113099.html) which started using html tags instead of so setting (setq org-html-keep-old-src t) fixed the issue for me. My question is why is this behavior not the default? It looks like Klipse supports very few languages (of which I use none) but the change affects every single language supported by Org mode. Thanks, Alex
[O] How can I trigger org-redisplay-inline-images automatically when '[[..]]' is shown as a link.
#+OPTIONS: latex:t toc:nil H:3 Hi, I usually paste images into emacs buffer. I'd like org mode automatically show those images instead of manually trigger it with org-redisplay-inline-images. regards, Amos
Re: [O] Bug: Please make org-emphasis-regexp-components respect all whitespace [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]
Hello, Reuben Thomas writes: > I currently have in my Emacs init: > > (setq org-emphasis-regexp-components ;; define before loading org > '("[:space:]('\"{" "-[:space:].,:!?;'\")}\\[" "[:space:]\r\n" "." 1)) > > In other words, I added [:space:] to the BORDER pattern too. > > It would seem reasonable to have something like this be the default. In > particular, worg/dev/org-syntax.org already talks about “whitespace”, > not specifically “spaces, tabs etc.”. > > But, I wonder, is it a problem that [:space:] contains vertical > whitespace characters too? (I left “\r\n” in the BORDER pattern as a > reminder that they are there on purpose, whereas PRE and POST previously > contained only space and tab, i.e. horizontal whitespace.) On the other > hand, since PRE and POST are anchored to the start and end of a line, > and the number of newlines is by default limited to 1, perhaps it’s not > a problem? I don't think it is a problem with vertical spaces. IIRC, that change was request by someone else some months ago, but the request probably felt through the cracks. Anyway, I made that change to master branch. We'll see what happens. Thank you. -- Nicolas Goaziou
Re: [O] [RFC] New "kbd" macro?
Hello, Rasmus writes: > I am not sure where it makes sense to print in "plain" text as opposed to > code or verbatim by default. Anyway, I think it makes sense to add > specific export mechanisms for several backends, which might make it > possible to remove that argument. Plain text allows user to define its own environment. I'm not against forcing ~...~ on keybindings when no specific syntax is required. > - HTML, MD :: as Kaushal points out, please use .. This is (almost) already the case. > > - LaTeX :: it’s complicated, as e.g. keys needs to be translated in a specific > way, depending on the package that is being used, e.g. "libertinekey", > "menukeys" or whatnot. We should not add new default packages IMO. We > could always support a couple of different packages, but default to > something like "\fbox{\ttfamily %s}". Adding support for other packages > reduces to mapping specific sequences, like "SPC" to something like > "\LKeySpace". > > - ODT :: it should be possible to use something like Biolinium or > Libertinus keyboard fonts if we just have an alist mapping sequences > like CTRL to the right unicode symbol (E.g. U+E173 here), but the place > in the font would probably depend on the font. So unless there’s a > standard it would be risky. Since fonts aren’t (typically?) embedded in > ODT it might be better to add a new odt style that prints the words in > the mono font inside a box, i.e. the equivalent of "\fbox{\ttfamily %s}". For those back-ends, I think, e.g., ~M-~ is a good default. It is very close to what Texinfo can produce. The "fbox" thing seems a bit heavy. WDYT? Regards, -- Nicolas Goaziou
Re: [O] library of babel ingest interferes with noweb
Hello, ed...@openmail.cc writes: > Hello, > > It seems that when I have two blocks of code with noweb, and then I do > a babel ingest, I don't get my original result (see attached file). > [...] > * This works > #+NAME: test1 > #+BEGIN_SRC bash > a=2 > #+END_SRC > > #+NAME: test2 > #+BEGIN_SRC bash :noweb yes > <> > #+END_SRC > > #+BEGIN_SRC bash :noweb yes > <> > #+END_SRC > > shows in the org-edit-special window > #+BEGIN_EXAMPLE > a=2 > #+END_EXAMPLE I don't get this. I have #+BEGIN_EXAMPLE <> #+END_EXAMPLE However, it seems wrong to have #+BEGIN_EXAMPLE a=2 #+END_EXAMPLE because you no longer know what part you are editing. Regards, -- Nicolas Goaziou
[O] Bug: Please make org-emphasis-regexp-components respect all whitespace [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]
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 http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. I tried writing: ~get~/~set~ methods Fair enough, this renders as all verbatim, according to the parsing rules. So, I tried adding zero-width spaces around the slash. Same result. org-emphasis-regexp-components indeed does not consider all whitespace, just some. So, I tried adding [:space:] to the PRE and POST patterns, and now it works. I currently have in my Emacs init: (setq org-emphasis-regexp-components ;; define before loading org '("[:space:]('\"{" "-[:space:].,:!?;'\")}\\[" "[:space:]\r\n" "." 1)) In other words, I added [:space:] to the BORDER pattern too. It would seem reasonable to have something like this be the default. In particular, worg/dev/org-syntax.org already talks about “whitespace”, not specifically “spaces, tabs etc.”. But, I wonder, is it a problem that [:space:] contains vertical whitespace characters too? (I left “\r\n” in the BORDER pattern as a reminder that they are there on purpose, whereas PRE and POST previously contained only space and tab, i.e. horizontal whitespace.) On the other hand, since PRE and POST are anchored to the start and end of a line, and the number of newlines is by default limited to 1, perhaps it’s not a problem? In any case, it would be nice to have a natural solution to the problem of emphasis delimiters in this sort of situation. Simply taking advantage of Unicode characters such as zero-width space seems simpler than complicating the parser (and it’s also increasingly obvious to users as they get used to the power of Unicode, and is the sort of trick that works with lots of different systems, not just Org). Emacs : GNU Emacs 25.2.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2017-09-12 Package: Org mode version 9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/) -- https://rrt.sc3d.org/
Re: [O] reformatting a quite large table
A huge table reformatting speed-up was achieved and committed on January 9th. The mail thread was "spee-up table refresh". On 14/09/2017 10:48, Luca Ferrari wrote: Hi all, I'm just curios, having a an org table that is 140 MB of text in size (it's a dump of an sql table if that matters), how can I speed up reformatting the table? Something I can do in background or limiting rows to what is shown to me in the buffer will suffice. Is that possible? Thanks, Luca
[O] library of babel ingest interferes with noweb
Hello, It seems that when I have two blocks of code with noweb, and then I do a babel ingest, I don't get my original result (see attached file). Is there a reason for this? Is this a bug? Thanks. - ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands! $24.95 ONETIME Lifetime accounts with Privacy Features! 15GB disk! No bandwidth quotas! Commercial and Bulk Mail Options! ;; This buffer is for notes you don't want to save, and for Lisp evaluation. ;; If you want to create a file, visit that file with C-x C-f, ;; then enter the text in that file's own buffer. * This works #+NAME: test1 #+BEGIN_SRC bash a=2 #+END_SRC #+NAME: test2 #+BEGIN_SRC bash :noweb yes <> #+END_SRC #+BEGIN_SRC bash :noweb yes <> #+END_SRC shows in the org-edit-special window #+BEGIN_EXAMPLE a=2 #+END_EXAMPLE * This does not work After loading this block, #+BEGIN_SRC emacs-lisp :exports none :results none (org-babel-lob-ingest "t.org") #+END_SRC #+BEGIN_SRC bash :noweb yes <> #+END_SRC shows in the org-edit-special window #+BEGIN_EXAMPLE <> #+END_EXAMPLE * What I expect After ingesting the file, I should still get =a=2= in the org-edit-special
Re: [O] Bug: Confusing example in "Advanced configuration" [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]
Hi Reuben, Thank you for your bug report. Reuben Thomas writes: > 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 > > http://orgmode.org/manual/Feedback.html#Feedback > > Your bug report will be posted to the Org mailing list. > > > The page http://orgmode.org/manual/Advanced-configuration.html has the > following example: > > Here is an example filter that replaces non-breaking spaces ~ in the Org > buffer with _ for the LaTeX back-end. > > (defun my-latex-filter-nobreaks (text backend info) >"Ensure \"_\" are properly handled in LaTeX export." >(when (org-export-derived-backend-p backend 'latex) > (replace-regexp-in-string "_" "~" text))) > > (add-to-list 'org-export-filter-plain-text-functions > 'my-latex-filter-nobreaks) > > This is confusing in several ways. First, the replacement is made the > other way around (that is, _ is replaced by ~). Secondly, “_” does not > denote a non-breaking space in org-mode, as far as I can see. Does the > text mean “LaTeX non-breaking spaces”? Finally, underscore has a > particular meaning in Org, namely, subscript. It should be a non-breaking space " " which is displayed like a ruby-colored "_" in (my) Emacs. It was changed to a normal underscore upstream via commit 961cf22823d55. It was then rewritten in 6ce21caac53d376758 to the current form. It is a useful example so we could undo the first part of 6ce21caac53. Alternatively, perhaps discussing a space unicode character becomes a bit too awkward to follow in anything but Emacs so we could also replace something else in the example. Rasmus -- Nothing's wrong with an email that ends in a minor key
Re: [O] Bug: Setting org-export-use-babel to nil causes exporting to ignore :exports header
Thanks, Nicolas. It looks like the default behavior changed at some point but it could have been some while ago... Sent from my iPad > On Sep 14, 2017, at 5:58 AM, Nicolas Goaziou wrote: > > Hello, > > Richard Stanton writes: > >> Emacs : GNU Emacs 25.2.1 (x86_64-apple-darwin16.7.0, Carbon Version 157 >> AppKit 1504.83) >> of 2017-08-28 >> Package: Org mode version 9.1 (9.1-20-ga4f139-elpa @ >> /Users/stanton/.emacs.d/elpa/org-20170911/) >> >> I typically set org-export-use-babel to nil, to prevent all the code >> cells being executed on export. However, if this variable is set, org >> export both code and results for each cell, regardless of the setting of >> the :exports header option. Withoput this variable being set, exporting >> correctly obeys the :exports directives in the cell headers. > > Here is `org-export-use-babel' docstring: > > Switch controlling code evaluation and header processing during > export. When set to nil no code will be evaluated as part of the > export process and no header arguments will be obeyed. Users who wish > to avoid evaluating code on export should use the header argument > ‘:eval never-export’. > > So you need to use ":eval never-export", not that variable. > > Regards, > > -- > Nicolas Goaziou
[O] Bug: Confusing example in "Advanced configuration" [9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/)]
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 http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. The page http://orgmode.org/manual/Advanced-configuration.html has the following example: Here is an example filter that replaces non-breaking spaces ~ in the Org buffer with _ for the LaTeX back-end. (defun my-latex-filter-nobreaks (text backend info) "Ensure \"_\" are properly handled in LaTeX export." (when (org-export-derived-backend-p backend 'latex) (replace-regexp-in-string "_" "~" text))) (add-to-list 'org-export-filter-plain-text-functions 'my-latex-filter-nobreaks) This is confusing in several ways. First, the replacement is made the other way around (that is, _ is replaced by ~). Secondly, “_” does not denote a non-breaking space in org-mode, as far as I can see. Does the text mean “LaTeX non-breaking spaces”? Finally, underscore has a particular meaning in Org, namely, subscript. Is this an example that used to make sense but doesn’t any longer? Emacs : GNU Emacs 25.2.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.18.9) of 2017-09-12 Package: Org mode version 9.0.10 (9.0.10-5-g1654a5-elpa @ /home/rrt/.emacs.d/elpa/org-20170904/) -- https://rrt.sc3d.org/
Re: [O] Using orgtbl-mode with markdown: hfmt1
> The point of orgtbl-mode is to edit Org tables, not Markdown tables, > which have a different syntax. The point of a screwdriver is to drive screws. I happened to notice that this particular screwdriver makes a good chisel, too. Unfortunately, the way things are at the moment means that using this screwdriver as a chisel damages it (by making me change the native org-mode table syntax, too). The analogy stops here: Different from an actual screwdriver, it is possible to add a switch to org-table-align that allows to use it for either purpose, without damage. (To me, it seems that the existence of an orgtbl-mode minor mode points out that this kind of use outside org-mode is not an entirely foreign concept here.) > The usual workflow is to edit the Org mode tables and "send" it to > another location within the same buffer, applying some pre-defined > transformation. See (info "(org) Radio tables") for more information. These workflows would make more sense if I’m working alone on the document. Well, then I could write them entirely in org-mode in the first place. The point of writing them in markdown is to be able to collaborate with people who don’t use org-mode (or Emacs, or even a plaintext editor at all!). > Another option is to add an advice on `org-table-align'. See > `add-advice’. That doesn’t work too well as the tiny change is in the middle of that function; advice-add could be used to manipulate its input or its output, but not that small difference in table syntax between org-mode and github markdown (the main culprit here — many other markdown implementations don’t have a problem with org-mode table syntax). Grüße, Carsten
Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?
Eric S Fraga writes: > On Thursday, 14 Sep 2017 at 09:56, Loris Bennett wrote: >> Hi, >> >> I have the following in my .emacs: >> >> (require 'gnus-icalendar) >> (gnus-icalendar-setup) >> (gnus-icalendar-org-setup) > > I have one setting alongside these: > > (setq gnus-icalendar-org-capture-file "...path to my diary.org") > > I wonder whether gnus needs this to be defined for it to show all the > buttons? Maybe check the value of this before and after? > > I always see all the buttons (I think). Rereading this, I decided to move the settings out from the Customize block to before call to gnus-icalendar-org-setup: (require 'gnus-icalendar) (setq gnus-icalendar-org-capture-file "~/git/org.git/gtd.org") (setq gnus-icalendar-org-capture-headline (quote ("Exchange"))) (gnus-icalendar-setup) (gnus-icalendar-org-setup) Now I get all the buttons first time round and didn't have to resort to a flaky hack, so thanks, Eric. But should this kind of ordering dependency happen? Or should my Customize block just be at the beginning of my .emacs rather than at the end? Cheers, Loris -- This signature is currently under construction.
Re: [O] Using orgtbl-mode with markdown: hfmt1
Hello, Carsten Bormann writes: > As is, orgtbl-mode is a great addition to markdown-mode. > > There is one snag: > > The markdown table syntax isn’t fully standardized. > A number of implementations react unfavorable to the + characters that > orgtbl-mode uses as a column/row separator in the line separating the > header from the body of the table; they prefer the | character here as > well. > > So I apply this little patch in org-table-align each time I install a new > version of org-mode: > > org-table.el > 874c158 > < (hfmt1 "-%s-+")) > --- >> (hfmt1 "-%s-|")) ; HACK: + ➔ | > > Works perfectly. But it would be nice not to have to apply this patch each > time I update. > > Would it be possible to make hfmt1 configurable? > (Preferably, using a buffer-local variable so I don’t have to break > tables in org-mode proper?) The point of orgtbl-mode is to edit Org tables, not Markdown tables, which have a different syntax. The usual workflow is to edit the Org mode tables and "send" it to another location within the same buffer, applying some pre-defined transformation. See (info "(org) Radio tables") for more information. Another option is to add an advice on `org-table-align'. See `add-advice'. Regards, -- Nicolas Goaziou
Re: [O] [RFC] New "kbd" macro?
> Copying Oleh, as I believe he would also have some interest in this. Thanks for the info. I still prefer to denote keys as ~C-x C-f~, and code as =forward-char=: 1. It looks good in text. 2. It looks good on Github/Gitlab render. 3. It still exports as C-x C-f for HTML, and @kbd{C-x C-f} for Texinfo. See for example: https://github.com/abo-abo/swiper/blob/master/doc/ivy.org#writing-this-manual regards, Oleh
Re: [O] Library of Babel
Hello, Charles Millar writes: > First. Should Sections 14.5 and 14.6 of the manual need revision since > lob has been moved to Worg? Or at least a reference to Worg site be > inserted. Indeed. Would you want to provide a patch for that? > Second: Am I correct that ob-lob.el has not been removed so that I can > ingest my own source code blocks into, e.g. some/directory/cm-lob? That's correct. Regards, -- Nicolas Goaziou
Re: [O] [bug, fr] cannot doneify repeaters that have clock entries when org-log-repeat is nil
Hello, Samuel Wales writes: > * x > recent maint > > (setq org-log-repeat nil) > > doneify this in emacs 24.4.1 -Q. > *** TODO test if presence of clock entry fails to advance repeater > when doneified :goto: > SCHEDULED: <2017-09-07 Thu 12:00 .+1d> > :PROPERTIES: > :LAST_REPEAT: [2017-09-12 Tue 15:27] > :END: > :LOGBOOK: > - State "DONE" from "NEXTREPEAT" [2017-09-12 Tue 12:05] > - State "DONE" from "NEXTREPEAT" [2017-09-12 Tue 11:52] > CLOCK: [2017-09-11 Mon 12:34]--[2017-09-11 Mon 12:48] => 0:14 > :END: Fixed. Thank you. > *** also feature request 'never What would mean this value? Regards, -- Nicolas Goaziou
Re: [O] org-babel-script-escape problem
Hello, Lawrence Bottorff writes: > In a fresh org file I try this: > > #+begin_src scheme :session mainsession > (define (mysquare x) > (* x x)) > #+end_src > > and get this: > > executing Scheme code block... > => # > : ‘org-babel-script-escape’ expects a string It now prints: : # Please let me know if that fixes the problem on your side. Thank you. Regards, -- Nicolas Goaziou
Re: [O] Bug: Setting org-export-use-babel to nil causes exporting to ignore :exports header
Hello, Richard Stanton writes: > Emacs : GNU Emacs 25.2.1 (x86_64-apple-darwin16.7.0, Carbon Version 157 > AppKit 1504.83) > of 2017-08-28 > Package: Org mode version 9.1 (9.1-20-ga4f139-elpa @ > /Users/stanton/.emacs.d/elpa/org-20170911/) > > I typically set org-export-use-babel to nil, to prevent all the code > cells being executed on export. However, if this variable is set, org > export both code and results for each cell, regardless of the setting of > the :exports header option. Withoput this variable being set, exporting > correctly obeys the :exports directives in the cell headers. Here is `org-export-use-babel' docstring: Switch controlling code evaluation and header processing during export. When set to nil no code will be evaluated as part of the export process and no header arguments will be obeyed. Users who wish to avoid evaluating code on export should use the header argument ‘:eval never-export’. So you need to use ":eval never-export", not that variable. Regards, -- Nicolas Goaziou
Re: [O] Bug in ox.el
Qiang Fang writes: > The issue happen with list-table in the unofficial ox-odt, list-table enables > list in tables, it's very cool. AFAIK, list-tables are supported in bundled "ox-odt.el" too. So, again, could you provide an ECM? > And I think there is no one more capable and willing to fix issues related to > ox-odt than the original author. You may well be right for the first part of the sentence, but I can tell I'm at least as willing as anyone to fix the issues related to ox-odt. > It will benifit more people if we can include it in the official > org-mode. Alas, this is not possible, and it doesn't depend on us. Regards,
Re: [O] Strange latex symbol behavior on html export
Hello, Nick Dokos writes: > I looked at the diff between html files produced with and without the $\big/$ > addition. > The one without does not include any of the mathjax configuration code at > all. Is that > code included conditionally perhaps when a latex construct is seen? Maybe the > latex construct > in the caption does not trigger the inclusion? Good catch! Fixed. Thank you. Regards, -- Nicolas Goaziou
Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?
Eric S Fraga writes: > On Thursday, 14 Sep 2017 at 11:11, Loris Bennett wrote: > > [...] > >> It obviously does work, in principle, for me too, as the re-eval shows. >> However, it seems as if something later in my .emacs undoes some aspect >> of whatever it is that the gnus-icalendar-org-setup does. > > Well, may be time to bisect etc...? Yes, you're probably right. However, the problem is not very serious (thankfully I don't get invited to many meetings) and my .emacs with its big Customize block doesn't really lend itself to bisection. So for the moment I might just chicken out and set up a keybinding for gnus-icalendar-org-setup. Cheers, Loris -- This signature is currently under construction.
[O] org-babel-script-escape problem
In a fresh org file I try this: #+begin_src scheme :session mainsession (define (mysquare x) (* x x)) #+end_src and get this: executing Scheme code block... => # : ‘org-babel-script-escape’ expects a string I'm using latest elpa everything (orgmode, geiser) with Racket v6.10.1 as of this morning. Just started happening. . . . LB
[O] error with tramp & publishing
Hello, when I try to publish a single file from a project, I get the following error: : Publishing file /home/ucecesf/hg/homepages/index.org using ‘org-html-publish-to-html’ : make-directory: Creating directory: Permission denied, /ssh:MYSERVER:MYDIRECTORY I can directly visit that directory from Emacs and, once having done so, a subsequent (and more) publishing request works. It's as if org expects that connection to the server to have been made already. Any suggestions as to what I may be doing wrong? Thanks, eric -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-57-gc6e563 signature.asc Description: PGP signature
Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?
On Thursday, 14 Sep 2017 at 11:11, Loris Bennett wrote: [...] > It obviously does work, in principle, for me too, as the re-eval shows. > However, it seems as if something later in my .emacs undoes some aspect > of whatever it is that the gnus-icalendar-org-setup does. Well, may be time to bisect etc...? -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-57-gc6e563 signature.asc Description: PGP signature
Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?
Eric S Fraga writes: > On Thursday, 14 Sep 2017 at 09:56, Loris Bennett wrote: >> Hi, >> >> I have the following in my .emacs: >> >> (require 'gnus-icalendar) >> (gnus-icalendar-setup) >> (gnus-icalendar-org-setup) > > I have one setting alongside these: > > (setq gnus-icalendar-org-capture-file "...path to my diary.org") > > I wonder whether gnus needs this to be defined for it to show all the > buttons? Maybe check the value of this before and after? I also have the following: '(gnus-icalendar-org-capture-file "~/git/org.git/gtd.org") '(gnus-icalendar-org-capture-headline (quote ("Exchange"))) (but this was in the buried in the 'Customize' bit of my .emacs, so I forgot about it). > I always see all the buttons (I think). It obviously does work, in principle, for me too, as the re-eval shows. However, it seems as if something later in my .emacs undoes some aspect of whatever it is that the gnus-icalendar-org-setup does. Cheers, Loris -- This signature is currently under construction.
[O] reformatting a quite large table
Hi all, I'm just curios, having a an org table that is 140 MB of text in size (it's a dump of an sql table if that matters), how can I speed up reformatting the table? Something I can do in background or limiting rows to what is shown to me in the buffer will suffice. Is that possible? Thanks, Luca
Re: [O] Is it possible to repeat tasks only a certain amount of times?
On Thursday, 14 Sep 2017 at 11:05, Göktuğ Kayaalp wrote: > It seems to me that my only option ATM is what Eric S Fraga pointed, > but that's rather tedious as things like lessons change during the > year (different classrooms, time changes). Funnily enough, it is for changes in lecture halls etc. that I use the clone subtree approach: that way each entry can have different information. I specify the defaults in the first entry; clone the number I want and then modify any special cases as required (e.g. different lecture hall, delete the reading week slot, ...). But, of course, YMMV! -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-57-gc6e563 signature.asc Description: PGP signature
Re: [O] Table format error
On Thursday, 14 Sep 2017 at 08:39, Cecil Westerhof wrote: [...] > But when I then format the table, > the last heading goes from right aligned to left aligned: > |---+---+---| > | 1 | Text | 2 | > |---+---+---| > | Some text | Some more | And even more | > | Some text | Some more | And even more | > |---+---+---| > > What is happening here? > > I am using: Org-mode version 8.2.10. Org tries to guess what the alignment should be: columns with numbers will be right-aligned; with text they will be left-aligned. Maybe org did a count and decided this was a text column after all once you added the new row. You can specify the actual alignment by using in a separate row, e.g.: |---+---+---| | 1 | Text | 2 | | | || |---+---+---| | Some text | Some more | And even more | | Some text | Some more | And even more | |---+---+---| HTH, eric -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-57-gc6e563 signature.asc Description: PGP signature
Re: [O] (gnus-icalendar-org-setup) not evaluated in .emacs?
On Thursday, 14 Sep 2017 at 09:56, Loris Bennett wrote: > Hi, > > I have the following in my .emacs: > > (require 'gnus-icalendar) > (gnus-icalendar-setup) > (gnus-icalendar-org-setup) I have one setting alongside these: (setq gnus-icalendar-org-capture-file "...path to my diary.org") I wonder whether gnus needs this to be defined for it to show all the buttons? Maybe check the value of this before and after? I always see all the buttons (I think). -- : Eric S Fraga via Emacs 26.0.50, Org release_9.1-57-gc6e563 signature.asc Description: PGP signature
Re: [O] Strange latex symbol behavior on html export
Nick Dokos writes: > Lawrence Bottorff writes: > >> ... I use >> >> # this makes MathJax work >> #+OPTIONS: tex:t >> >> I just now found this caption weirdness because I started a new .org >> file with no latex symbol markup besides in the caption. Quite >> bizarre that when my file sees other latex symbols, the caption >> symbols then render correctly. >> > >> On Wed, Sep 13, 2017 at 6:55 PM, Nick Dokos wrote: >> >> Nicolas Goaziou writes: >> >> > Hello, >> > >> > Lawrence Bottorff writes: >> > >> >> Consider this markup: >> >> >> >> >> >> * MATHEMATICS AUXILIARY >> >> >> >> ** deriving sines and cosines >> >> >> >> #+caption: Right triangle with two $\pi\big/4$ angles. >> >> [[file:images/45-45-triangle.png]] >> >> >> >> $\big/$ >> >> >> >> >> >> If I remove the second $\big/$, the first latex, $\pi\big/4$, in the >> >> caption will not properly render on export to html. Include it and >> both >> >> render just fine. Without the second, the first looks like this: >> >> >> >> Figure 1: Right triangle with two \(\pi\big/4\) angles. >> >> >> >> Is this a bug? >> > >> > If you use >> > >> > #+options: tex:dvipng >> > >> > the symbol in the caption is correctly rendered. It may be a bug in >> Mathjax. >> > >> >> I looked at the diff between html files produced with and without the >> $\big/$ addition. >> The one without does not include any of the mathjax configuration code >> at all. Is that >> code included conditionally perhaps when a latex construct is seen? >> Maybe the latex construct >> in the caption does not trigger the inclusion? >> >> -- >> Nick >> > > org-html--build-mathjax-config includes the mathjax code only if > > (and (memq (plist-get info :with-latex) '(mathjax t)) >(org-element-map (plist-get info :parse-tree) >'(latex-fragment latex-environment) 'identity info t)) > > is true. I guess we didn’t want to load extra JS unless it’s needed. > So if there is latex markup in the file (other than the caption) the > org-element-map > call finds it and returns non-nil, but it apparently does not look inside the > caption. When org-element looks at something like "#+caption: a $b$" it sees a keyword. I don’t know if it’s possible to check explicitly whether it contains maths. Alternatively, we could check if :with-latex is explicitly set in the buffer (like in ox-koma-letter) and then load it regardless. Rasmus -- This is the kind of tedious nonsense up with which I will not put
Re: [O] [RFC] New "kbd" macro?
Hi Nicolas, Thanks for looking into this. Nicolas Goaziou writes: > I would like to submit a new minor macro for integration within Org: the > "kbd" macro. > > The "kbd" macro focuses on normalizing keybinding during export. For > example, during Texinfo export, {{{kbd(v SPC)}}} becomes > > @kbd{v @key{SPC}} > > whereas in another back-end, it becomes > > v > > More specifically: > > Within {{{kbd(...)}}}, the following case-sensitive keys are wrapped > within angle brackets: SPC, RET, LFD, TAB, BS, ESC, DELETE, SHIFT, > CTRL, META, up, down, left, right. (I wish there was a more light-weight syntax for macros... Maybe we should provide something similar to C-c C-l for inserting them...) > With an optional argument, it can wrap the key-binding within verbatim > or code markup: > > {{{kbd(v SPC,code)}}} => ~v ~ > > {{{kbd(v SPC,verbatim)}}} => =v = > > Other markup is not implemented because, in that case, you can wrap > appropriate characters around the macro. I am not sure where it makes sense to print in "plain" text as opposed to code or verbatim by default. Anyway, I think it makes sense to add specific export mechanisms for several backends, which might make it possible to remove that argument. - HTML, MD :: as Kaushal points out, please use .. - LaTeX :: it’s complicated, as e.g. keys needs to be translated in a specific way, depending on the package that is being used, e.g. "libertinekey", "menukeys" or whatnot. We should not add new default packages IMO. We could always support a couple of different packages, but default to something like "\fbox{\ttfamily %s}". Adding support for other packages reduces to mapping specific sequences, like "SPC" to something like "\LKeySpace". - ODT :: it should be possible to use something like Biolinium or Libertinus keyboard fonts if we just have an alist mapping sequences like CTRL to the right unicode symbol (E.g. U+E173 here), but the place in the font would probably depend on the font. So unless there’s a standard it would be risky. Since fonts aren’t (typically?) embedded in ODT it might be better to add a new odt style that prints the words in the mono font inside a box, i.e. the equivalent of "\fbox{\ttfamily %s}". - Texinfo :: already supported. Rasmus -- Bang bang
Re: [O] Is it possible to repeat tasks only a certain amount of times?
On 2017-09-13 20:58 +03, Jorge Morais Neto wrote: > How about a diary-style sexp entry, with org-class? That is, something > like ~<%%(org-class 2017 7 31 2018 3 23 1)>~. That example would appear > on the agenda on every Monday between 2017-07-31 and 2018-03-23. Thanks a lot, this in combination with the hours of the event in the title (I didn't know that this worked) works nicely in Org Agenda, but unfortunately such entries do not get exported to ICS, which is important for me. It seems to me that my only option ATM is what Eric S Fraga pointed, but that's rather tedious as things like lessons change during the year (different classrooms, time changes). Cheers, -g. > Regards -- İ. Göktuğ Kayaalp http://www.gkayaalp.com/index.html s...@gkayaalp.com🎀PGP = 024C 30DD 597D 142B 49AC Plaintext please! {UTF8} Fingerprint 40EB 465C D949 B101 2427
[O] (gnus-icalendar-org-setup) not evaluated in .emacs?
Hi, I have the following in my .emacs: (require 'gnus-icalendar) (gnus-icalendar-setup) (gnus-icalendar-org-setup) When I get an invitation to a meeting, Gnus displays the email with the following buttons: [ Accept ][ Tentative ][ Decline ] However, if leave the email, re-evaluate the line (gnus-icalendar-org-setup) in my .emacs and then revisit the email invitation, I get the following buttons [ Accept ][ Tentative ][ Decline ] [ Show Agenda ][ Export to Org ] Obviously I would like Gnus to display all the buttons first time around. Does anyone have any idea what might be going on? I'm using the following: - Gnus v5.13 - GNU Emacs 25.1.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.12) of 2017-04-23, modified by Debian - Org mode version 9.1 (9.1-20-ga4f139-elpaplus @ /home/loris/.emacs.d/elpa/org-plus-contrib-20170911/) As I'm not sure this is an Org or a Gnus thing, I'm cross-posting. Cheers, Loris -- This signature is currently under construction.