Re: [O] Inline source does not evaluate when inserted insie a minipage environment
On 09/22/17 17:22, Nicolas Goaziou wrote: Hello, Charles Millarwrites: This problem may not be limited to just \begin{minipage}, etc., but to other latex commands which may precede text which contains inline source code The following inline code evaluates as expected to 1 This is some text. Some more test with an inline src_sh[:results raw]{echo 1} a bit more However, when I C-c C-c the same code when inside a minipage, I get the message " 'C-c C-c' can do nothing useful here" \begin{minipage}[t]{4.0in} This is some text. Some more test with an inline src_sh[:results raw]{echo 1} a bit more \end{minipage} This is not a bug. \begin{minipage} ... \end{minipage} defines a LaTeX environment, i.e., pure LaTeX code, and Org doesn't look into this. This is like $...$ or \(...\), but as block element. Thank you.
Re: [O] Issue with org-babel-clojure evaluation returning all forms
It is quite likely an issue due to changes in cider. Cider from melpa gets a lot of updates and is a fast moving target. IMO cider is not the best back end to use with org. You are probably better off using inf-clojure. The cider back end has a lot of complexity to support repl driven development which really complicates matters when your just wanting to get clojure blocks evaluated and results back. The inf-clojure back end is much simpler and undergoes less change, so is more stable. Personally, I'm not using this functionality in org. I found the complexities of trying to get clojure blocks to work in this way was way too high once you tried to do anything more than very simple statement evaluation. I now use a more traditional literate programming approach where I maintain the code in org files, but tangle the whole file to get a clj/cljs file, which is what is loaded into the repl. regards, Tim Matthew Stegall writes: > I'm trying to set up babel for use with Clojure according to > http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-clojure.html#org85bc1ec > and > I can evaluate code but when I evaluate a block with multiple forms in it > it outputs all of the form like so > > #+begin_src clojure :results value > (def small-map {:a 2 :b 4 :c 8}) > (:b small-map) > #+end_src > > #+RESULTS: > : #'user/small-map4 > > I'm using cider for the back end as given in the tutorial and I'm not > getting any errors just unwanted input. > > I don't think anything in my emacs config should effect this but I can post > if needed. > > I'm also using org-plus-contrib as I the default org installation doesn't > allow me to evaluate clojure blocks, saying it can't find slime. > > I've used the debugging tools to go through cb-clojure.el and found that > the nrepl-sync-request:eval result dictionary list the output of all of the > form in value without any separator so it may be something with cider, I'm > running the latest version from melpa-stable. > > If any other information is needed, let me know and thanks in advance for > any help. -- Tim Cross
Re: [O] Bug: org-emphasis-alist not fully applied [9.1.1 (9.1.1-1-g80cbf9-elpa @ x:/folder/user/.emacs.d/elpa/org-20170918/)]
Hello, Jens Langewrites: > "If they don't want items added to org-emphasis-alist they shouldn't use > the repeat customization type which allows insertion and deletion. > Furthermore, they should add a note about this restriction in the doc > string of org-emphasis-alist. Maybe, you can give a follow-up in the > bug-report about that." Indeed, the customize type needs to be fixed. Patch welcome! > So I did what he requested. He also provided me with a working solution. > Even with that said I might ask if you could consider supporting adding new > emphasis definitions in the future? I'm not even sure about what you are talking about. Allowing to extend `org-emphasis-alist' with any marker means there is not anymore a single Org format. Any one can define its own with fancy markers. This is not portable.Besides, having syntax you cannot control is asking for trouble. I'm totally against this idea. Org already provides 6 emphasis markers, which is enough in my book. On the other hand, you may be only interested in marking some text with a special face in a buffer. Both Org and Emacs provide ways to do that without messing with Org syntax. As pointed out in the thread, `org-font-lock-set-keywords-hook' is one of them. Regards, -- Nicolas Goaziou
Re: [O] Inline source does not evaluate when inserted insie a minipage environment
Hello, Charles Millarwrites: > This problem may not be limited to just \begin{minipage}, etc., but to > other latex commands which may precede text which contains inline > source code > > The following inline code evaluates as expected to 1 > > This is some text. > Some more test with an inline src_sh[:results raw]{echo 1} > a bit more > > However, when I C-c C-c the same code when inside a minipage, I get > the message " 'C-c C-c' can do nothing useful here" > \begin{minipage}[t]{4.0in} This is some text. > Some more test with an inline src_sh[:results raw]{echo 1} > a bit more > \end{minipage} This is not a bug. \begin{minipage} ... \end{minipage} defines a LaTeX environment, i.e., pure LaTeX code, and Org doesn't look into this. This is like $...$ or \(...\), but as block element. Regards, -- Nicolas Goaziou
Re: [O] width/height/alignement of images in tables
Date: Fri, 22 Sep 2017 09:56:35 +0200 From: C?dric ODYTo: emacs-orgmode@gnu.org Subject: [O] width/height/alignement of images in tables Would there be a way to add width/height/alignment parameters for images that are included in a table, say | [[./a.png]] | [[./b.png]] | by for instance adding the parameters inside the brackets [[./a.png,width,height,halign,valign]]? thanks, Hope this helps: https://github.com/linktohack/ox-latex-subfigure - 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!
[O] Inline source does not evaluate when inserted insie a minipage environment
Hi, This problem may not be limited to just \begin{minipage}, etc., but to other latex commands which may precede text which contains inline source code The following inline code evaluates as expected to 1 This is some text. Some more test with an inline src_sh[:results raw]{echo 1} a bit more However, when I C-c C-c the same code when inside a minipage, I get the message " 'C-c C-c' can do nothing useful here" \begin{minipage}[t]{4.0in} This is some text. Some more test with an inline src_sh[:results raw]{echo 1} a bit more \end{minipage} Org mode version 9.1.1 (release_9.1.1-62-g6e7d15.dirty @ /usr/local/share/emacs/site-lisp/org-mode/lisp/) GNU Emacs 25.1.50.2 (x86_64-unknown-linux-gnu, GTK+ Version 3.14.5) of 2016-07-21 I admit that I did only a cursory search in the list, so if the issue has been addressed before this, please point me in right direction. Charlie Millar
Re: [O] Add ability to force-enable TOC
Kaushal Modiwrites: > On Wed, Sep 20, 2017, 6:25 AM Nicolas Goaziou > wrote: > > I didn't say it was an unusual case. I said it didn't cover all > the use-cases. Maybe you are really needing a subset of the > initial feature. > > Understood. > > IOW, do mixed numbered/unnumbered headings make sense in TOC? > > Correct. That does not make sense to me. That is not my use case. I support the use case of unnumbered table of contents. In addition (although this is probably too much of a corner case to support officially in Org Mode), it is common in the U.S. to use a mix of numbered and unnumbered headings in books. One accomplishes this in LaTeX with the following: --8<---cut here---start->8--- \tableofcontents \chapter*{Introduction} \addcontentsline{toc}{chapter}{Introduction} \chapter{A Chapter} \chapter{Another Chapter} \chapter*{Conclusion} \addcontentsline{toc}{chapter}{Introduction} --8<---cut here---end--->8--- The resulting Table of Contents looks like this... Introduction3 1 A Chapter 5 2 Another Chapter 7 Conclusion 9 Best, Matt
[O] Issue with org-babel-clojure evaluation returning all forms
I'm trying to set up babel for use with Clojure according to http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-clojure.html#org85bc1ec and I can evaluate code but when I evaluate a block with multiple forms in it it outputs all of the form like so #+begin_src clojure :results value (def small-map {:a 2 :b 4 :c 8}) (:b small-map) #+end_src #+RESULTS: : #'user/small-map4 I'm using cider for the back end as given in the tutorial and I'm not getting any errors just unwanted input. I don't think anything in my emacs config should effect this but I can post if needed. I'm also using org-plus-contrib as I the default org installation doesn't allow me to evaluate clojure blocks, saying it can't find slime. I've used the debugging tools to go through cb-clojure.el and found that the nrepl-sync-request:eval result dictionary list the output of all of the form in value without any separator so it may be something with cider, I'm running the latest version from melpa-stable. If any other information is needed, let me know and thanks in advance for any help.
[O] [PATCH] ox-publish.el: Fix regexp `match' to be non-nil
Hi there, recursive publishing fails with base-extension any because a nil regexp is passed. The attached patch fixes this. Best wishes Jens P.S. I did the necessary paperwork (copyright assignment) for Emacs. >From 6584a78c350016e39c199bb61d203bc12c0c4c53 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jens=20Lechtenb=C3=B6rger?=Date: Fri, 22 Sep 2017 11:30:13 +0200 Subject: [PATCH] ox-publish.el: Fix regexp `match' to be non-nil * lisp/ox-publish.el (org-publish-get-base-files): Make sure `match' is a string (not nil) before calling `directory-files-recursively'. --- lisp/ox-publish.el | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/lisp/ox-publish.el b/lisp/ox-publish.el index 753176b..b592bc9 100644 --- a/lisp/ox-publish.el +++ b/lisp/ox-publish.el @@ -435,8 +435,9 @@ This splices all the components into the list." (let* ((base-dir (file-name-as-directory (org-publish-property :base-directory project))) (extension (or (org-publish-property :base-extension project) "org")) - (match (and (not (eq extension 'any)) - (concat "^[^\\.].*\\.\\(" extension "\\)$"))) + (match (or (and (not (eq extension 'any)) + (concat "^[^\\.].*\\.\\(" extension "\\)$")) + "")) (base-files (cl-remove-if #'file-directory-p (if (org-publish-property :recursive project) -- 2.1.4
Re: [O] setting local variables
Nicolas Goaziouwrites: > Hello, > > Carsten Dominik writes: > >> yes, I am aware that LaTeX does use unnumbered for this, but this is >> backend specific implementation, and not an argument about the logic of >> this approach. > > Fair enough. I reverted the commit. > > I think a :NOTOC: property to ignore headlines from TOC is an acceptable > solution, even though it add yet another property. > > I also suggest to classify LaTeX issue as "wontfix". IMO, in ox-latex, "num" should only affect secnumdepth. I don’t think the current behavior is very good. Having numbered and unnumbered in the TOC can be archived using e.g. KOMA-Script (there’s also a sty on github breaking out the relevant part of of KOMA-Script) and adding a new class to org-latex-classes. -- Hvor meget poesi tror De kommer ud af et glas isvand?
[O] width/height/alignement of images in tables
Hello, Would there be a way to add width/height/alignment parameters for images that are included in a table, say | [[./a.png]] | [[./b.png]] | by for instance adding the parameters inside the brackets [[./a.png,width,height,halign,valign]]? From what I have seen, the alignment should however concern the table data in which the image is embedded, for html export. thanks,
Re: [O] setting local variables
Hi Nicolas, thanks! Carsten On Thu, Sep 21, 2017 at 9:21 PM, Nicolas Goaziouwrote: > Hello, > > Carsten Dominik writes: > > > yes, I am aware that LaTeX does use unnumbered for this, but this is > > backend specific implementation, and not an argument about the logic of > > this approach. > > Fair enough. I reverted the commit. > > I think a :NOTOC: property to ignore headlines from TOC is an acceptable > solution, even though it add yet another property. > > I also suggest to classify LaTeX issue as "wontfix". > > Any objection? > > Regards, > > -- > Nicolas Goaziou >