[O] how to get org-version using emacs batch mode.
How can I get the org-version on my command line? I think using batch mode it is possible. I tried : emacs --batch --eval '(org-version)' but it doesn't work. It gives me blank result. -- Thanks Regards, Supriya Pravin Sawant
Re: [O] Tried to use `org-agenda-top-headline-filter' in agenda block
Hi Brady, Brady Trainor algeb...@uw.edu writes: Org-mode version 8.2.5h (8.2.5h-137-gc7812f-elpa @ /home/iam/.emacs.d/elpa/org-20140421/) I tried to use `org-agenda-top-headline-filter'. There was a bug here, please try again from a fresh pull of the maint or master branch. Thanks for reporting this, -- Bastien
Re: [O] observations on updating to recent org
Hi Greg, Greg Troxel g...@ir.bbn.com writes: I used to get an ID PROPERTIES entries for nodes that were exported to the calendar, which was basically nodes that had an active timestamp. But now I had a huge number of changes, adding ID to every node, even those with no real content and just children. Is this a feature? Indeed. Nicolas, do you remember why we added IDs to all headlines and not just the one that we be exported in the .ics file? -- Bastien
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Hi Aaron, Aaron Ecay aarone...@gmail.com writes: How does this sound as an algorithm: 1. if :file is present, behave exactly as we do now 2. if :file is absent but :file-ext and a #+name is present, generate a :file parameter from :output-dir, the #+name, and :file-ext. I suggest this one: 1. if :file is present, behave exactly as we do now 2. if :file-ext is present: - if #+name is present, generate a :file parameter from :output-dir, #+name and :file-ext - otherwise, generate the :file parameter from :output-dir, the headline or the title or the current file name and :file-ext Just falling back on something sensible when :file is absent and :file-ext is specified. Open questions: 1. should :file-ext without a #+name be a no-op, or an error? See above. 2. should :output-dir apply to the :file case as well? To me yes. In overall I think would be good, but I'd like Eric and other babelist around here to have a look before we commit this. So perhaps another round of patch testing will be good. Thanks! -- Bastien
Re: [O] how to get org-version using emacs batch mode.
Supriya Sawant sp.sawan...@gmail.com writes: emacs --batch --eval '(org-version)' but it doesn't work. It gives me blank result. emacs --batch --eval '(message (org-version))' HTH, -- Bastien
Re: [O] Exporting Code Blocks to PDF
Instead of switching fontsizes regularly, you might want to set the monofont
size or scale:
#+LATEX_HEADER: \setmonofont[Scale=0.8]{Source Code Pro}
Bernhard
John Hendy jw.he...@gmail.com schrieb am Tue, 22. Apr 19:43:
On Tue, Apr 22, 2014 at 6:28 PM, Elasady, Summer s...@stowers.org wrote:
Hello Emacs World-
I’m using LaTex to export documents to PDF, but the code blocks are not
fitting to the page properly and the code is being cutoff. Is there a way to
turn on word-wrapping for export to PDF, or to resize code blocks?
I don't know if there's a way to wrap, but in my one formal
programming class, the convention was only to write 80 characters or
less -- are you exceeding that? If not, and it's just a font size
thing, you can always use LaTeX to reduce the font. I frequently do
this, especially using code in Beamer presentations:
#+latex: \scriptsize
#+begin_src R blah blah
code here
#+end_src
#+latex: \normalsize
This way, the block is downsized, and then resumes to regular font
size for the rest of the document. You can use any size command you
want; I frequently use \footnotesize, \scriptsize, and \tiny. I hardly
notice a difference with \small, though you can try that, too.
Also, does anyone have a good system for dealing with exporting large
tables? Right now I’m just linking to a file, but I’m curious if anyone else
is doing anything clever.
For tables that are /close/ in size already, I do the same thing as
above, at least if we're talking about fitting to width. You can also
flip sideways and extend over multiple pages to handle both wide and
long:
#+latex: \begin{landscape}
#+attr_latex: :environment longtable
| *alpha* | *beta* | *gamma* | *delta* |
|-++-+-|
| 1 | 1 | 1 | 1 |
| 2 | 2 | 2 | 2 |
| 3 | 3 | 3 | 3 |
| 4 | 4 | 4 | 4 |
#+latex: \end{landscape}
You can use them independently, too. Initially I tried the Org syntax
for sidewaystable, but it didn't seem to work with longtable:
- http://orgmode.org/manual/LaTeX-specific-attributes.html
As in, technically it would seem you could do:
#+attr_latex: :environment longtable :float sidewaystable
But perhaps that's more of a LaTex issue:
-
http://tex.stackexchange.com/questions/63585/sidewaystable-together-with-longtable
Anyway, the above works, and that covers any handles I've ever used
(font, rotate, extend over multiple pages). Other than trying to
wordsmith my column names where the title exceeds the contents...
that's all the tricks up my sleeve!
John
Thanks in advance!
Summer
s...@stowers.org
Re: [O] observations on updating to recent org
Hello, Bastien b...@gnu.org writes: Nicolas, do you remember why we added IDs to all headlines and not just the one that we be exported in the .ics file? It is a bit difficult to do otherwise. We don't know beforehand what headlines are going to be exported. We get this information when a headline is encountered during export, which happens in a different buffer, and possibly in a different process. I think it is a minor inconvenience and we can live with it. Regards, -- Nicolas Goaziou
Re: [O] how to get org-version using emacs batch mode.
Is it possible to redirect or get the output of batch mode command in variable. cmd = emacs --batch --eval '(message (org-version))' ouput=cmd print output i.e output contains version no.(output=7.9.3f) On Wed, Apr 23, 2014 at 12:00 PM, Bastien b...@gnu.org wrote: Supriya Sawant sp.sawan...@gmail.com writes: emacs --batch --eval '(org-version)' but it doesn't work. It gives me blank result. emacs --batch --eval '(message (org-version))' HTH, -- Bastien -- Thanks Regards, Supriya Pravin Sawant
Re: [O] how to get org-version using emacs batch mode.
Supriya Sawant sp.sawan...@gmail.com writes: Is it possible to redirect or get the output of batch mode command in variable. Assuming you use bash : $ MYOUTPUT=$(emacs --batch --eval '(princ (org-version))') $ echo $MYOUTPUT 8.2.5c -- Nico.
Re: [O] observations on updating to recent org
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: Bastien b...@gnu.org writes: Nicolas, do you remember why we added IDs to all headlines and not just the one that we be exported in the .ics file? It is a bit difficult to do otherwise. Assuming this is just difficult, not impossible, what would be the way to do it? We don't know beforehand what headlines are going to be exported. Would it be possible to emulate export first just for the sake of adding IDs where it's necessary? We get this information when a headline is encountered during export, which happens in a different buffer, and possibly in a different process. I think it is a minor inconvenience and we can live with it. `org-icalendar-store-UID' is `nil' by default because a value of `t' might be very inconvenient in some circumstances -- quoting the docstring: This variable is not turned on by default because we want to avoid creating a property drawer in every entry if people are only playing with this feature, or if they are only using it locally. One way to adapt to the current behavior is to have a file dedicated to being exported as an ics file -- but for people who want to export entries from their regular files, having all those drawers created everywhere just for the sake of a few entries being picked up for the .ics output certainly feels wrong. I'm interested in enhancing the current behavior if you can give me a few directions. Thanks, -- Bastien
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Looks useful to me, but :file png looks wrong, with too much implicit. We should find something less confusing. One option would be to use :file-ext instead, to generate a :file parameter. I didn’t go this route because autogenerating :file from other parameters seemed like too much magic. But your points in the other direction are good. How does this sound as an algorithm: 1. if :file is present, behave exactly as we do now 2. if :file is absent but :file-ext and a #+name is present, generate a :file parameter from :output-dir, the #+name, and :file-ext. This sounds like a great approach to me. Open questions: 1. should :file-ext without a #+name be a no-op, or an error? One option might be to borrow naming behavior from the comment functionality in ob-tangle which looks like the following (from line 426 in ob-tangle.el). (let (... (source-name (intern (or (nth 4 info) ; explicit #+name: (format %s:%d; constructed from header and position (or (ignore-errors (nth 4 (org-heading-components))) No heading) block-counter ...)) 2. should :output-dir apply to the :file case as well? If you mean should :output-dir be used as the base when :file is a relative pathname then I'd say yes, and I think if this isn't the current behavior then the current behavior should be changed. Thanks for this nice patch, Eric -- Aaron Ecay -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Bastien b...@gnu.org writes: Hi Aaron, Aaron Ecay aarone...@gmail.com writes: How does this sound as an algorithm: 1. if :file is present, behave exactly as we do now 2. if :file is absent but :file-ext and a #+name is present, generate a :file parameter from :output-dir, the #+name, and :file-ext. I suggest this one: 1. if :file is present, behave exactly as we do now 2. if :file-ext is present: - if #+name is present, generate a :file parameter from :output-dir, #+name and :file-ext - otherwise, generate the :file parameter from :output-dir, the headline or the title or the current file name and :file-ext Just falling back on something sensible when :file is absent and :file-ext is specified. FWIW I'm in full agreement here, see my other email for one sensible alternative. (Sorry to split up my reply, the hazards of an asynch/batch email pull/read/write/push setup.) Open questions: 1. should :file-ext without a #+name be a no-op, or an error? See above. 2. should :output-dir apply to the :file case as well? To me yes. In overall I think would be good, but I'd like Eric and other babelist around here to have a look before we commit this. So perhaps another round of patch testing will be good. I agree here. Thanks again, Thanks! -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] observations on updating to recent org
Bastien b...@gnu.org writes: Assuming this is just difficult, not impossible, what would be the way to do it? The major difficulty is to keep an association table between headlines in the pristine original buffer, and headlines in the copy being exported. Note that hooks and Babel code may have deleted or added some, or altered their contents, which means that it is theoretically impossible to get it right. You may want to go for an approximation, i.e., add an ID property only for headlines or inlinetasks with either - a TODO-like keyword, - a SCHEDULED value, - a DEADLINE value, - a timestamp in their contents, - a diary-sexp in their contents. AFAIK, ox-icalendar only considers these for export, so you will often end up marking a super-set of actually exported entries. Unfortunately, this will fail if a user decides to add TODO keywords or timestamps through hooks or Babel (e.g., in order to mark current headline with a today mark). I don't think you can limit the numbers of properties drawers created without inserting some limitations. Would it be possible to emulate export first just for the sake of adding IDs where it's necessary? I don't think so. `org-icalendar-store-UID' is `nil' by default because a value of `t' might be very inconvenient in some circumstances -- quoting the docstring: This variable is not turned on by default because we want to avoid creating a property drawer in every entry if people are only playing with this feature, or if they are only using it locally. I know. Though, I don't find it very inconvenient to create ID properties everywhere once per file. Regards, -- Nicolas Goaziou
Re: [O] Bug: Setting system command org-file-apps does not allow other settings to refer to it [8.2.5h (release_8.2.5h-620-g7fd183 @ /home/rrt/.emacs.d/el-get/package/elpa/org-20140210/)]
On 21 April 2014 20:00, Bastien b...@gnu.org wrote: Hi Reuben, Reuben Thomas r...@sc3d.org writes: 1. I customize org-file-apps's system command to be xdg-open %s, then customize the default command to be the system command. Please share the value of `org-file-apps' (C-h v org-file-apps RET). Value: ((auto-mode . emacs) (\\.mm\\' . default) (\\.x?html?\\' . default) (\\.pdf\\' . default) (t . xdg-open %s) (system . xdg-open %s)) What I've found is that, since .pdf documents can be opened in Emacs and since org-file-apps contains (auto-mode . emacs) as its first element, then changing the system's value to xdg-open after that will fail because (auto-mode . emacs) is applied first. That's interesting, but I'm no less confused. With the value above, PDF files *are* opened with xdg-open. Sure, the docstring needs a bit of simplification, thought. That would be a good start: if I can understand what is supposed to happen, I have some chance to tell whether the actual behaviour is correct or not! Thanks for your continued attention to this issue. -- http://rrt.sc3d.org
Re: [O] Export arrays for 'sh' code blocks when using bash
On Tue, Apr 22, 2014 at 5:22 PM, Bastien b...@gnu.org wrote: Mhh... okay then, thanks for mentioning it. The stackoverflow link contains what appears to be a good workaround that functions in old and new versions of bash. Perhaps Pascal Fleury could modify the org code to avoid using 'declare -A' when bash version 4.
Re: [O] setting left margin in PDF output of ORG file
jdavidb...@adboyd.com (J. David Boyd) writes:
I've looked through all the latex, org-latex, org-beamer variables I can find
with customize-apropos, but not having any luck.
You can use the LaTeX geometry package:
\usepackage[margin=0.25in]{geometry}
HTH,
--
Bastien
[O] setting left margin in PDF output of ORG file
I can export an org file to a PDF no problem, looks great. However, how do I get rid of the huge left and right and top and bottom margins? I like my PDFs to have no more than .75 top, bottom, left and right. I've looked through all the latex, org-latex, org-beamer variables I can find with customize-apropos, but not having any luck. Thanks, Dave
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Hi, Eric Schulte schulte.e...@gmail.com writes: One option might be to borrow naming behavior from the comment functionality in ob-tangle which looks like the following (from line 426 in ob-tangle.el). Indeed, it's safer than just using the buffer file name. Aaron, please go ahead with the patch when you want, thanks again for it! -- Bastien
Re: [O] Bug: Setting system command org-file-apps does not allow other settings to refer to it [8.2.5h (release_8.2.5h-620-g7fd183 @ /home/rrt/.emacs.d/el-get/package/elpa/org-20140210/)]
Hi Reuben, Reuben Thomas r...@sc3d.org writes: Value: ((auto-mode . emacs) (\\.mm\\' . default) (\\.x?html?\\' . default) (\\.pdf\\' . default) (t . xdg-open %s) (system . xdg-open %s)) What I've found is that, since .pdf documents can be opened in Emacs and since org-file-apps contains (auto-mode . emacs) as its first element, then changing the system's value to xdg-open after that will fail because (auto-mode . emacs) is applied first. That's interesting, but I'm no less confused. With the value above, PDF files *are* opened with xdg-open. Okay, see those two bits of `org-file-apps' docstring: `auto-mode'Matches files that are matched by any entry in `auto-mode-alist', so all files Emacs knows how to handle. Using this with command `emacs' will open most files in Emacs. Beware that this will also open html files inside Emacs, unless you add (html . default) to the list as well. So (auto-mode . emacs) says to open .pdf files in emacs... but (\\.pdf\\' . default) says to open .pdf files using the default application: `default' Use the default application for this file type, which is the association for t in the list Since you have (t . xdg-open %s), xdg-open is used. Yep, it's all a bit tricky... -- Bastien
Re: [O] observations on updating to recent org
Greg Troxel g...@ir.bbn.com writes: Exporting to ical as a single file took a really long time, perhaps a whole minute, whereas it used to take a second to a few seconds. The resulting export did seem ok. I timed this. With 6161 lines in 14 org-mode files (about 2175 of which are due to PROPERTIES/ID/END), doing a combined export took 88s of cpu time. emacs-23.4.1, NetBSD 6, i386, plenty of RAM, Core i5 2.9 GHz. In contrast, starting up emacs and generating the agenda took 0.97s. I noticed that TODO entries got exported multiple times, apparently once for each inactive timestamp. (I realize I need to prepare a minimal example.) I used to get an ID PROPERTIES entries for nodes that were exported to the calendar, which was basically nodes that had an active timestamp. But now I had a huge number of changes, adding ID to every node, even those with no real content and just children. Is this a feature? Thanks for the comments; I see the point that this is hard.. For now, I've just turned off uid storing, because I don't sync the exported calendar, and I'll nuke the ID entries and properties drawers at some point; I find them distracting when editing. I wonder if there's some way to go back and store the UID when it actually needs to be generated, so that UIDs are only stored for entries that actually have been exported. I only want to export appointments, by which I mean entries with active timestamps, which are pretty few in number compared to nodes. Greg pgpLoLtCr7RyY.pgp Description: PGP signature
Re: [O] observations on updating to recent org
Hello, Greg Troxel g...@ir.bbn.com writes: I timed this. With 6161 lines in 14 org-mode files (about 2175 of which are due to PROPERTIES/ID/END), doing a combined export took 88s of cpu time. emacs-23.4.1, NetBSD 6, i386, plenty of RAM, Core i5 2.9 GHz. In contrast, starting up emacs and generating the agenda took 0.97s. You may want to use ELP to instrument Org and report where most time is spent. I noticed that TODO entries got exported multiple times, apparently once for each inactive timestamp. (I realize I need to prepare a minimal example.) This is to be expected. Each plain timestamp defines a new VEVENT block. By default, it shouldn't do this for inactive timestamps, though. See `org-icalendar-with-timestamps'. Thanks for the comments; I see the point that this is hard.. For now, I've just turned off uid storing, because I don't sync the exported calendar, and I'll nuke the ID entries and properties drawers at some point; I find them distracting when editing. Note that UID storing is off by default. I wonder if there's some way to go back and store the UID when it actually needs to be generated, so that UIDs are only stored for entries that actually have been exported. This is not really possible without some sacrifices (which Bastien may or may not want to do). See other messages in this thread. Also, since you don't need UID anyway, why is that a problem anymore? I'm a bit confused here. Regards, -- Nicolas Goaziou
Re: [O] observations on updating to recent org
Nicolas Goaziou n.goaz...@gmail.com writes: Greg Troxel g...@ir.bbn.com writes: I timed this. With 6161 lines in 14 org-mode files (about 2175 of which are due to PROPERTIES/ID/END), doing a combined export took 88s of cpu time. emacs-23.4.1, NetBSD 6, i386, plenty of RAM, Core i5 2.9 GHz. In contrast, starting up emacs and generating the agenda took 0.97s. You may want to use ELP to instrument Org and report where most time is spent. OK - will try to do that. I noticed that TODO entries got exported multiple times, apparently once for each inactive timestamp. (I realize I need to prepare a minimal example.) This is to be expected. Each plain timestamp defines a new VEVENT block. I guess that's an interesting question about what makes sense. Here's the actual todo entry, with just a few words redacted. I don't see why someone would want VEVENTS for this kind of history, but I suppose maybe that's what you get when you turn on events from inactive timestamps. * TODO [#C] order more [redacted] SCHEDULED: 2014-04-28 Mon .+4w - State DONE from TODO [2013-11-07 Thu 10:30] - State DONE from TODO [2013-08-05 Mon 16:27] - State DONE from WAITING[2013-06-04 Tue 10:27] - State WAITINGfrom TODO [2013-05-28 Tue 11:19] \\ ordered via [redacted] - State DONE from TODO [2013-03-25 Mon 23:16] laura did - State DONE from WAITING[2013-01-08 Tue 11:49] - State WAITINGfrom TODO [2012-12-18 Tue 20:41] \\ ordered - State TODO from WAITING[2012-09-20 Thu 13:05] - State WAITINGfrom TODO [2012-09-13 Thu 10:01] \\ ordered - State DONE from TODO [2012-07-12 Thu 10:39] - State DONE from TODO [2012-06-04 Mon 14:22] - State DONE from TODO [2012-03-27 Tue 08:54] - State DONE from TODO [2011-10-01 Sat 08:10] :PROPERTIES: :ID: b617c8e4-c8f2-11e0-8735-000476353fb4 :LAST_REPEAT: [2013-11-07 Thu 10:30] :END: By default, it shouldn't do this for inactive timestamps, though. See `org-icalendar-with-timestamps'. I didn't try to turn this on. My icalendar-relevant settings are (setq org-icalendar-alarm-time 10) (setq org-icalendar-use-scheduled nil) (setq org-icalendar-use-deadline nil) I am trying to get ics entries only for headlines with active timestamps. Thanks for the comments; I see the point that this is hard.. For now, I've just turned off uid storing, because I don't sync the exported calendar, and I'll nuke the ID entries and properties drawers at some point; I find them distracting when editing. Note that UID storing is off by default. Yes - I had it turned on intentionally from long ago. I wonder if there's some way to go back and store the UID when it actually needs to be generated, so that UIDs are only stored for entries that actually have been exported. This is not really possible without some sacrifices (which Bastien may or may not want to do). See other messages in this thread. I did see them, but I guess I just don't understand enough for this to make sense. That's ok - please don't try harder to explain to me :-) Also, since you don't need UID anyway, why is that a problem anymore? I'm a bit confused here. It's not a problem for me any more. It just seems really unfortunate for others in the general case to have extra content in every headline when it isn't necessary. pgprezh66bXsI.pgp Description: PGP signature
Re: [O] Export arrays for 'sh' code blocks when using bash
On Wed, Apr 23, 2014 at 10:13 AM, Pascal Fleury fle...@google.com wrote: (have not used bash3 in quite a long time :-) Even OS X Mavericks uses bash 3. So it will be around for quite a long time.
Re: [O] observations on updating to recent org
Greg Troxel g...@ir.bbn.com writes: I guess that's an interesting question about what makes sense. Here's the actual todo entry, with just a few words redacted. I don't see why someone would want VEVENTS for this kind of history, but I suppose maybe that's what you get when you turn on events from inactive timestamps. * TODO [#C] order more [redacted] SCHEDULED: 2014-04-28 Mon .+4w - State DONE from TODO [2013-11-07 Thu 10:30] - State DONE from TODO [2013-08-05 Mon 16:27] - State DONE from WAITING[2013-06-04 Tue 10:27] - State WAITINGfrom TODO [2013-05-28 Tue 11:19] \\ ordered via [redacted] - State DONE from TODO [2013-03-25 Mon 23:16] laura did - State DONE from WAITING[2013-01-08 Tue 11:49] - State WAITINGfrom TODO [2012-12-18 Tue 20:41] \\ ordered - State TODO from WAITING[2012-09-20 Thu 13:05] - State WAITINGfrom TODO [2012-09-13 Thu 10:01] \\ ordered - State DONE from TODO [2012-07-12 Thu 10:39] - State DONE from TODO [2012-06-04 Mon 14:22] - State DONE from TODO [2012-03-27 Tue 08:54] - State DONE from TODO [2011-10-01 Sat 08:10] :PROPERTIES: :ID: b617c8e4-c8f2-11e0-8735-000476353fb4 :LAST_REPEAT: [2013-11-07 Thu 10:30] :END: By default, no VEVENT should be created from any timestamp in your example. By default, it shouldn't do this for inactive timestamps, though. See `org-icalendar-with-timestamps'. I didn't try to turn this on. My icalendar-relevant settings are (setq org-icalendar-alarm-time 10) (setq org-icalendar-use-scheduled nil) (setq org-icalendar-use-deadline nil) I am trying to get ics entries only for headlines with active timestamps. It is a bug then. I'll look into it in a few hours. It's not a problem for me any more. It just seems really unfortunate for others in the general case to have extra content in every headline when it isn't necessary. If there are few exported headlines in the document, it is also possible to keep `org-icalendar-store-UID' to nil and add ID value manually for each of them. Regards, -- Nicolas Goaziou
Re: [O] setting left margin in PDF output of ORG file
Bastien b...@gnu.org writes:
jdavidb...@adboyd.com (J. David Boyd) writes:
I've looked through all the latex, org-latex, org-beamer variables I can
find with customize-apropos, but not having any luck.
You can use the LaTeX geometry package:
\usepackage[margin=0.25in]{geometry}
HTH,
Thanks, but since my LaTeX-fu and Org-fu are quite weak, where would I use
this at?
I can put it into the .tex file that is created manually, then run pdflatex 3
times like org does, but there must be somewhere to put it into the org
config, yes?
Dave
Re: [O] setting left margin in PDF output of ORG file
On Wed, Apr 23, 2014 at 11:59 AM, J. David Boyd jdavidb...@adboyd.com wrote:
Bastien b...@gnu.org writes:
jdavidb...@adboyd.com (J. David Boyd) writes:
I've looked through all the latex, org-latex, org-beamer variables I can
find with customize-apropos, but not having any luck.
You can use the LaTeX geometry package:
\usepackage[margin=0.25in]{geometry}
HTH,
Thanks, but since my LaTeX-fu and Org-fu are quite weak, where would I use
this at?
I have a line at the top like so:
#+latex_header: \usepackage[margin=0.25in]{geometry}
(Mine's different, but that's the analog for this case). Anything you
would normally put in LaTeX straight-up, like commands, settings,
packages, etc. would go into #+latex_header: lines in Orgmode. Here's
an example of my default setup:
#+AUTHOR:John Henderson
#+OPTIONS: *:t TeX:t H:5 creator:nil
#+latex_header: \usepackage[hmargin=2.5cm,vmargin=2.5cm]{geometry}
#+latex_header: \usepackage{mathpazo} \usepackage{paralist}
#+latex_header: \usepackage{enumitem}
#+latex_header: \setlength{\parskip}{0.5cm} \setlength{\parindent}{0cm}
#+latex_header: \usepackage{lscape}
#+latex_header: \usepackage{booktabs}
#+latex_header: \hypersetup{colorlinks=true,linkcolor=blue,urlcolor=blue}
Just wanted to give an example of how you might setup Org to do what
you want in LaTeX/PDF output.
To go even further, I don't even have the above in each Org file. I
keep it in ~/org/aux/setupfile.org. Then in each file I create, I use
this line:
#+setupfile: ~/org/aux/setupfile.org
So, for any regularly used options, I just leave them in setupfile.org
and bring them in with the above line for new files. For things I want
to set per-file, I'd add a file-specific #+latex_header line, or tweak
the #+options parameters.
John
I can put it into the .tex file that is created manually, then run pdflatex 3
times like org does, but there must be somewhere to put it into the org
config, yes?
Dave
Re: [O] setting left margin in PDF output of ORG file
jdavidb...@adboyd.com (J. David Boyd) writes:
Bastien b...@gnu.org writes:
jdavidb...@adboyd.com (J. David Boyd) writes:
I've looked through all the latex, org-latex, org-beamer variables I can
find with customize-apropos, but not having any luck.
You can use the LaTeX geometry package:
\usepackage[margin=0.25in]{geometry}
HTH,
Thanks, but since my LaTeX-fu and Org-fu are quite weak, where would I use
this at?
I can put it into the .tex file that is created manually, then run pdflatex 3
times like org does, but there must be somewhere to put it into the org
config, yes?
In the org file:
#+LATEX_HEADER: \usepackage[margin=0.25in]{geometry}
If you want to make this the default, you can customize
org-latex-packages-alist:
(add-to-list 'org-latex-packages-alist
'(margin=0.25in geometry nil))
Nick
Re: [O] setting left margin in PDF output of ORG file
John Hendy jw.he...@gmail.com writes:
On Wed, Apr 23, 2014 at 11:59 AM, J. David Boyd jdavidb...@adboyd.com wrote:
Bastien b...@gnu.org writes:
jdavidb...@adboyd.com (J. David Boyd) writes:
I've looked through all the latex, org-latex, org-beamer variables I can
find with customize-apropos, but not having any luck.
You can use the LaTeX geometry package:
\usepackage[margin=0.25in]{geometry}
HTH,
Thanks, but since my LaTeX-fu and Org-fu are quite weak, where would I use
this at?
I have a line at the top like so:
#+latex_header: \usepackage[margin=0.25in]{geometry}
(Mine's different, but that's the analog for this case). Anything you
would normally put in LaTeX straight-up, like commands, settings,
packages, etc. would go into #+latex_header: lines in Orgmode. Here's
an example of my default setup:
#+AUTHOR:John Henderson
#+OPTIONS: *:t TeX:t H:5 creator:nil
#+latex_header: \usepackage[hmargin=2.5cm,vmargin=2.5cm]{geometry}
#+latex_header: \usepackage{mathpazo} \usepackage{paralist}
#+latex_header: \usepackage{enumitem}
#+latex_header: \setlength{\parskip}{0.5cm} \setlength{\parindent}{0cm}
#+latex_header: \usepackage{lscape}
#+latex_header: \usepackage{booktabs}
#+latex_header: \hypersetup{colorlinks=true,linkcolor=blue,urlcolor=blue}
Just wanted to give an example of how you might setup Org to do what
you want in LaTeX/PDF output.
To go even further, I don't even have the above in each Org file. I
keep it in ~/org/aux/setupfile.org. Then in each file I create, I use
this line:
#+setupfile: ~/org/aux/setupfile.org
So, for any regularly used options, I just leave them in setupfile.org
and bring them in with the above line for new files. For things I want
to set per-file, I'd add a file-specific #+latex_header line, or tweak
the #+options parameters.
John
Thanks very much! Exactly what I was looking for.
Dave
Re: [O] setting left margin in PDF output of ORG file
Nick Dokos ndo...@gmail.com writes:
jdavidb...@adboyd.com (J. David Boyd) writes:
Bastien b...@gnu.org writes:
jdavidb...@adboyd.com (J. David Boyd) writes:
I've looked through all the latex, org-latex, org-beamer variables I can
find with customize-apropos, but not having any luck.
You can use the LaTeX geometry package:
\usepackage[margin=0.25in]{geometry}
HTH,
Thanks, but since my LaTeX-fu and Org-fu are quite weak, where would I use
this at?
I can put it into the .tex file that is created manually, then run pdflatex 3
times like org does, but there must be somewhere to put it into the org
config, yes?
In the org file:
#+LATEX_HEADER: \usepackage[margin=0.25in]{geometry}
If you want to make this the default, you can customize
org-latex-packages-alist:
(add-to-list 'org-latex-packages-alist
'(margin=0.25in geometry nil))
Nick
Beautiful! Thanks very much. I'll definitely be adding it into my defaults.
Have a great orging day!
Dave
Re: [O] observations on updating to recent org
Nicolas Goaziou n.goaz...@gmail.com writes: Greg Troxel g...@ir.bbn.com writes: I didn't try to turn this on. My icalendar-relevant settings are (setq org-icalendar-alarm-time 10) (setq org-icalendar-use-scheduled nil) (setq org-icalendar-use-deadline nil) I am trying to get ics entries only for headlines with active timestamps. It is a bug then. I'll look into it in a few hours. This should be fixed. Thank you for the report. Regards, -- Nicolas Goaziou
Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Aaron Ecay writes: How does this sound as an algorithm: 1. if :file is present, behave exactly as we do now 2. if :file is absent but :file-ext and a #+name is present, generate a :file parameter from :output-dir, the #+name, and :file-ext. 3. If both :file and :file-ext are present, :file takes precedence and :file-ext is ignored. 1. should :file-ext without a #+name be a no-op, or an error? Since you are hoping to inherit these via properties, this should be a nop if not applicable. 2. should :output-dir apply to the :file case as well? I'd say no since it seems this would be backwards-incompatible. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [BUG] Cannot open load file: ob-sh
Bastien writes: Nick Dokos ndo...@gmail.com writes: Check local.mk for BTEST_OB_LANGUAGES: delete sh if present. Or rename sh to shell. No, delete it. There is no reason to include it there since it is automatically present when testing. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [RFC] Sloppy `org-element-context'?
Hello, Bastien b...@gnu.org writes: I don't think `org-element-context' should be sloppy *at all*. [...] For example, on a comment, (eq 'comment (car (org-element-at-point))) *coughs* (eq 'comment (org-element-type (org-element-at-point))) should always return `t'. But if the user wants to open bracket links from comments (or in a property), then something like this would do: (defun org-open-links-in-comment-and-properties () Open links in a comment or in a property. (interactive) (let ((string-ahead (and (looking-at .+) (match-string 0))) (buffer-substring (point) (line-end-position)) (value (org-element-property :value (org-element-at-point (with-temp-buffer (org-mode) (let ((org-inhibit-startup t)) (org-mode)) (insert value) (goto-char (point-min)) (search-forward string-ahead) (org-open-at-point which do work right now. Indeed. Of course this could be generalized, provided the property to consider is always named :value, which is not the case IIUC: sometimes it's :raw-data, right? No, :raw-value are different and shouldn't get in the way in this case. Last but not least: the spirit of the solution shown above does not prevent amending the syntax if we *really* need to amend it, but that's where I'd be as conservative as possible -- that is, as *you* :) Indeed. Hope this all makes sense -- let me know what you think. I agree. We can ignore the patch. Regards, -- Nicolas Goaziou
Re: [O] (org-insert-headline '(4)) should insert new headline before point
Hi Bastien, I just wanted to report an issue with this fix. In many use cases it makes C-RET less useful, and renders the speedkeys command `i' useless. It makes C-RET function much like M-RET, and it makes `i' insert headlines before any content. So if I call C-RET in the middle of the following headline: --- ** Important Meeting SCHEDULED: 2014-04-26 Sat 16:30 headline content... --- I get: --- ** Important ** Meeting SCHEDULED: 2014-04-26 Sat 16:00 headline content... --- And when I use the speedkeys command `i' at the beginning, I get --- ** Important Meeting ** SCHEDULED: 2014-04-26 Sat 16:00 headline content... --- Both of these break the scheduling cookie and defeat the main purpose of these commands. Reverting the change restores expected behavior in these cases, but then I suppose we are left with York's problem. All best, Leonard On 22 April 2014 10:23, Bastien b...@gnu.org wrote: Hi York, thanks for coming back to this. York Zhao gtdplatf...@gmail.com writes: What I meant was that with one prefix argument, the command `org-insert-heading' should insert a new heading *before* the current heading, not after. Actually, this has little to do with the prefix argument: when at the beginning of a heading or a list item, M-RET should add a new heading/item *before* the current heading/item. This is fixed now, thanks for reporting this, PS: Using C-u M-RET will force `org-insert-heading-respect-content' to `t', i.e. add the headline at the end of the subtree. As Nicolas noted, this is the same than C-RET. -- Bastien
Re: [O] (org-insert-headline '(4)) should insert new headline before point
Sorry, I should clarify that the C-RET functions as expected in the content of an entry, it is only problematic when it is called from the headline. All best, Leonard On 23 April 2014 22:42, Leonard Randall leonard.a.rand...@gmail.com wrote: Hi Bastien, I just wanted to report an issue with this fix. In many use cases it makes C-RET less useful, and renders the speedkeys command `i' useless. It makes C-RET function much like M-RET, and it makes `i' insert headlines before any content. So if I call C-RET in the middle of the following headline: --- ** Important Meeting SCHEDULED: 2014-04-26 Sat 16:30 headline content... --- I get: --- ** Important ** Meeting SCHEDULED: 2014-04-26 Sat 16:00 headline content... --- And when I use the speedkeys command `i' at the beginning, I get --- ** Important Meeting ** SCHEDULED: 2014-04-26 Sat 16:00 headline content... --- Both of these break the scheduling cookie and defeat the main purpose of these commands. Reverting the change restores expected behavior in these cases, but then I suppose we are left with York's problem. All best, Leonard On 22 April 2014 10:23, Bastien b...@gnu.org wrote: Hi York, thanks for coming back to this. York Zhao gtdplatf...@gmail.com writes: What I meant was that with one prefix argument, the command `org-insert-heading' should insert a new heading *before* the current heading, not after. Actually, this has little to do with the prefix argument: when at the beginning of a heading or a list item, M-RET should add a new heading/item *before* the current heading/item. This is fixed now, thanks for reporting this, PS: Using C-u M-RET will force `org-insert-heading-respect-content' to `t', i.e. add the headline at the end of the subtree. As Nicolas noted, this is the same than C-RET. -- Bastien
[O] Trying to separate clocked time /ranges/ from scheduled times in a clean-ish view.
I can't see how to get a clean view of clocked time ranges. Not just the length of time, but the actual start and end times. I would like to share my attempts to give you an idea. If I include (org-agenda-start-with-log-mode '(closed clock state)) in my agenda block, then I can see them, but unfortunately I am clocking on items I've scheduled for myself, so they mix in and it is hard to read quickly. That is, I have #+BEGIN_SRC ** example *** circus act:routine: backflips CLOCK: [2014-04-23 Wed 07:45]--[2014-04-23 Wed 07:48] = 0:03 SCHEDULED: 2014-04-23 Wed 07:45-07:50 :PROPERTIES: :Effort: 0:05 :END: somersaults SCHEDULED: 2014-04-23 Wed 07:50-08:00 CLOCK: [2014-04-23 Wed 07:48]--[2014-04-23 Wed 07:52] = 0:04 :PROPERTIES: :Effort: 0:10 :END: front flips :PROPERTIES: :Effort: 0:10 :END: *** feed elephant :routine: SCHEDULED: 2014-04-23 Wed 21:10-21:30 :PROPERTIES: :Effort: 0:20 :END: *** tell fortune :routine: SCHEDULED: 2014-04-23 Wed 08:00-08:20 CLOCK: [2014-04-23 Wed 07:52]--[2014-04-23 Wed 08:10] = 0:18 :PROPERTIES: :Effort: 0:20 :END: #+END_SRC In an `agenda' block, I have tried to filter the scheduled lines out, and keep the clock lines, but filters seem to work before deciding to include the clocking, so the pair, scheduled and clocked will vanish together. (If I could get a view of just clock time ranges, I might use a sticky buffer to see one agenda block with scheduled time ranges, and another agenda block with clocked time ranges.) I tried using a clock report table, but I can't see how to get the actual clocked time, instead of the timestamp range. Via (org-agenda-start-with-clockreport-mode t) I've looked at column view as a possibility, but again, the clock time does not seem to be available. I tried to use the `search' block, but did not think of a way to display only clock times there. Here are the results of my best tries at an agenda view. (I found it a little awkward to compare clocked times to scheduled times as they are mixed in here.) _ / / Day-agenda (W17): Wednesday 23 April 2014 agendatest: 7:45- 7:48 Clocked: (0:03) backflips:routine:: agendatest: 7:45- 7:50 Scheduled: backflips :routine:: agendatest: 7:48- 7:52 Clocked: (0:04) somersaults :routine:: agendatest: 7:50- 8:00 Scheduled: somersaults:routine:: agendatest: 7:52- 8:10 Clocked: (0:18) tell fortune :routine: agendatest: 8:00- 8:20 Scheduled: tell fortune:routine: 8:00.. 10:00.. 12:00.. 14:00.. 16:00.. 17:15.. now - - - - - - - - - - - - - - - - - - - - - 18:00.. 20:00.. agendatest: 21:10-21:30 Scheduled: feed elephant :routine: | Timestamp | Effort | Headline| Time | |++-++-- | ALL|| *Total time*| *0:25* | |++-++-- ||| *File time* | *0:25* | ||| circus act | 0:07 | | 2014-04-23 Wed 07:45-07:50 | 0:05 | \__ backflips || 0:03 | 2014-04-23 Wed 07:50-08:00 | 0:10 | \__ somersaults || 0:04 | 2014-04-23 Wed 08:00-08:20 | 0:20 | tell fortune| 0:18 | = Search words: CLOCK agendatest: backflips :routine:: agendatest: somersaults:routine:: agendatest: tell fortune:routine: \ \ Finally, here is my custom-command that I have been working on: #+BEGIN_SRC emacs-lisp (org-add-agenda-custom-command '(r routine ((agenda ( (org-clocktable-defaults '( :timestamp t :properties (Effort) :indent t )) ) ) (search CLOCK) ) ( (org-agenda-files '(/e/org/agendatest.org)) (org-agenda-span 'day) (org-agenda-start-with-clockreport-mode t) (org-agenda-start-with-log-mode '(closed clock state)) (org-agenda-tag-filter-preset '(+routine)) ) )) #+END_SRC To give a visual of what I am trying to do, Day-agenda (W17): Wednesday 23 April 2014 agendatest: 7:45- 7:48 Clocked: (0:03) backflips:routine:: agendatest:
Re: [O] Export arrays for 'sh' code blocks when using bash
Skip Collins skip.coll...@gmail.com writes: On Wed, Apr 23, 2014 at 10:13 AM, Pascal Fleury fle...@google.com wrote: (have not used bash3 in quite a long time :-) Even OS X Mavericks uses bash 3. So it will be around for quite a long time. I believe Bash 4 is GPLv3 and Bash 3 is GPLv2, so it is very possible that OSX will never upgrade to the current bash. If the fix is obvious and simple then it sounds like a win. I suppose the argument could be made that an Emacs project should not go out of it's way to support old versions of software which are potentially being used only to avoid GPLv3 licensing... but I won't make that argument here. -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] How do I chain babel blocks with arguments?
Alan Schmitt alan.schm...@polytechnique.org writes: Hi Eric, On 2014-04-22 13:30, Eric Schulte schulte.e...@gmail.com writes: Sorry, that's because the x should be z. See the following. #+name: z : bar #+name: test3 #+begin_src emacs-lisp :var x=foo x #+end_src #+RESULTS: test3 : foo #+name:test4 #+begin_src emacs-lisp :var y=test3(x=z) y #+end_src #+results: test4 : bar #+call: test4(y=BAZ) #+RESULTS: : BAZ I'm afraid I'm not being clear: I want to use the result of `test3' in the computation done to test4. Intuitively, I want test4 to be something like: (lambda (x) (... (test3 x) ...)). This is why I was writing a header of the form: #+begin_src emacs-lisp :var x=foo :var y=test3(x) where x would be given by the call to the block, and y would only be used internally. I see, then sbe is probably the way to go. Best, Thanks, Alan -- Eric Schulte https://cs.unm.edu/~eschulte PGP: 0x614CA05D
Re: [O] Trying to separate clocked time /ranges/ from scheduled times in a clean-ish view.
On 4/23/2014 5:47 PM, Brady Trainor wrote: Day-agenda (W17): Wednesday 23 April 2014 agendatest: 7:45- 7:48 Clocked: (0:03) backflips:routine:: agendatest: 7:45- 7:50 Scheduled: backflips :routine:: agendatest: 7:48- 7:52 Clocked: (0:04) somersaults :routine:: agendatest: 7:50- 8:00 Scheduled: somersaults:routine:: agendatest: 7:52- 8:10 Clocked: (0:18) tell fortune :routine: agendatest: 8:00- 8:20 Scheduled: tell fortune:routine: 8:00.. 10:00.. Even if I could make this a little more vertically aligned, like somehow entering the effort. Day-agenda (W17): Wednesday 23 April 2014 agendatest: 7:45- 7:48 Clocked: (0:03) backflips:routine:: agendatest: 7:45- 7:50 Scheduled: [0:05] backflips:routine:: agendatest: 7:48- 7:52 Clocked: (0:04) somersaults :routine:: agendatest: 7:50- 8:00 Scheduled: [0:10] somersaults :routine:: agendatest: 7:52- 8:10 Clocked: (0:18) tell fortune :routine: agendatest: 8:00- 8:20 Scheduled: [0:20] tell fortune :routine: 8:00.. 10:00.. could make it a bit more readable for me. (Maybe this would be made to only turn on with `l' in the agenda.) But my synapses are fully extended to get here, so I am not seeing how to do this either. Brady
[O] auto-roll-over of org-todo's?
In my agenda I have several items I call my weeklies because they repeat weekly, this is one of them - --8---cut here---start-8--- Desert island discs - radio 2 @ 1100 SCHEDULED: 2014-04-27 Sun +7d --8---cut here---end---8--- Is there any way in which it can be auto-rolled-over every Sunday without intervention from myself please? Thanks Sharon. -- A taste of linux = http://www.sharons.org.uk my git repo = https://bitbucket.org/boudiccas/dots TGmeds = http://www.tgmeds.org.uk Debian testing, Fluxbox 1.3.5, emacs 24.4.50.10 signature.asc Description: PGP signature
