Re: [O] editing orgmode code blocks always indents content..anyway to stop this?
On Tue, Jan 31, 2017 at 9:53 AM, Nicolas Goaziouwrote: > org-edit-src-content-indentation > thx Nicolas! i have this set in my config to '0' see here #+BEGIN_SRC emacs-lisp :results none ;; don't indent source code org-edit-src-content-indentation 0 ;; don't adapt indentation org-adapt-indentation nil ;; preserve the indentation inside of source blocks org-src-preserve-indentation t #+END_SRC shouldn't that not indent?
Re: [O] editing orgmode code blocks always indents content..anyway to stop this?
Hello, Xebar Saramwrites: > i have this weird behaviour where when sometime i edit org code blocks the > text moves (i guess indents) automatically so i start with this > > #+BEGIN_SRC emacs-lisp :results none > (require 'gnus) > (require 'nnir) > #+END_SRC > > > > and the text switches automatically to this: > > #+BEGIN_SRC emacs-lisp :results none > (require 'gnus) > (require 'nnir) > #+END_SRC > > > is there a setting to disable this? See `org-edit-src-content-indentation'. Regards, -- Nicolas Goaziou
[O] editing orgmode code blocks always indents content..anyway to stop this?
Hi all i have this weird behaviour where when sometime i edit org code blocks the text moves (i guess indents) automatically so i start with this #+BEGIN_SRC emacs-lisp :results none (require 'gnus) (require 'nnir) #+END_SRC and the text switches automatically to this: #+BEGIN_SRC emacs-lisp :results none (require 'gnus) (require 'nnir) #+END_SRC is there a setting to disable this? best Z
[O] [PATCH] ox-latex.el: Wrap 'minted' src blocks in a 'listing', environment
Hi everyone, Included is a patch to make the 'minted' source code syntax highlighting package behave the same as the 'listings' source code syntax package when exporting an org-mode document to LaTeX. Previously, 'minted' would only get exported to a floating environment if '#+ATTR_LATEX: :float multicolumn' was provided, whereas the org-mode documentation implies that it should be floated if any caption is provided. Regards, Lixin Chin * lisp/ox-latex.el (org-latex-src-block): Make source highlighting using the 'minted' syntax highlighting package behave the same as using the 'listings' syntax highlighting package. The source block should be floating if a caption is provided, or if ':float t' is provided in an '#+ATTR_LATEX:' block. Previously, the source block would only be floating if ':float multicolumn' was provided. This now matches the org-mode documentation for source blocks. --- lisp/ox-latex.el | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el index d05991233..3cea81650 100644 --- a/lisp/ox-latex.el +++ b/lisp/ox-latex.el @@ -1301,7 +1301,7 @@ For non-floats, see `org-latex--wrap-label'." (and (eq type 'src-block) (not (plist-get attr :float)) (memq (plist-get info :latex-listings) - '(nil minted) + '(nil) (short (org-export-get-caption element t)) (caption-from-attr-latex (plist-get attr :caption))) (cond @@ -2880,13 +2880,19 @@ contextual information." (float-env (cond ((string= "multicolumn" float) - (format "\\begin{listing*}\n%s%%s\n%s\\end{listing*}" + (format "\\begin{listing*}[%s]\n%s%%s\n%s\\end{listing*}" + (plist-get info :latex-default-figure-position) (if caption-above-p caption-str "") (if caption-above-p "" caption-str))) (caption - (concat (if caption-above-p caption-str "") - "%s" - (if caption-above-p "" (concat "\n" caption-str + (format "\\begin{listing}[%s]\n%s%%s\n%s\\end{listing}" + (plist-get info :latex-default-figure-position) + (if caption-above-p caption-str "") + (if caption-above-p "" caption-str))) + ((string= "t" float) + (concat (format "\\begin{listing}[%s]\n" + (plist-get info :latex-default-figure-position)) + "%s\n\\end{listing}")) (t "%s"))) (options (plist-get info :latex-minted-options)) (body -- 2.11.0 From 4daf10b3f5283e3e992fc9e11ff76b6b33c488b6 Mon Sep 17 00:00:00 2001 From: Lixin ChinDate: Tue, 31 Jan 2017 14:15:40 +0800 Subject: [PATCH] ox-latex.el: Wrap 'minted' src blocks in a 'listing' environment * lisp/ox-latex.el (org-latex-src-block): Make source highlighting using the 'minted' syntax highlighting package behave the same as using the 'listings' syntax highlighting package. The source block should be floating if a caption is provided, or if ':float t' is provided in an '#+ATTR_LATEX:' block. Previously, the source block would only be floating if ':float multicolumn' was provided. This now matches the org-mode documentation for source blocks. --- lisp/ox-latex.el | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/lisp/ox-latex.el b/lisp/ox-latex.el index d05991233..3cea81650 100644 --- a/lisp/ox-latex.el +++ b/lisp/ox-latex.el @@ -1301,7 +1301,7 @@ For non-floats, see `org-latex--wrap-label'." (and (eq type 'src-block) (not (plist-get attr :float)) (memq (plist-get info :latex-listings) - '(nil minted) + '(nil) (short (org-export-get-caption element t)) (caption-from-attr-latex (plist-get attr :caption))) (cond @@ -2880,13 +2880,19 @@ contextual information." (float-env (cond ((string= "multicolumn" float) - (format "\\begin{listing*}\n%s%%s\n%s\\end{listing*}" + (format "\\begin{listing*}[%s]\n%s%%s\n%s\\end{listing*}" + (plist-get info :latex-default-figure-position) (if caption-above-p caption-str "") (if caption-above-p "" caption-str))) (caption - (concat (if caption-above-p caption-str "") - "%s" - (if caption-above-p "" (concat "\n" caption-str + (format "\\begin{listing}[%s]\n%s%%s\n%s\\end{listing}" + (plist-get info :latex-default-figure-position) + (if caption-above-p caption-str "") + (if caption-above-p ""
Re: [O] Mobile org
Thanks for letting me know. Note that the latest release is now available: https://itunes.apple.com/us/app/mobileorg/id634225528?mt=8 On Mon, Jan 30, 2017 at 12:59 PM Paul Schlesingerwrote: > There appear to be more than just one of us. > > paul > > On Mon, Jan 30, 2017 at 11:26 AM, Kenneth Jacker > wrote: > > > there are people besides just me that use it :) > > > Yes ... like me! > > *OrgMode* is one of my most used "systems". > > Getting *MobileOrg* updated would be great! > > -Kenneth > > > > > > -- > Paul H. Schlesinger MD, PhD > Washington University School of Medicine >
[O] Update for MobileOrg iOS v1.7 released
Hello fellow Org users, After beta testing several builds, the latest updated version of MobileOrg for iOS has finally been released: https://itunes.apple.com/us/app/mobileorg/id634225528?mt=8 Functionality is essentially the same as the previous version, just refreshed the various SDKs and updated the Dropbox API due to Dropbox deprecating v1. Please report any bugs to Github: https://github.com/MobileOrg/mobileorg/issues Much thanks to Mario Martelli and Boris for their invaluable help getting this release ready. Sean
Re: [O] org-ref glitch with 2 bib files
I can confirm this was happening. I am not sure how it broke, but I have pushed a fix that I think fixes it. Alan L Tyree writes: > G'day, > > I have this near the end of my MS: > > bibliography:refs.bib,tyree.bib > > org-ref finds the entries from refs.bib, but not tyree.bib. > > If I reverse the two bib file, it finds the ones from tyree.bib, but not > from refs.bib. > > Org mode version 9.0.4 (9.0.4-elpaplus @ > /home/alant/.emacs.d/elpa/org-plus-contrib-20170124/) > > GNU Emacs 24.5.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of > 2016-03-20 on trouble, modified by Debian > > System is Linux, Debian Jessie. > > I'm no expert, so I may well be missing something, so let me know if you > need more information or whatever. > > Thanks, > > Alan -- Professor John Kitchin Doherty Hall A207F Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213 412-268-7803 @johnkitchin http://kitchingroup.cheme.cmu.edu
Re: [O] Bug: Emacs hangs with badly defined multi characters key hierarchy in org-capture-templates [9.0 (9.0-dist @ /cygdrive/c/Users/re/.emacs.d/site-lisp/org-9.0/lisp/)]
Hello, Roland Everaertwrites: > When using multicharacters keys, if a key definition entry is missing, > emacs hangs and must be killed. > > Example of an offending org-capture-templates definition: > > (setq org-capture-templates > '(("t" "Todo" entry (file+headline "~/somefile.org" "Tâches") > "* TODO %?\n %i\n" :clock-in t :clock-resume t) > ("l" "Mail" entry (file+datetree "~/somefile.org" "Divers") > "* EMAIL %?\n %i\n" :clock-in t :clock-resume t) > ("fm" "some Menu - level 2") > ("fmm" "template defintion - level 3 " entry (file+olp "~/somefile.org" > "Level 1" "level 2") > "* MEETING %?\n %i\n" :clock-in t :clock-resume t) > ("fmt" "another template definition - level 3" entry (file+olp "~/ > somefile.org" "Level 1" "level 2") > "*** TODO %?\n %i\n" :clock-in t :clock-resume t))) > > The definition of the "f" key is missing. Fixed. Thank you. Regards, -- Nicolas Goaziou
[O] :results raw for html export problem
Here's some Lisp in an org file that I export to html #+begin_src lisp :exports both :results raw (write (setf my-array (make-array '(10 (terpri) ; goo.gl/lCcdDU / Function TERPRI, FRESH-LINE (setf (aref my-array 0) 25) (setf (aref my-array 1) 23) (setf (aref my-array 2) 45) (setf (aref my-array 3) 10) (setf (aref my-array 4) 20) (setf (aref my-array 5) 17) (setf (aref my-array 6) 25) (setf (aref my-array 7) 19) (setf (aref my-array 8) 67) (setf (aref my-array 9) 30) (write my-array) #+end_src #+RESULTS: #(25 23 45 10 20 17 25 19 67 30) . . . but the results look munged after an html export: #(25 23 45 10 20 17 25 19 67 30) #(25 23 45 10 20 17 25 19 67 30) . . . not the mono-space font and the answer is repeated. However, this code behaves well: #+begin_src lisp :exports both (setf x (make-array '(3 3) :initial-contents '((0 1 2 ) (3 4 5) (6 7 8))) ) (write x) #+end_src #+RESULTS: : #2A((0 1 2) (3 4 5) (6 7 8)) and exports well. Please advise. I'm on latest, greatest everything (25.1.1; 9.0.4;U16.10; SBCL1.3.14; fresh quicklisp slime). LB
Re: [O] Sync up the org in emacs master to org maint branch?
John Wiegley writes: >> "DE" == David Engsterwrites: > > DE> This is a misunderstanding. I said I wanted to move support for certain > DE> languages and project types into ELPA, not CEDET core. I'm still of the > DE> opinion that moving it completely to ELPA is a mistake. > > It would only be a mistake if other parts of core need to use it. If only > users make use of it, then having it ELPA will be invisible to them. It is a mistake because you are creating more moving targets and bring them together very late in the release process. This reduces the amount of testing that is done for those packages, so bugs will be noticed later and the quality of the relases suffer. It moves even more work into the RC-phase, which is already crowded and where people who can fix those bugs might not be readily available. It removes those packages from Emacs CI, so that breakages due to changes in core are not immediately noticed, and often times they have to be fixed not by those who created the breakage, but by those who notice them. -David
Re: [O] Mobile org
There appear to be more than just one of us. paul On Mon, Jan 30, 2017 at 11:26 AM, Kenneth Jackerwrote: > > there are people besides just me that use it :) > > > Yes ... like me! > > *OrgMode* is one of my most used "systems". > > Getting *MobileOrg* updated would be great! > > -Kenneth > > > -- Paul H. Schlesinger MD, PhD Washington University School of Medicine
Re: [O] Mobile org
> there are people besides just me that use it :) Yes ... like me! *OrgMode* is one of my most used "systems". Getting *MobileOrg* updated would be great! -Kenneth
Re: [O] Sync up the org in emacs master to org maint branch?
> "DE" == David Engsterwrites: DE> This is a misunderstanding. I said I wanted to move support for certain DE> languages and project types into ELPA, not CEDET core. I'm still of the DE> opinion that moving it completely to ELPA is a mistake. It would only be a mistake if other parts of core need to use it. If only users make use of it, then having it ELPA will be invisible to them. -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
Re: [O] Org-mode: Tagging the CLOCK line
Thanks. I was hoping that collaboration had advanced since the 2010 discussion on this topic. Unfortunately, I don't know enough about elisp to hack something together for org-mode. This combined with GIT would be awesome for a project management tracking tool. Shawn Way, PE -Original Message- From: Emacs-orgmode [mailto:emacs-orgmode-bounces+sway=meco@gnu.org] On Behalf Of Eric S Fraga Sent: Thursday, January 26, 2017 8:49 AM To: emacs-orgmode@gnu.org Subject: Re: [O] Org-mode: Tagging the CLOCK line On Thursday, 26 Jan 2017 at 14:02, Shawn Way wrote: > Is there a modification that can be made to add a tag, such as > someone’s initials, to the CLOCK line? I would like to use this to > separate out time spent by multiple individuals in a clocking table. Not what you want as such but what I have done in the past is create subheadings which I clock into/out of specifically. -- : Eric S Fraga (0xFFFCF67D), Emacs 26.0.50.1, Org release_9.0.3-241-gc3d67b