[O] org-cycle Collapse and Expand
I find it confusing that TAB is bound to org-cycle, which cycles through 3 states. It first expands a node, then it expands leaf nodes and then it collapses the node againt. I'd like it to just expand and collapse the current node. Any way to set this in some variable?. -- Esben Stien is b0ef@e s a http://www. s tn m irc://irc. b - i . e/%23contact sip:b0ef@ e e jid:b0ef@n n
Re: [O] HowTo: Letter template method using yasnippet
Am Samstag, 7. Juli 2012, 00:35:32 schrieb Nicolas Goaziou:
> Hello,
>
> Based on your work, I've put up the attached back-end:
> org-koma-letter.el.
>
> Quoting its documentation:
>
> You will need to add an appropriate association in `org-e-latex-classes'
> in order to use the KOMA Scrlttr2 class. For example, you can use the
> following code:
>
> (add-to-list 'org-e-latex-classes
>'("my-letter"
> "\\documentclass\[%
> DIV=14,
> fontsize=12pt,
> parskip=half,
> subject=titled,
> backaddress=false,
> fromalign=left,
> fromemail=true,
> fromphone=true\]\{scrlttr2\}
> \[DEFAULT-PACKAGES]
> \[PACKAGES]
> \[EXTRA]"
> ("\\section\{%s\}" . "\\section*\{%s\}")
> ("\\subsection\{%s\}" . "\\subsection*\{%s\}")
> ("\\subsubsection\{%s\}" . "\\subsubsection*\{%s\}")))
>
> Then, in your Org document, be sure to require the proper class with :
>
>#+LATEX_CLASS: my-letter
>
> In this back-end, headlines are ignored during export.
> --8<---cut here---end--->8---
>
This is very usefull, scrlttr2 is being used much. Thank you very much!
To avoid misunderstandings: Letter classes do not support headlines out of the
box, but the author of KOMAscript, Markus Kohm, offers files to customize
scrlttr2, among those is »sections.lco«, see here:
http://www.komascript.de/sections.lco
This file adds headings from section down to paragraph, but does not support a
table of contents. The counters have been adapted to a German lawyers needs,
starting with "A." (section), "I." (subsections), "1." (subsubsection) and
"a)" (paragraph), but this can be customized in sections.lco.
So we can use headings in scrlttr2. As the page about sections.lco got nearly
10.000 hits during the last years, I guess many people use it for business
letters including headlines.
At least I do, which leads to my plea to amend org-koma-letter.el to export
headlines.
> It's far from being complete. See it as a proof of concept. Feel free to
> upgrade it.
Just in case someone has a rainy sunday as well . . .
Regards,
Alexander
[O] using variables defined by org mode table in R leads to invalid function error on remote host
Hi, adding to this question: http://lists.gnu.org/archive/html/emacs-orgmode/2012-06/msg00677.html I have the following problem. If I define a table in an .org file and then try to use it in R as a variable, it's no problem on the local host. However, remotely I get the error: Invalid function: with-parsed-tramp-file-name The following code lines are sort of a minmal example for the behavior: (leave the first line away for local execution) #+PROPERTY: dir /foo@bar://home/user #+TBLNAME: genes | names | || | ENSMUSG031 | | ENSMUSG0063856 | | ENSMUSG0006056 | #+BEGIN_SRC R :session :var genes=genes print(genes[,1]) #+END_SRC Any ideas? Thanks a lot, Johannes
Re: [O] Org/LaTeX set-up for business letters?
Hi all, Thorsten Jolitz wrote: > Vikas Rawal writes: >>> > [1] Off the top of the head I recall a package called `scrlttr'. >>> >>> Yes, part of KOMA (?), but thats rather low level if you have to design >>> your own letters - and who knows all that stuff about professional letter >>> design?. I tried that once and the result was ugly, there is a lot of >>> extra work necesary to make it look fancy and modern. >> >> May be relevant to look at this thread from the list: >> >> http://comments.gmane.org/gmane.emacs.orgmode/29926 > > So package 'isodoc' seems to be another (maybe simpler?) option. However, > the thread proves again that it is not trivial to do-it-yourself. but there > are quite a lot of options, it seems. This is still the solution I'm using -- however, not often sending postal mails... The only drawback there is that we need to tangle the buffer, and C-c C-c the resulting LaTeX file in AUCTeX mode to get the PDF. IIRC, Eric planed to look at the problem so that we could stay in Org for making the whole loop. Best regards, Seb -- Sebastien Vauban
Re: [O] Exporting to groff, now in org-export.el ...
suvayu ali writes: >> suvayu ali writes: >> Yes there is a reason. > > Ah, so it's a legacy reason. It is always great to learn about history. > :) Maybe this information would be worth mentioning in the future > documentation for the groff exporter. Yeah, I would say it is more of an implementation reason, but legcy will do as well. :). I tried the same with the MOM and MS macros, same results. Table of content command needs to be placed at the end of the file and it will be printed at the end. I'm aware that documentation is lacking, but this code is still in quite active development. I have been making comments relevants as I go by through the code. Today is my last day of holidays though; the rate of development will slow down. (at least my wife's cousins are gone... ) -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] HowTo: Letter template method using yasnippet
Hello, AW writes: > At least I do, which leads to my plea to amend org-koma-letter.el to export > headlines. Just remove the line: (headline . org-koma-letter-headline) in the file (and `org-koma-letter-headline' function if you want to) If you don't want to reload emacs in order to take changes into account, you'll have to: M-: (makunbound 'org-koma-letter-translate-alist) and eval buffer again. Regards, -- Nicolas Goaziou
Re: [O] using variables defined by org mode table in R leads to invalid function error on remote host
Johannes Meisig writes: > Hi, > > adding to this question: > > http://lists.gnu.org/archive/html/emacs-orgmode/2012-06/msg00677.html > > I have the following problem. If I define a table in an .org file and > then try to use it in R as a variable, it's no problem on the local > host. However, remotely I get the error: > > Invalid function: with-parsed-tramp-file-name > On my system that function is provided by tramp.el, so maybe adding (require 'tramp) to your .emacs will solve this problem. Best, > > The following code lines are sort of a minmal example for the >behavior: > (leave the first line away for local execution) > > #+PROPERTY: dir /foo@bar://home/user > > #+TBLNAME: genes > | names | > || > | ENSMUSG031 | > | ENSMUSG0063856 | > | ENSMUSG0006056 | > > > #+BEGIN_SRC R :session :var genes=genes > print(genes[,1]) > #+END_SRC > > Any ideas? Thanks a lot, > > Johannes > -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Exporting to groff, now in org-export.el ...
On Sun, Jul 08, 2012 at 09:14:14AM -0400, Luis Anaya wrote: > suvayu ali writes: > > :) Maybe this information would be worth mentioning in the future > > documentation for the groff exporter. > [...] > I'm aware that documentation is lacking, but this code is still in quite > active development. I have been making comments relevants as I go by > through the code. > I didn't mean now. :-p I meant when this backend gets included in org core (not contrib, as org-export is now), it might be worthwhile comment for the info manual. Just something keep in mind for the future. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] HowTo: Letter template method using yasnippet
Am Sonntag, 8. Juli 2012, 15:34:33 schrieb Nicolas Goaziou: > Hello, > > AW writes: > > At least I do, which leads to my plea to amend org-koma-letter.el to > > export > > headlines. > > Just remove the line: > > (headline . org-koma-letter-headline) > > in the file (and `org-koma-letter-headline' function if you want to) > > If you don't want to reload emacs in order to take changes into account, > you'll have to: > > M-: (makunbound 'org-koma-letter-translate-alist) > > and eval buffer again. Thank you again! I'm gonna test during the next week and will report. Regards, Alexander
Re: [O] Output of R babel blocks with quotes is mangled/truncated
Viktor Rosenfeld writes: > Hi, > > if a value outputted by R in a Babel block contains quotes only the > quoted parted is exported. > Try #+begin_src R :results verbatim q = 'cat="S"' q #+end_src > Consider this: > > #+BEGIN_SRC R > q = 'cat="S"' > q > #+END_SRC > > #+RESULTS: > : S > > The expected result would be entire string, i.e. 'cat="S"' (without > single quotes). Is there a workaround? I've tried escaping with > backslashes to no avail. > > Cheers, > Viktor > > -- Charles C. BerryDept of Family/Preventive Medicine cberry at ucsd edu UC San Diego http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
[O] Exporting to FreeMind - opened in FreeMind failed
Hi, I have installed GNU Emacs 23.4.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.10) of 2012-04-07 on trouble, modified by Debian installed from Debian repository, and FreeMind Version 0.9.0 installed from Debian repository. In Emacs Org-mode I export a tree by running C-c C-e m and try open the exported file.mm in FreeMind but get error message: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: Element type "br" must be followed by either attribute specifications, ">" or "/>". What is the problem here? Is this an Org-mode, or FreeMind bug, or both? -- Regards from Pal
Re: [O] Showing or going to previous entry from agenda view
Hi Karl, pretty much the same for me. org-reveal says ... With optional argument SIBLINGS, on each level of the hierarchy all siblings are shown. This repairs the tree structure to what it would look like when opened with hierarchical calls to `org-cycle'. With double optional argument C-u C-u, go to the parent and show the entire tree. I admit my elisp is not strong enough to bind this to one key, but it seems like the thing you're asking for. Well hidden though. For me it works btw. Cheers, Simon On 06/28/2012 04:10 PM, Karl Voit wrote: * Bernt Hansen wrote: Karl Voit writes: C-c C-p (outline-previous-visible-heading) jumps from «Meeting 3» directly to the previous *visible* heading «Person X» and not to «Meeting 2». C-c C-r should call org-reveal which will show the preceeding hidden headline, then you can use C-c C-p normally. Hm, at my side, org-reveal does not show me the items above. In fact, org-reveal does not seem to have any effect at all :-O
Re: [O] using variables defined by org mode table in R leads to invalid function error on remote host
Hi Eric, No, (require 'tramp) doesn't solve the problem. However, commenting out (declare-function with-parsed-tramp-file-name "tramp" (filename var &rest body)) in ob.el does the job. However, this can hardly be the solution (Also, it doesn't get rid of the error message in the minibuffer). Johannes On 07/08/2012 03:37 PM, Eric Schulte wrote: Johannes Meisig writes: Hi, adding to this question: http://lists.gnu.org/archive/html/emacs-orgmode/2012-06/msg00677.html I have the following problem. If I define a table in an .org file and then try to use it in R as a variable, it's no problem on the local host. However, remotely I get the error: Invalid function: with-parsed-tramp-file-name On my system that function is provided by tramp.el, so maybe adding (require 'tramp) to your .emacs will solve this problem. Best, The following code lines are sort of a minmal example for the behavior: (leave the first line away for local execution) #+PROPERTY: dir /foo@bar://home/user #+TBLNAME: genes | names | || | ENSMUSG031 | | ENSMUSG0063856 | | ENSMUSG0006056 | #+BEGIN_SRC R :session :var genes=genes print(genes[,1]) #+END_SRC Any ideas? Thanks a lot, Johannes
Re: [O] Exporting to groff, now in org-export.el
Hi: I added the ability to modify positioning for EPS images. It maps to the parameters for .PSPIC calls. It only works with EPS images being that groff PIC images are self contained. Source: http://ppl.ug/v-RtLdtfM2E/ PDF Output: http://ppl.ug/wbx7AVcI_Ak/ Tables might take some doing, but that'll be the next thing to work on. -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] Output of R babel blocks with quotes is mangled/truncated
Hi Charles,
cbe...@tajo.ucsd.edu wrote:
> Viktor Rosenfeld writes:
>
> > Hi,
> >
> > if a value outputted by R in a Babel block contains quotes only the
> > quoted parted is exported.
> >
>
> Try
>
> #+begin_src R :results verbatim
> q = 'cat="S"'
> q
>
> #+end_src
This is not a solution since I want to output vectors or data frames
from R as a table.
E.g. the following should return a table, but verbatim returns a quoted
block which I cannot use further in my processing:
#+NAME: quote-mangling
#+BEGIN_SRC R
q = c('cat="S"', 'pos="VVFIN"')
q
#+END_SRC
I also tried an extra newline at the end, but it makes no difference.
Cheers,
Viktor
>
> > Consider this:
> >
> > #+BEGIN_SRC R
> > q = 'cat="S"'
> > q
> > #+END_SRC
> >
> > #+RESULTS:
> > : S
> >
> > The expected result would be entire string, i.e. 'cat="S"' (without
> > single quotes). Is there a workaround? I've tried escaping with
> > backslashes to no avail.
> >
> > Cheers,
> > Viktor
> >
> >
>
> --
> Charles C. BerryDept of Family/Preventive Medicine
> cberry at ucsd eduUC San Diego
> http://famprevmed.ucsd.edu/faculty/cberry/ La Jolla, San Diego 92093-0901
>
>
[O] org-export-select-tags
I have an org-file with many headlines of various levels, but no tags. I tagged one top-level headline with :export: and exported to LaTeX with C-c C-e l. The tagged headline and everything below it was exported, but so was the first headline (and everything below it) in the org file, even though it did not have any tags. The *only* tag is :exported: on the headline I want exported.
[O] org-remember from anywhere
Hi there,
I've been enjoying org-mode for a good few months now and I love it.
I'm using the following versions in both Ubuntu 10.04 on my desktop
and 12.04 on my laptop.
#+BEGIN_SRC lisp
(org-version)
Org-mode version 7.8.11
"Org-mode version 7.8.11"
(emacs-version)
"GNU Emacs 24.1.50.1 (i486-pc-linux-gnu, GTK+ Version 2.20.1)
of 2012-05-25 on muntries, modified by Debian"
#+END_SRC
I've recently started using org-remember/capture and its working well
although I found the presence of org-remember and org-capture
confusing.
I have been trying to get the capture working from anywhere using
[[http://orgmode.org/worg/org-contrib/org-protocol.html][this guide]]
so that it drops the captured note into my misc journal. It works fine
when I'm in emacs (which is about 50% of my working time). Here is my
setup:
#+BEGIN_SRC lisp
;;; Capture setup
(org-remember-insinuate)
(setq org-directory "~/notes/")
(setq org-default-notes-file (concat org-directory "misc.org"))
(setq org-remember-default-headline "Incoming")
(define-key global-map "\C-cr" 'org-remember)
(setq org-remember-templates
'(("Todo" ?t "* TODO %^{Title} %u\n%?\n%i\n%a\n")))
;;; Capture from anywhere
(require 'org-protocol)
(defun org-protocol-capture (data)
;; Capture (ignore data for now)
(org-remember))
(add-to-list 'org-protocol-protocol-alist
'("Remember"
:protocol "my-org-capture"
:function org-protocol-capture))
#+END_SRC
(start-server) is called earlier in the setup.
I intend to stick the command line invokation onto a hot key
combination so I can enter emacs notes from anywhere.
(orb-protocol-capture) works in emacs but when I try the command line
I get this:
#+BEGIN_SRC sh
~ $ emacsclient org-protocol://org-capture//
Waiting for Emacs...
\*ERROR*: Wrong type argument: stringp, org-capture
~ $ emacsclient org-protocol://org-capture//foo
Waiting for Emacs...
\*ERROR*: Wrong type argument: stringp, org-capture
#+END_SRC
What am I doing wrong?
Feel free to point me at the right manual or guide. From the notes it
looked like this feature might once have been built in.
Regards,
Paul Whipp
Office: 07 3103 2894
Mobile: 0410 545 357
Do more business with your website!
Joomla, Python, PHP and MySQL web application developer
PS: I usually export the org as html but for some reason the above
headed section just did nothing. A separate issue I'll look into
sometime but if anyone knows the answer I'd be grateful.
[O] Org Properties and tab completion issues
Using the example in the Org Manual doesn't seem to work although I am new to
emacs and org mode so maybe i'm not grasping the concept.
I set org-use-inheritance to true, I saved the file and loaded it fresh and
tried C-c C-c on the #+PROPERTY line to refresh local setup.
Problems:
1. If the property is not yet used on an entry, tab completion only shows
"property_ALL" instead of "property", and of course there is no completion on
possible values.
2. inherited properties - Where is the GENRES property and the inheritance?
3. Is there a way to display only some of the STANDARD properties along with my
custom properties in the completion buffer?
See sample org file below:
Use case - i am trying to manage my contacts and want to predefine about 30
properties and their allowed values before using them. I want to use COLUMN
view to look through 1,000's of contacts and possibly sort them by different
criteria depending on task at hand. I will use agenda to manage TODOs and
SCHEDULED. By setting a UUID for each top -level entry (a person) then
possibly write some functions (providing a database -like functionality). I
need this to work across Windows, Mac Leopard & Lion, Centos, and OpenSuse,
along with syncing some contact info to iPhone & iPad, all whether I'm online
or offline (in the field). I will use svn or git to keep things current on the
desktop/laptop platforms.
#+PROPERTY: NDisks_ALL 1 2 3 4
* CD collection
:PROPERTIES:
:Publisher_ALL: "Deutsche Grammophon" Philips EMI
:END:
** Classic
:PROPERTIES:
:GENRES: Classic
:END:
*** Goldberg Variations
:PROPERTIES:
:Title:Goldberg Variations
:Artist: Glen Gould
:Composer: J.S. Bach
:Publisher: Deutsche Grammophon
:NDisks:1
:GENRES+: Baroque
:END:
#+begin_src emacs-lisp :results output
(print (version))
(print org-use-property-inheritance)
(print (org-entry-properties nil ))
#+end_src
#+RESULTS:
:
: "GNU Emacs 24.1.1 (x86_64-apple-darwin11.3.0, NS apple-appkit-1138.32)
: of 2012-06-15 on gamma.local"
:
: t
:
: (("FILE" . "/Users/davidcoate/gtd/temp.org") ("BLOCKED" . "") ("Title" .
"Goldberg Variations") ("Artist" . "Glen Gould") ("Composer" . "J.S. Bach")
("Publisher" . "Deutsche Grammophon") ("NDisks" . "1") ("CATEGORY" . "temp"))
David Coate
Broker Associate
"Coate Connection"
www.CoateConnection.com
Re/Max Paradise
www.AlabamaParadise.com
Licensed in AL and FL
23525 Perdido Beach Blvd.
Orange Beach, Al 36561
251-213-8811 cell
251-948- fax
1-800-339-2836 direct toll free
Re: [O] Exporting to groff, now in org-export.el ...
Hi: Ok, got global table control coded. I still need to figure out how to perform column control. Source: http://ppl.ug/H8mbZtyn7AQ/ PDF Output: http://ppl.ug/tvl9DIWIABo/ Now off to put the recyclables on the curb for collection. -- Luis Anaya papo anaya aroba hot mail punto com "Do not use 100 words if you can say it in 10" - Yamamoto Tsunetomo
Re: [O] org-export-select-tags
SW wrote: > I have an org-file with many headlines of various levels, but no tags. I > tagged > one top-level headline with :export: and exported to LaTeX with C-c C-e l. The > tagged headline and everything below it was exported, but so was the first > headline (and everything below it) in the org file, even though it did not > have > any tags. The *only* tag is :exported: on the headline I want exported. > > Can't reproduce it here: Org-mode version 7.8.11 (release_7.8.11-107-ga69f4b @ /home/nick/elisp/org-mode/lisp/) Tried both the old and the new exporter, exporting to ascii, latex and html of the following file: --8<---cut here---start->8--- * foo ** foo1 ** foo2 * bar :export: ** bar1 ** bar2 * baz ** baz1 --8<---cut here---end--->8--- and I only get the bar tree exported in all cases. NB: the tag should be ``:export:'', not ``:exported:'' if you are using the default settings. Nick
[O] Don't show future TODO items in the agenda
Hi, I have a bunch of TODO items, each with a timestamp, which I would like to not being displayed in the agenda if the day of their timestamp/schedule is in the future. Is there a special property that I can attach to these TODO items which achieves what I want? -- Mark
