Re: [O] [RFC] [PATCH] ob-core.el: allow the auto-generation of output file names for src blocks.
Aaron Ecay writes: Thanks so much for the feedback. I’ve adopted the :file-ext approach suggested by Bastien, leaving the previous default behavior in place for blocks with a :file argument. THanks for taking care, I'll not have time to look at this for the remainder of the week, though… Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Waldorf MIDI Implementation additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] Org version of texinfo manual
Aaron Ecay writes: Last year, Thomas started a project to translate the org manual to org format, and use the ox-texinfo exporter to generate the .info and .pdf manuals. (email thread: http://mid.gmane.org/m1bob8cffh@tsdye.com) It seems like that project showed promise but never was completed. Is there any interest in seeing it through? As an occasional contributor, I would certainly find it pleasanter and less time-consuming to write docs in org rather than texinfo. I'm still in favor of doing this, but it will be an uphill battle. I'll have to check what the state of my local branch is on this, let me get back to you when it at least compiles the old version of the manual. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
[O] org-bbdb link completion fix
The most recent versions of BBDB return single records from `bbdb-completing-read-record'. That currently breaks completion on bbdb: links -- possibly earlier versions of BBDB always returned list values. We should probably check for this in `org-bbdb-complete-link', I propose the attached patch. Thanks, Eric diff --git a/lisp/org-bbdb.el b/lisp/org-bbdb.el index b9841a6..cfd5b3b 100644 --- a/lisp/org-bbdb.el +++ b/lisp/org-bbdb.el @@ -400,8 +400,11 @@ This is used by Org to re-create the anniversary hash table. (defun org-bbdb-complete-link () Read a bbdb link with name completion. (require 'bbdb-com) - (concat bbdb: - (bbdb-record-name (car (bbdb-completing-read-record Name: ) + (let ((rec (bbdb-completing-read-record Name: ))) +(concat bbdb: + (bbdb-record-name (if (listp rec) + (car rec) +rec) (defun org-bbdb-anniv-export-ical () Extract anniversaries from BBDB and convert them to icalendar format.
Re: [O] What happened to clocktable in pdf export?
Am 25.04.2014 16:07, schrieb Buddy Butterfly: Hi, what happened to the pdf export of clocktables? After the upgrade to Ubuntu 13.10 (emacs 24.3.1), the clocktable export looks ugly as hell. With the latex headers aligne=l|r etc. and the indentation in the clocktable I got a very nice export before. The lines where also indented and I had vertical separators for the columns. Now, in the new version I get in the PDF for the indentation (\_) and there are not separator lines between columns. What changed? Is it just configuration or did change completely? Cheers, Matt Any idea what could have caused the change? Is it texlive or within Emacs?
Re: [O] What happened to clocktable in pdf export?
Hello, Buddy Butterfly buddy.butter...@web.de writes: Any idea what could have caused the change? Is it texlive or within Emacs? Would you mind posting a simple example? Regards, -- Nicolas Goaziou
Re: [O] org-review-schedule
Hi Alexander, On 2014-04-28 09:20, AW alexander.will...@t-online.de writes: Am Sonntag, 27. April 2014, 10:09:35 schrieb Alan Schmitt: On 2014-04-25 10:02, Nicolas Goaziou n.goaz...@gmail.com writes: Alan Schmitt alan.schm...@polytechnique.org writes: I guess I should have asked: who decides what goes in contrib? The Org maintainer. Another option is to turn it into an ELPA package. I need to learn how to do this. In the meantime, I've put the code on github: https://github.com/brabalan/org-review Alan I'm really interessted in a more sophisticated review system than to put REVIEW on the list of TODO | DONE items. I guess you are having a good point here and your code will improve orgmode. But after reading your initial post and the README on github I'm not sure how to use your code. Could you complete your Example in the README, please? I've just expanded on the README. Please let me know if you have additional questions. 1. Probably -- sorry, I'm lacking of lisp understanding -- we need to put the file org-review.el into a place where Emacs can find it. Yes. 2. It is probably necessary to add (require 'org-review) before the code in the example into the .emacs file, or am I wrong? Yes, it is necessary. 3. Usually people have something like #+TODO: TODO INPUT ASK MAYBE | DONE in their org-file or an equivalent in their .emacs file. What will happen to such customisations? Nothing. Review tracking is done using properties, not keywords. Best, Alan
[O] org-babel pass data between blocks
Dear All, Is there way to pass data between blocks in org-babel. For example lets say have two blocks #+begin_src python from pylab import * # Simple carrier t=linspace(0,1,100); fc=100; Ac =1; C=Ac*cos(2*pi*t); #+end_src What I would like to do is to pass both C and t to another python block, but it is not clear how to do this. #+begin_src python from pylab import * fm=1; Am=1 m=Am*cos(2*pi*t); # message signal z=m*C; #double side-band modulated signal #+end_src Thanks, M
[O] Setting startup to contents does not seem to work.
Visiting this file --8---cut here---start-8--- #+STARTUP: contents * Foo ** Bar ** Baz * Foo2 ** Bar2 ** Baz2 --8---cut here---end---8--- just shows the folded top-level Foo headlines: Bar and Baz headlines are invisible. That's not the way it's supposed to work, I think. Anybody else see that? Org-mode version 8.2.6 (release_8.2.6-901-g91da1b @ /home/nick/elisp/org-mode/lisp/) GNU Emacs 24.4.50.1 (x86_64-unknown-linux-gnu, GTK+ Version 3.6.4) of 2014-03-27 Thanks, Nick
Re: [O] org-babel pass data between blocks
On 2014-04-28 14:41, Marvin Doyley marvin...@gmail.com writes: Dear All, Is there way to pass data between blocks in org-babel. For example lets say have two blocks #+begin_src python from pylab import * # Simple carrier t=linspace(0,1,100); fc=100; Ac =1; C=Ac*cos(2*pi*t); #+end_src What I would like to do is to pass both C and t to another python block, but it is not clear how to do this. #+begin_src python from pylab import * fm=1; Am=1 m=Am*cos(2*pi*t); # message signal z=m*C; #double side-band modulated signal #+end_src I see three options (there are probably many others): - use a session (see http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.html for instance); - have C and t be the results of the first block, and chain the blocks; - use noweb to include the second block is the first block. Alan
Re: [O] Prepare release 8.2.6
Just checked it with Org-mode version 8.2.6 (release_8.2.6-936-gd9e6bd @ /Users/rainerkrug/.emacs.d/org-mode/lisp/) and it works there. Cheers, Rainer Bastien b...@gnu.org writes: Hi Rainer, Rainer M Krug rai...@krugs.de writes: This has been introduced within the previous week, if I am not mistaken. Can you try to bisect a bit more? Maybe look for a commit that changed property inheritance, as it looks like it's related. Thanks, -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 pgp4Hz2V7Gpq8.pgp Description: PGP signature
[O] Copyright assignment
Hi I have received the signed copyright assignment - should I re-send the patches for ob-R.el? Thanks, Rainer -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Stellenbosch University South Africa Tel : +33 - (0)9 53 10 27 44 Cell: +33 - (0)6 85 62 59 98 Fax : +33 - (0)9 58 10 27 44 Fax (D):+49 - (0)3 21 21 25 22 44 email: rai...@krugs.de Skype: RMkrug PGP: 0x0F52F982 pgpQKyJhHElpz.pgp Description: PGP signature
Re: [O] setting left margin in PDF output of ORG file
On 2014-04-25, John Hendy wrote: I have to ask: is whatever was once considered the golden ratio for text-to-whitespace in printed material, or even used by Gutenberg himself for proper typesetting considered relevant/best practice today? Yes, at least partly. Verachtet mir die alten Meister nicht! (Do not condemn the old masters!) -- Richard Wagner Default Org - LaTeX article looks *ugly as all hell* to me. Check the Komascript classes. Other than theoretical principle, is there evidence that readers prefer the look of the default LaTeX article sizing? Beyond all aesthetic meanings, there are some practical aspects that are valid for all presentations of text to readers. The most important rule is that the number of characters per line shall not exceed 70. Together with the chosen font, its size, and tracking, this rule defines the width of the type area. Together with the interlinear space, this rule is relevant for the readability. The longer the line, the larger (but not to large!) the interlinear space. Thus for printed papers where the most economical use of paper is important, a multi-column layout is the way to go to get the smallest margins. -- Michael Strey www.strey.biz
[O] Emphasis in title export
I have a title in which I need to have some text in italics. I tried this: #+TITLE: Analysis of Sartre's /No Exit/ But the slashes were just exported literally, instead of italicizing. This seemed like a pretty basic problem, but I've been unable to find anything about it via Google or in the list archives. Is there a simple solution? Thanks, Will
Re: [O] org-babel pass data between blocks
Thanks, Your first option works like a charm cheers, M On Apr 28, 2014, at 9:07 AM, Alan Schmitt alan.schm...@polytechnique.org wrote: On 2014-04-28 14:41, Marvin Doyley marvin...@gmail.com writes: Dear All, Is there way to pass data between blocks in org-babel. For example lets say have two blocks #+begin_src python from pylab import * # Simple carrier t=linspace(0,1,100); fc=100; Ac =1; C=Ac*cos(2*pi*t); #+end_src What I would like to do is to pass both C and t to another python block, but it is not clear how to do this. #+begin_src python from pylab import * fm=1; Am=1 m=Am*cos(2*pi*t); # message signal z=m*C; #double side-band modulated signal #+end_src I see three options (there are probably many others): - use a session (see http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-python.html for instance); - have C and t be the results of the first block, and chain the blocks; - use noweb to include the second block is the first block. Alan
Re: [O] org-bbdb link completion fix
Hello, Eric Abrahamsen e...@ericabrahamsen.net writes: The most recent versions of BBDB return single records from `bbdb-completing-read-record'. That currently breaks completion on bbdb: links -- possibly earlier versions of BBDB always returned list values. We should probably check for this in `org-bbdb-complete-link', I propose the attached patch. Thank you for the patch. Would you mind providing a proper commit message and send it again? Regards, -- Nicolas Goaziou
Re: [O] State of the art in citations
Hi Leonard, Yes, I will be definitively interested on this! Thanks! Julian Leonard Randall writes: Hi Julian et al., I am not sure if this helps, but I am in the process of writing a new package for inserting citations into org buffers using RefTeX. This solution would make citation insertion very convenient, but it would not be quite as easy to read as Clément's solution, and it would only work for latex export. (It might work with html export if you used bibtex to html, but I do not have enough experience with bibtex to html to know.) On the other hand, it will work with multicite commands, whereas Clement's does not look like it will. I was also thinking of adding out of the box biblatex support for org-bibtex (see my previous post). Let me know if you might be interested in either of these, as I will try to work on them this week. All best, Leonard -- Julian Mariano Burgos, PhD Hafrannsóknastofnun/Marine Research Institute Skúlagata 4, 121 Reykjavík, Iceland Sími/Telephone : +354-5752037 Bréfsími/Telefax: +354-5752001 Netfang/Email: jul...@hafro.is
Re: [O] State of the art in citations
Thanks Clément and everybody else for their comments/ideas. I will go
through these carefully.
John Kitchin writes:
It seems there are a lot of variants of citation handling out there! I will
add to the list my own variants here:
https://github.com/jkitchin/jmax/blob/master/jorg-bib.el. My citation needs
are simple, I basically only use \cite{key1,key2} in LaTeX. And I only use
bibtex, because I have not gotten around to anything else, bibtex works
fine if your needs are simple (like mine).
There is certainly duplication of some things, but the following are
features in mine that I am not aware of anywhere else.
1. Integration with reftex. You type C-c ] and select keys from reftex and
insert a cite link. If you type it again on a citation, the new entries are
appended to the end. This current conversation inspired me to implement
this!
2. Clickable cite links. If you have a citation link like
cite:key1,key2,key3 you can click on key1 and open the bibliography file to
key1, and you can click on key2 and have it open at key 2. This link would
export in latex as \cite{key1,key2,key3}. Other cite formats, e.g. citep,
citep*, etc... are defined too, but are relatively untested. You can also
use completion to enter a bibtex key.
3. citation tooltips. If clicking is too disruptive, you can run a command
and get a tooltip of the citation under point. If clicking is too tiring,
you can turn on an idle timer that shows a tooltip if the cursor is on a
citation.
4. clickable label links. clicking checks the buffer for another label by
the same name.
5. Clickable ref links. Clicking on the ref:label takes you to the label,
and provides C-c to get back to that point. You can also use completion
to get a list of labels in the buffer to make a ref to.
6. A bibliographystyle and bibliography link. The bibliography link opens
the bibtex file that was clicked on.
7. Code to make a clickable list of figures and tables.
8. Code to extract the bibtex entries cited in an org-file to a text block
at the end of the org-file
9. variables to point to a notes file and pdf directory, and functions to
jump to your notes and the pdf file from a bibtex entry.
10. a function to build a complete pdf bibliography from your bibtex file.
This is handy for checking the entries are spelled correctly, etc...
11. A little function and python script to upload a bibtex entry to
citeulike.
I have not tried to do much with anything but LaTeX, so these links are not
likely to be that good for html or odt I suspect.
Anyway, there are some very interesting ideas in this code, and I am using
it on a pretty regular basis. Maybe some of you would also find them
interesting/helpful. I look forward to see this continue developing!
John
---
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Sun, Apr 27, 2014 at 12:57 PM, Clément B. clem...@inventati.org wrote:
It appears to work for multicite for me. Or at least well enough. If I
select multiple entries, I get this:
[[ref:Author1:,Author2:,Author3:][()]]
I can then easily insert the text I want into the (). It exports
properly to LaTeX as \cite{Author1:,Author2:,Author3:}.
Maybe most people multi-cite more than me, but I think it is only a bit
of extra work to add what I want in the () and then it exports properly
to LaTeX and, using the references-via-LaTeX, to ODT/HTML too!
-k.
The problem is that you can't link to a bibtex entry,
[[ref:Author1:,Author2:]] is not picked up by org search
function of `org-open-file`. And even if it was, it couldn't link
to several entries at once. So to preserve the ability to jump
quickly to a reference, I quite like the export filter approach,
which I was unaware of (thank you Thomas! ).
Clément
--
Julian Mariano Burgos, PhD
Hafrannsóknastofnun/Marine Research Institute
Skúlagata 4, 121 Reykjavík, Iceland
Sími/Telephone : +354-5752037
Bréfsími/Telefax: +354-5752001
Netfang/Email: jul...@hafro.is
Re: [O] Organizing org-mode files: Tree view
Hi Dotan, If there is a better way to organize the files, then I would love to know how the more experienced users do it. I'm using an extremely simplistic approach: just dump all the org files into one directory. The name of each org file should be concise but descriptive, e.g. Makefile.org describes Makefiles, and git.org describes git. This simplicity completely alleviates organization effort: there's nothing to organize, since there's only one directory to put the files in. At the same time, it's very accessible by means of two `helm` wrappers: - globally, C-0 runs the command helm-org-wiki (the code is below) - in org-mode, g runs the command wspecial-worf-goto (the code is at https://github.com/abo-abo/worf) It's like a two-stage personal Google: the first stage is to find an org-file, the second stage is to search within an org-file. For example, here's the sequence of key bindings when I want to look up how git bisect works, assuming that I'm in some random buffer, like `ansi-term`: C-0 gi RET g bis RET Done. Note that gi was enough to match git.org, since all my other pages don't contain gi. Same thing for bis being able to match uniquely the heading git bisect. I think that it's quite optimal that I'm able to find the topic git bisect by using only 10 key presses, which is the same as the amount of characters in git bisect. Compare this to `helm-google-suggest` (bound to C-p g): C-p g git bi RET TAB RET That's 12 key presses (10 in Emacs, 2 in Firefox). New wiki pages can be created with C-0 as well, just type in the name of the new file and hit RET. That's it, the code is below. It's very similar to `org-switchb`, except that the files need not be opened to appear in the completion list, and new files are created if there's no match. (defgroup helm-org-wiki nil Simple jump-to-org-file package. :group 'org :prefix helm-org-wiki-) (defcustom helm-org-wiki-directory ~/org/wiki/ Directory where files for `helm-org-wiki' are stored. :group 'helm-org-wiki :type 'directory) (defun helm-org-wiki-files () Return .org files in `helm-org-wiki-directory'. (let ((default-directory helm-org-wiki-directory)) (mapcar #'file-name-sans-extension (file-expand-wildcards *.org (defvar helm-source-org-wiki `((name . Projects) (candidates . helm-org-wiki-files) (action . ,(lambda (x) (find-file (expand-file-name (format %s.org x) helm-org-wiki-directory)) (defvar helm-source-org-wiki-not-found `((name . Create org-wiki) (dummy) (action . (lambda (x) (helm-switch-to-buffer (find-file (format %s/%s.org helm-org-wiki-directory x))) ;;;###autoload (defun helm-org-wiki () Select an org-file to jump to. (interactive) (helm :sources '(helm-source-org-wiki helm-source-org-wiki-not-found))) (provide 'helm-org-wiki) regards, Oleh
Re: [O] Is OrgMode really GTD compliant?
Richard Lawrence richard.lawrence at berkeley.edu writes: I am not really familiar with the official GTD methodology, and I don't know exactly how you would normally represent the energy needed associated with a task, but here's a suggestion. It occurs to me that you could just use the A/B/C priority cookies to represent energy levels, since you don't want to use them to encode priorities. Something like: #A: need to be fresh #C: can be wasted #B: everything else or whatever would work for you. If that's granular enough to represent your energy-needed levels, then it's a neat hack that requires zero customization. Sorting and filtering by energy needed is then already built into the agenda functions, etc. Just think energy needed whenever Org says priority (which isn't very often), and you're good to go. That's exactly what I've been doing so far. But that's not that convenient. The energy level appears in front of the action headline. This adds noise to the real action info. I think I'll have to make the Energy Level an orgmode property that appears in the :PROPERTIES: drawer of the action. I'm not used to defining new properties in orgmode. I'll try to define an Energy property as well as functions like org-agenda-cmp-user-defined in order to correctly use org-agenda-sorting-strategy, unless someone has already done so... --
[O] org-babel-lilypond newbie
I'm a new Lilypond user (and a beginning but dedicated Emacs user), trying to decide whether to use Frescobaldi or the org based Arrange Mode. I think I've got Arrange Mode running, but can't seem to get the tangle command to work. I opened a .ly file I made in Frescobaldi, put point at the top, and run M-x ly-tangle. The message returned is Tangled 0 code blocks from file-ly.ly. I'm running org 8.2.6, and have evince installed on my system (though I haven't told org anything about that, specifically). Thank you! steven arntson
[O] struggle with using variable org-agenda-*-filter* properly
I am often having difficulties with the various org-agenda filter settings, for creating org-agenda-custom-commands. There is not much documentation, especially, examples for those new to for instance regexp, and Emacs' regexp, and how these work with org's syntax. In the following agenda-custom-command, I tried to use regexp in regexp-filter and tag-filter, but could not succeed. I did successfully get the skip-function to work, but I was hoping to clarify if I should expect the other variables to work, now or in the future, and/or if you could help me understand how to use them properly. (org-add-agenda-custom-command '(h habits agenda ((org-agenda-files '(/e/org/agendas-main.org)) (org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp :STYLE:.+habit)) (org-agenda-span 'day) ;; (org-agenda-regexp-filter-preset '(:STYLE:.+habit)) ;; (org-agenda-tag-filter-preset '(+STYLE=\habit\)) ) )) I have tried various permutations of the syntax, but could not make the latter two variables work. Leads: - http://orgmode.org/manual/Matching-tags-and-properties.html - which links to, http://orgmode.org/manual/Special-agenda-views.html#x-agenda-skip-entry-regexp, perhaps the intended solution at this time - http://orgmode.org/worg/org-tutorials/advanced-searching.html - http://www.emacswiki.org/emacs/RegularExpression Thank you, Brady
Re: [O] Emphasis in title export
Hi Will, The example works fine for me. It seems like the most likely cause of your issue is your export settings. One thing that you might try is to add this to the top of your file. #+Options: *:t If you already have an options section on your file you may want to check that you do not have *:nil anywhere in this line. If you do change it to `*:t as in the example above. You might also want to check that you have not set `org-export-with-emphasis' to nil anywhere in your init file. More info on configuring export settings can be found here: http://orgmode.org/manual/Export-settings.html Hope this helps! All best, Leonard On 28 April 2014 15:17, William Kunkel w...@wkunkel.com wrote: I have a title in which I need to have some text in italics. I tried this: #+TITLE: Analysis of Sartre's /No Exit/ But the slashes were just exported literally, instead of italicizing. This seemed like a pretty basic problem, but I've been unable to find anything about it via Google or in the list archives. Is there a simple solution? Thanks, Will
Re: [O] struggle with using variable org-agenda-*-filter* properly
On 4/28/2014 2:58 PM, Brady Trainor wrote: Maybe I should have included version: Org-mode version 8.2.6 (8.2.6-6-gfc37d1-elpa @ c:/Users/user-name/AppData/Roaming/.emacs.d/elpa/org-20140428/)
Re: [O] Emphasis in title export
I played around with it for a little bit and now the export is working fine. I'm not sure exactly what I changed, but it's working as intended now. Thanks, Will On Mon, Apr 28, 2014 at 6:10 PM, Leonard Randall leonard.a.rand...@gmail.com wrote: Hi Will, The example works fine for me. It seems like the most likely cause of your issue is your export settings. One thing that you might try is to add this to the top of your file. #+Options: *:t If you already have an options section on your file you may want to check that you do not have *:nil anywhere in this line. If you do change it to `*:t as in the example above. You might also want to check that you have not set `org-export-with-emphasis' to nil anywhere in your init file. More info on configuring export settings can be found here: http://orgmode.org/manual/Export-settings.html Hope this helps! All best, Leonard On 28 April 2014 15:17, William Kunkel w...@wkunkel.com wrote: I have a title in which I need to have some text in italics. I tried this: #+TITLE: Analysis of Sartre's /No Exit/ But the slashes were just exported literally, instead of italicizing. This seemed like a pretty basic problem, but I've been unable to find anything about it via Google or in the list archives. Is there a simple solution? Thanks, Will
Re: [O] setting left margin in PDF output of ORG file
On Mon, Apr 28, 2014 at 8:58 AM, Michael Strey mst...@strey.biz wrote: On 2014-04-25, John Hendy wrote: I have to ask: is whatever was once considered the golden ratio for text-to-whitespace in printed material, or even used by Gutenberg himself for proper typesetting considered relevant/best practice today? Yes, at least partly. Verachtet mir die alten Meister nicht! (Do not condemn the old masters!) -- Richard Wagner Fair enough, but let's not forget that the old masters of the medical profession around that time were practicing bloodletting. Default Org - LaTeX article looks *ugly as all hell* to me. Check the Komascript classes. Other than theoretical principle, is there evidence that readers prefer the look of the default LaTeX article sizing? Beyond all aesthetic meanings, there are some practical aspects that are valid for all presentations of text to readers. The most important rule is that the number of characters per line shall not exceed 70. Together with the chosen font, its size, and tracking, this rule defines the width of the type area. Together with the interlinear space, this rule is relevant for the readability. The longer the line, the larger (but not to large!) the interlinear space. This is more what I was looking for, especially if there have been some studies on something like reading speed, comprehension, or perhaps some quantifiable measure of eye fatigue. After you wrote this, I definitely recognize that almost every journal, magazine, and newspaper article is in column format. I don't work in academia or write journal articles, but I do work at a very large technology company (manufacturing, consumer goods, advanced materials, etc., not software) and I've never seen a column formatted internal technical report. So my comment was more about inquiring why these conventions aren't followed if they're so vastly superior. I'd have figured I'd run into at least *some* teacher/professor at some point in my life who requested/suggested/taught about the benefits of fixed character-per-line typesetting? Thus for printed papers where the most economical use of paper is important, a multi-column layout is the way to go to get the smallest margins. Also makes sense, and I hadn't thought about that -- default LaTeX just spits out an island of text some several inches in from all edges of the page, which never made sense to me (unless maybe I was writing a book, as that's the sort of look in connotes). John -- Michael Strey www.strey.biz
Re: [O] setting left margin in PDF output of ORG file
On Mon, Apr 28, 2014 at 8:58 AM, Michael Strey mst...@strey.biz wrote: On 2014-04-25, John Hendy wrote: [snip] Default Org - LaTeX article looks *ugly as all hell* to me. Check the Komascript classes. Missed this point. I've dabbled with them a little, but will have to take another look as they come up quite a bit. The point made above was: Please read http://en.wikipedia.org/wiki/Canons_of_page_construction before changing anything in the layout of margins. The typical LaTeX classes are made thorougly with those classic rules of page construction in mind. So I took the most typical LaTeX class to be the default one used, article. I'd expect the most common LaTeX class to truly represent the pinnacle of typesetting glory ;) Other than font, if Koma changes geometry/borders... I'm thinking that the article class must either 1) not embody the classic rules that well or 2) the classic rules aren't very aesthetically pleasing after all. John
Re: [O] setting left margin in PDF output of ORG file
John Hendy jw.he...@gmail.com writes: I'm thinking that the article class must either 1) not embody the classic rules that well or 2) the classic rules aren't very aesthetically pleasing after all. or 3) the classic rules are variable and flexible. Here is a quote from the Koma script manual: Many LATEX classes, including the standard classes, present the user with the largely fixed configuration of margins and typearea. With the standard classes, the configuration determined is very much dependent on the chosen font size. There are separate packages, such as geometry (see [Ume00]), which give the user complete control, but also full responsibility, of the settings of typearea and margins. KOMA-Script takes a somewhat different approach with its typearea package. Here the user is given several construction setting and automatization possibilities based on established typography standards in order to help guide him or her in making a good choice. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] org-bbdb link completion fix
Nicolas Goaziou n.goaz...@gmail.com writes: Hello, Eric Abrahamsen e...@ericabrahamsen.net writes: The most recent versions of BBDB return single records from `bbdb-completing-read-record'. That currently breaks completion on bbdb: links -- possibly earlier versions of BBDB always returned list values. We should probably check for this in `org-bbdb-complete-link', I propose the attached patch. Thank you for the patch. Would you mind providing a proper commit message and send it again? Yup, sorry about that. Hey, on this subject... How do you all handle these situations with one-time commits being sent to the list? It's kind of a pain making the commit, then waiting for the same or equivalent commit to come back via upstream, then reverting the local commit. Does everyone use throwaway branches for this? E From 55f41f66cd51ed27c396c3e7c805d83d894eb987 Mon Sep 17 00:00:00 2001 From: Eric Abrahamsen e...@ericabrahamsen.net Date: Tue, 29 Apr 2014 08:59:13 +0800 Subject: [PATCH] Fix BBDB link completion lisp/org-bbdb.el: org-bbdb-complete-link Newer versions of BBDB seem to be returning atomic values from `bbdb-completing-read-record', we should be prepared for both atoms and lists. --- lisp/org-bbdb.el | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/lisp/org-bbdb.el b/lisp/org-bbdb.el index b9841a6..cfd5b3b 100644 --- a/lisp/org-bbdb.el +++ b/lisp/org-bbdb.el @@ -400,8 +400,11 @@ This is used by Org to re-create the anniversary hash table. (defun org-bbdb-complete-link () Read a bbdb link with name completion. (require 'bbdb-com) - (concat bbdb: - (bbdb-record-name (car (bbdb-completing-read-record Name: ) + (let ((rec (bbdb-completing-read-record Name: ))) +(concat bbdb: + (bbdb-record-name (if (listp rec) + (car rec) +rec) (defun org-bbdb-anniv-export-ical () Extract anniversaries from BBDB and convert them to icalendar format. -- 1.9.2
[O] more from org-babel newbie
I'm trying to get going with org-babel and lilypond music markup. I have the system basically functioning, but there's an elementary issue I can't seem to wrap my brain around. The reason I'm excited to use org with lilypond files is the foldable headers *, **, *** etc, as well as drawers and tables. However, that's available only in an org-mode buffer, and I'm also wanting to use lilypond-mode, which gives excellent colored markup and indentation. How do I get the advantages of both? Or is that not even what I should be after? I may be fundamentally missing what's potentially useful about all of this for my musical use case! Thank you, Steven Arntson
Re: [O] more from org-babel newbie
Aloha Steven, Steven Arntson ste...@stevenarntson.com writes: The reason I'm excited to use org with lilypond files is the foldable headers *, **, *** etc, as well as drawers and tables. However, that's available only in an org-mode buffer, and I'm also wanting to use lilypond-mode, which gives excellent colored markup and indentation. How do I get the advantages of both? Or is that not even what I should be after? I may be fundamentally missing what's potentially useful about all of this for my musical use case! I haven't used babel for lilypond, but the usual way to edit a source code block in the emacs mode for the language is to press C-c ' in the source code block. hth, Tom -- Thomas S. Dye http://www.tsdye.com
[O] org-store-link dired and files with spaces
Hi everyone, I'm having an issue with storing links to files with spaces in their names. If I visit a dired buffer, use c-c l to store the link of the file under point and then in an org buffer c-c c-l to insert it. I find that the file can not be opened from within the org buffer as org appears to not recognize spaces in the file name and only sees the filename as the part up until the first space. An example of a link that does not work: [[file:resumes/Sandeep%20Salwan%20Satellite%20network%20engineer%20Cover%20Letter.doc][file:resumes/Sandeep Salwan Satellite network engineer Cover Letter.doc]] I don't quite understand why the first part of the link (the description) is url encoded but not the latter part? Kind regards Bart -- Bart Bunting
Re: [O] more from org-babel newbie
t...@tsdye.com (Thomas S. Dye) writes: Aloha Steven, Steven Arntson ste...@stevenarntson.com writes: The reason I'm excited to use org with lilypond files is the foldable headers *, **, *** etc, as well as drawers and tables. However, that's available only in an org-mode buffer, and I'm also wanting to use lilypond-mode, which gives excellent colored markup and indentation. How do I get the advantages of both? Or is that not even what I should be after? I may be fundamentally missing what's potentially useful about all of this for my musical use case! I haven't used babel for lilypond, but the usual way to edit a source code block in the emacs mode for the language is to press C-c ' in the source code block. hth, Tom This is embarrassing ... I'd tried that and hadn't managed to get it to work, and now I realize I was using C-c ` and not C-c '. The devil is in the details. I'm still a little mystified about using org markup in the context of the lilypond file, but maybe now I can do a little more experimenting. Thank you! Steven
Re: [O] more from org-babel newbie
Steven Arntson ste...@stevenarntson.com writes: I'm still a little mystified about using org markup in the context of the lilypond file, but maybe now I can do a little more experimenting. Have you seen this? http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html There are some example org-mode files there that might help you on your way. hth, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] setting left margin in PDF output of ORG file
On Mon, Apr 28, 2014 at 7:06 PM, Thomas S. Dye t...@tsdye.com wrote: John Hendy jw.he...@gmail.com writes: I'm thinking that the article class must either 1) not embody the classic rules that well or 2) the classic rules aren't very aesthetically pleasing after all. or 3) the classic rules are variable and flexible. I love out-of-the-box thinking :) Here is a quote from the Koma script manual: Many LATEX classes, including the standard classes, present the user with the largely fixed configuration of margins and typearea. With the standard classes, the configuration determined is very much dependent on the chosen font size. There are separate packages, such as geometry (see [Ume00]), which give the user complete control, but also full responsibility, of the settings of typearea and margins. KOMA-Script takes a somewhat different approach with its typearea package. Here the user is given several construction setting and automatization possibilities based on established typography standards in order to help guide him or her in making a good choice. Interesting quote! You've sold me on Michael's original suggestion and I'll be checking out Koma more closely very soon. It's great timing as a semi-annual technical report at work is due from me shortly :) John All the best, Tom -- Thomas S. Dye http://www.tsdye.com
