[O] Interesting way to send notifications from emacs (OSX)
Hi Just found this blogpost [1] on how to send notifications from emacs without growl - might be useful for reminders and longer running computations in babel? Cheers, Rainer Footnotes: [1] http://justinsboringpage.blogspot.fr/2014/05/sending-notifications-from-emacs.html -- 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 pgpx4SlvyIheh.pgp Description: PGP signature pgpyjliqa2qa0.pgp Description: PGP signature
Re: [O] Folding in iESS R buffer
Rainer M Krug writes:
Hi Rainer,
sorry for the late reply, I was offline some time.
> I have modified the variable transfer in ob-R.el so that the variable
> transfer code is enclosed as can be seen below.
>
> My idea is that I can fold the R output so that the variable transfer is
> collapsed. I understand that I can use one of the org-outside-org minor
> modes [1] (presumibly utshine?) - but I can't figure out how.
>
> My questions are:
>
> 1) which enclosing should I use to fold the transfer code away?
Outshine is like Org, no enclosing, but file structuring with
(outcommented) headlines.
> 2) which minor mode should I use for this and how can I configure it?
I'm not sure if I understand. When you use ob-R.el, you work in Org
files with R source blocks, right? When do you want to fold the R output
below? When you are in org-mode or when editing source blocks in R-mode?
In the former case, Org-mode is in charge and you don't need
outshine. In the latter case, you could install outshine as described in
the docs and then add outline-minor-mode to the ESS/R mode hook, i.e.
,---
| ;; outline
| (when (require 'outline nil t)
| (add-hook 'ess-mode-hook 'outline-minor-mode)) ; is that the hook for R-mode?
|
| ;; outshine
| (when (require 'outshine nil t)
| (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
| (setq outshine-use-speed-commands t))
`---
Outshine headlines are outcommented Org headlines, i.e.
,--
| * Beginning org variable transfer
`--
becomes
,--
| ## * Beginning org variable transfer
`--
in R-mode.
The R output would become an outshine-subtree with the header above,
just like in Org-mode, possibly surrounded by other subtrees.
> --8<---cut here---start->8---
>> ##
> ## Beginning org variable transfer
> try(detach(.org_variables_), silent=TRUE)
> .org_variables_ <- new.env()
> assign( 'COLUMNS',
> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428U4A",
> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_ );
> lockBinding('COLUMNS', .org_variables_)
> assign( 'COLS_TO_EVAL',
> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428hCH",
> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_ );
> lockBinding('COLS_TO_EVAL', .org_variables_)
> assign( 'ALLSPECIES',
> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428uMN",
> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_ );
> lockBinding('ALLSPECIES', .org_variables_)
> assign( 'SPECIES',
> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-744287WT",
> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_ );
> lockBinding('SPECIES', .org_variables_)
> assign( 'YEARS',
> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428IhZ",
> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_ );
> lockBinding('YEARS', .org_variables_)
> assign('PRESENT', 2008, envir = .org_variables_); lockBinding('PRESENT',
> .org_variables_)
> assign('MINEFFORT', 3, envir = .org_variables_); lockBinding('MINEFFORT',
> .org_variables_)
> assign('PROPTRAIN', 0.6, envir = .org_variables_);
> lockBinding('PROPTRAIN', .org_variables_)
> assign('RNGSEED', 13, envir = .org_variables_); lockBinding('RNGSEED',
> .org_variables_)
> assign('RNGKIND', "Mersenne-Twister", envir = .org_variables_);
> lockBinding('RNGKIND', .org_variables_)
> assign('RNGNORMALKIND', "Inversion", envir = .org_variables_);
> lockBinding('RNGNORMALKIND', .org_variables_)
> assign('REFGRID', "./refGrid_8km.rds", envir = .org_variables_);
> lockBinding('REFGRID', .org_variables_)
> assign('IFN', "./__BOX__/IFN/DB_IFN/rds/tabplot.rds", envir =
> .org_variables_); lockBinding('IFN', .org_variables_)
> assign('IFNCOUNT',
> "./__BOX__/IFN/DB_IFN/rdsRasterized/tabplot.count.8km.rds", envir =
> .org_variables_); lockBinding('IFNCOUNT', .org_variables_)
> assign('IFNMEAN',
> "./__BOX__/IFN/DB_IFN/rdsRasterized/tabplot.mean.8km.rds", envir =
> .org_variables_); lockBinding('IFNMEAN', .org_variables_)
> assign('IFNPRES',
> "./__BOX__/IFN/DB_IFN/rdsRasterized/tabplot.pres.8km.rds", envir =
> .org_variables_); lockBinding('IFNPRES', .org_variables_)
> assign('IFNSD', "./__BOX__/IFN/DB_IFN/rdsRasterized/tabplot.sd.8km.rds",
> envir = .org_variables_); lockBinding('IFNSD', .org_variables_)
> assign('IFNTABTREE', "./__BOX__/IFN/DB_IFN/rds/tabtree.rds", envir =
> .or
Re: [O] Folding in iESS R buffer
Thorsten Jolitz writes:
> Rainer M Krug writes:
>
> Hi Rainer,
>
> sorry for the late reply, I was offline some time.
No problem.
>
>> I have modified the variable transfer in ob-R.el so that the variable
>> transfer code is enclosed as can be seen below.
>>
>> My idea is that I can fold the R output so that the variable transfer is
>> collapsed. I understand that I can use one of the org-outside-org minor
>> modes [1] (presumibly utshine?) - but I can't figure out how.
>>
>> My questions are:
>>
>> 1) which enclosing should I use to fold the transfer code away?
>
> Outshine is like Org, no enclosing, but file structuring with
> (outcommented) headlines.
So everything after the outcommented headline will be folded - so if I
only want to fold one part, I have to use
,
| ## * If this is folded
| SOME R CODE
| ## * This not anymore
| SOME R CODE
`
which I could fold to
,
| ## * If this is folded [...]
| ## * This not anymore
| SOME R CODE
`
correct?
>
>> 2) which minor mode should I use for this and how can I configure it?
>
> I'm not sure if I understand. When you use ob-R.el, you work in Org
> files with R source blocks, right?
Correct.
> When do you want to fold the R output below? When you are in org-mode
> or when editing source blocks in R-mode?
The evaluated code - not in the source code.
>
> In the former case, Org-mode is in charge and you don't need
> outshine.
True.
> In the latter case, you could install outshine as described in the
> docs and then add outline-minor-mode to the ESS/R mode hook, i.e.
That's it.
>
> ,---
> | ;; outline
> | (when (require 'outline nil t)
> | (add-hook 'ess-mode-hook 'outline-minor-mode)) ; is that the hook for
> R-mode?
> |
> | ;; outshine
> | (when (require 'outshine nil t)
> | (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
> | (setq outshine-use-speed-commands t))
> `---
>
> Outshine headlines are outcommented Org headlines, i.e.
>
> ,--
> | * Beginning org variable transfer
> `--
>
> becomes
>
> ,--
> | ## * Beginning org variable transfer
> `--
>
> in R-mode.
>
> The R output would become an outshine-subtree with the header above,
> just like in Org-mode, possibly surrounded by other subtrees.
Sounds great - thanks a lot. I will try it out,
Rainer
>
>> --8<---cut here---start->8---
>>> ##
>> ## Beginning org variable transfer
>> try(detach(.org_variables_), silent=TRUE)
>> .org_variables_ <- new.env()
>> assign( 'COLUMNS',
>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428U4A",
>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>> ); lockBinding('COLUMNS', .org_variables_)
>> assign( 'COLS_TO_EVAL',
>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428hCH",
>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>> ); lockBinding('COLS_TO_EVAL', .org_variables_)
>> assign( 'ALLSPECIES',
>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428uMN",
>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>> ); lockBinding('ALLSPECIES', .org_variables_)
>> assign( 'SPECIES',
>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-744287WT",
>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>> ); lockBinding('SPECIES', .org_variables_)
>> assign( 'YEARS',
>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428IhZ",
>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>> ); lockBinding('YEARS', .org_variables_)
>> assign('PRESENT', 2008, envir = .org_variables_); lockBinding('PRESENT',
>> .org_variables_)
>> assign('MINEFFORT', 3, envir = .org_variables_);
>> lockBinding('MINEFFORT', .org_variables_)
>> assign('PROPTRAIN', 0.6, envir = .org_variables_);
>> lockBinding('PROPTRAIN', .org_variables_)
>> assign('RNGSEED', 13, envir = .org_variables_); lockBinding('RNGSEED',
>> .org_variables_)
>> assign('RNGKIND', "Mersenne-Twister", envir = .org_variables_);
>> lockBinding('RNGKIND', .org_variables_)
>> assign('RNGNORMALKIND', "Inversion", envir = .org_variables_);
>> lockBinding('RNGNORMALKIND', .org_variables_)
>> assign('REFGRID', "./refGrid_8km.rds", envir = .org_variables_);
>> lockBinding('REFGRID', .org_variables_)
>> assign('IFN', "./__BOX__/IFN/DB_IFN/rds/tabplot.rds", envir =
>> .org_variables_); lockBinding('IFN', .org_variables_)
>> assign('IFNCOUNT',
>> "./__BOX__/IFN/DB_IFN/rds
Re: [O] Writing .el files for org in org?
Rainer M Krug writes: Hi Rainer, > But as I am struggling with elisp, I would like to put the ob-R.el file > into an org file which is then tangled into the ob-R.el file. again, this is the main use case for outshine & outorg. They work with old-school and outshine (= outcommented org-mode) headlines, so you just have to structure ob-R.el with some headlines, either like this: ,-- | ;;; Level 1 | Level 2 `-- or like this ,--- | ;; * Level 1 | ;; ** Level 2 `--- (just like you structure an Org file) and then you can switch between emacs-lisp-mode and org-mode with ,- | M-# M-# (outorg-edit-as-org) `- and ,- | M-# (outorg-copy-edits-and-exit) `- Org-mode and emacs-lisp-mode thus become two different views on the same (well-structured) file, and you can easily switch between them. -- cheers, Thorsten
Re: [O] org-edit-src-code outside of org
jorge.a.alf...@gmail.com (Jorge A. Alfaro-Murillo) writes: > Hi, I would like to use org-edit-src-code outside of org, I think it > would be very handy in Message mode, to send messages that contain code > and edit that code in the proper mode. This can be done with outshine.el and outorg.el. Install them as described in the docs and then add , | (when (require 'outline nil t) | (add-hook 'message-mode-hook 'outline-minor-mode)) | | (require 'outshine nil t) | (add-hook 'outline-minor-mode-hook 'outshine-hook-function) | | (setq outshine-use-speed-commands t) ` M-# M-# will then convert your message-mode buffer to full Org-mode, M-# will copy the changes back to message-mode. As a proof of concept, I attach this mail exported to ASCII by evaluating the following source-block directly in the outorg-edit-buffer: #+begin_src emacs-lisp (org-export-as 'ascii) #+end_src #+results: _ 745 Thorsten Jolitz _ Table of Contents _ 1 --text follows this line-- 1 --text follows this line-- jorge.a.alf...@gmail.com (Jorge A. Alfaro-Murillo) writes: > Hi, I would like to use org-edit-src-code outside of org, I think it > would be very handy in Message mode, to send messages that contain > code and edit that code in the proper mode. This can be done with outshine.el and outorg.el. Install them as described in the docs and then add , (when (require 'outline nil t) (add-hook 'message-mode-hook 'outline-minor-mode)) (require 'outshine nil t) (add-hook 'outline-minor-mode-hook 'outshine-hook-function) (setq outshine-use-speed-commands t) ` M-# M-# will then convert your message-mode buffer to full Org-mode, M-# will copy the changes back to message-mode. As a proof of concept, I attach this mail exported to ASCII. , | (org-export-as 'ascii) ` -- cheers, Thorsten -- cheers, Thorsten
Re: [O] Folding in iESS R buffer
Rainer M Krug writes:
> Thorsten Jolitz writes:
>
>> Rainer M Krug writes:
>>
>> Hi Rainer,
>>
>> sorry for the late reply, I was offline some time.
>
> No problem.
>
>>
>>> I have modified the variable transfer in ob-R.el so that the variable
>>> transfer code is enclosed as can be seen below.
>>>
>>> My idea is that I can fold the R output so that the variable transfer is
>>> collapsed. I understand that I can use one of the org-outside-org minor
>>> modes [1] (presumibly utshine?) - but I can't figure out how.
>>>
>>> My questions are:
>>>
>>> 1) which enclosing should I use to fold the transfer code away?
>>
>> Outshine is like Org, no enclosing, but file structuring with
>> (outcommented) headlines.
>
> So everything after the outcommented headline will be folded - so if I
> only want to fold one part, I have to use
>
> ,
> | ## * If this is folded
> | SOME R CODE
> | ## * This not anymore
> | SOME R CODE
> `
>
> which I could fold to
>
> ,
> | ## * If this is folded [...]
> | ## * This not anymore
> | SOME R CODE
> `
>
> correct?
I just tried it, and get the following:
Unfolded:
,
| >
| + . + ## * Variable Transfer from org
| ##
| ## org:variables environment created and in search path
| ##
|
| ## * Back to normal code
| here it is
| > >
`
where "here it is " is output
From normal R code in a source block evaluated.
Folded:
,
| >
| + . + ## * Variable Transfer from org
| ##...
| here it is
| > >
`
Is this what is expected?
Rainer
>
>>
>>> 2) which minor mode should I use for this and how can I configure it?
>>
>> I'm not sure if I understand. When you use ob-R.el, you work in Org
>> files with R source blocks, right?
>
> Correct.
>
>> When do you want to fold the R output below? When you are in org-mode
>> or when editing source blocks in R-mode?
>
> The evaluated code - not in the source code.
>
>>
>> In the former case, Org-mode is in charge and you don't need
>> outshine.
>
> True.
>
>> In the latter case, you could install outshine as described in the
>> docs and then add outline-minor-mode to the ESS/R mode hook, i.e.
>
> That's it.
>
>>
>> ,---
>> | ;; outline
>> | (when (require 'outline nil t)
>> | (add-hook 'ess-mode-hook 'outline-minor-mode)) ; is that the hook for
>> R-mode?
>> |
>> | ;; outshine
>> | (when (require 'outshine nil t)
>> | (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>> | (setq outshine-use-speed-commands t))
>> `---
>>
>> Outshine headlines are outcommented Org headlines, i.e.
>>
>> ,--
>> | * Beginning org variable transfer
>> `--
>>
>> becomes
>>
>> ,--
>> | ## * Beginning org variable transfer
>> `--
>>
>> in R-mode.
>>
>> The R output would become an outshine-subtree with the header above,
>> just like in Org-mode, possibly surrounded by other subtrees.
>
> Sounds great - thanks a lot. I will try it out,
>
> Rainer
>
>>
>>> --8<---cut here---start->8---
##
>>> ## Beginning org variable transfer
>>> try(detach(.org_variables_), silent=TRUE)
>>> .org_variables_ <- new.env()
>>> assign( 'COLUMNS',
>>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428U4A",
>>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>>> ); lockBinding('COLUMNS', .org_variables_)
>>> assign( 'COLS_TO_EVAL',
>>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428hCH",
>>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>>> ); lockBinding('COLS_TO_EVAL', .org_variables_)
>>> assign( 'ALLSPECIES',
>>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428uMN",
>>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>>> ); lockBinding('ALLSPECIES', .org_variables_)
>>> assign( 'SPECIES',
>>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-744287WT",
>>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>>> ); lockBinding('SPECIES', .org_variables_)
>>> assign( 'YEARS',
>>> read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428IhZ",
>>> header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
>>> ); lockBinding('YEARS', .org_variables_)
>>> assign('PRESENT', 2008, en
Re: [O] Writing .el files for org in org?
Hi Thorsten Thorsten Jolitz writes: > Rainer M Krug writes: > > Hi Rainer, > >> But as I am struggling with elisp, I would like to put the ob-R.el file >> into an org file which is then tangled into the ob-R.el file. > > again, this is the main use case for outshine & outorg. > > They work with old-school and outshine (= outcommented org-mode) > headlines, so you just have to structure ob-R.el with some headlines, > either like this: > > ,-- > | ;;; Level 1 > | Level 2 > `-- > > or like this > > ,--- > | ;; * Level 1 > | ;; ** Level 2 > `--- > > (just like you structure an Org file) and then you can switch between > emacs-lisp-mode and org-mode with > > ,- > | M-# M-# (outorg-edit-as-org) > `- > > and > > ,- > | M-# (outorg-copy-edits-and-exit) > `- > > Org-mode and emacs-lisp-mode thus become two different views on the same > (well-structured) file, and you can easily switch between them. I got it working - looks very nice. Definitely an option. 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 pgpE01nuAHkpO.pgp Description: PGP signature
Re: [O] [RFC] Org Minor Mode?
Bastien writes: Hi Bastien, > Thorsten Jolitz writes: > >> So I would rather have a clear picture of the 'political situation' wrt >> to org-minor-mode and some technical discussion first. But anyway, I >> will not have time to work on this again before June. > > I for one need to have a clearer picture of what such a minor mode > would really do, without getting prematurily lost in the details of > possible implementations. Its just a better and smarter outshine-mode (major-mode agnostic "Org look&feel" for programming modes). > Once we have a clear goal, let's build a small list of steps, then > submit a patch for the first step. (We can then work on a separate > branch for the whole feature, and spend months on this branch.) The goal for org-minor-mode would be the same like for outshine - give programming mode buffers the same look&feel like Org-mode buffers. This works already quite good with outshine, I structure all my elisp, picolisp, R, CSS (etc etc) files like Org files, and when I switch between them and Org-files I hardly notice a difference wrt navigation, folding, structure editing, fontification etc. But the backend for outshine is outline-(minor)-mode. Org-mode does some things better than outline-mode, and tons of things outline-mode can't do. > If the change is relying on too many external libraries, it is not > very likely to happen. It should end up as one new library (e.g. omm.el) that is part of Org-mode, replacing both orgstruct-mode and outshine. > The feature seems to bring interest, but let's refrain from spending > our enthusiasm in early and lengthy discussions that nobody can fully > follow, especially if you won't have time to hack something before > June... outshine, outorg and navi-mode are all in the mid-range of popular melpa packages, so there seems to be some real demand ... > So I really don't want to play the cold fish here, but let's move > with code and small steps rather than discussions and big goals. I started with code (https://github.com/tj64/omm), but faced the fundamental problem of hardcoded regexps (^, $, and \\*) all over the Org sources that make Org functions fail on outcommented headers and in outcommented text sections in general. The goals, ideas and even implementations (outshine, orgstruct) are already there, a first intent to merge them into one library exists (omm.el), but what to do about this core problem? -- cheers, Thorsten
Re: [O] org-contacts development
Reading http://orgmode.org/worg/dev/org-syntax.html#Node_Properties
I just realised that my clumsy property keys are against the rules since
they are containing whitespace characters.
Nevertheless I still like the idea of having a Type, a number and a
Value for every property that can occur multiple. Thus the properties
can be easily mapped to the VCard scheme as well as to any other scheme.
Thus, what I would like to propose is the following scheme:
#+BEGIN_SRC org
:PROPERTIES:
:Contact_Type: individual or organisation
:Organization_1_Type: company
:Organization_1_Name: The company name
:Organization_1_Department: department, business unit, division
:Organization_1_Title: job title of an individual
:FN: The full name
:GivenName:
:FamilyName:
:Name_Prefix:
:Name_Suffix:
:Nickname:
:Email_1_Type: Work
:Email_1_Value: n...@company.fr
:Address_1_Type: Work
:Address_1_Street: The street can contain multiple lines \\ second line
:Address_1_Box: Postal box
:Address_1_Extension: other extensions that can occur in addresses
:Address_1_City: The city
:Address_1_Region: Region, federal state etc.
:Address_1_Code: 12100
:Address_1_Country: France
:Phone_1_Type: Work
:Phone_1_Value: +33 565 623740
:Phone_2_Type: Fax
:Phone_2_Value: +33 565 623070
:Website_1_Type: Work
:Website_1_Value: http://www.domain.fr
:Birthday:
:Language: en
:Salutation:
:END:
#+END_SRC
Other user defined properties can be added and mapped to the appropriate
user defined keys during export.
Further remarks regarding my last e-mail:
> #+BEGIN: propview :id "39584cda-bff0-4b8a-9460-4fefb5b5922c" :cols (Given\
> Name Family\ Name ITEM Name\ Prefix Name\ Suffix Nickname EMAIL Phone\ 1\ -\
> Type Phone\ 1\ -\ Value Phone\ 2\ -\ Type Phone\ 2\ -\ Value Phone\ 3\ -\
> Type Phone\ 3\ -\ Value Phone\ 4\ -\ Type Phone\ 4\ -\ Value Address\ 1\ -\
> Type Address\ 1\ -\ Street Address\ 1\ -\ PO\ Box Address\ 1\ -\ Extended\
> Address Address\ 1\ -\ City Address\ 1\ -\ Region Address\ 1\ -\ Postal\ Code
> Address\ 1\ -\ Country Address\ 2\ -\ Type Address\ 2\ -\ Street Address\ 2\
> -\ PO\ Box Address\ 2\ -\ Extended\ Address Address\ 2\ -\ City Address\ 2\
> -\ Region Address\ 2\ -\ Postal\ Code Address\ 2\ -\ Country Address\ 3\ -\
> Type Address\ 3\ -\ Street Address\ 3\ -\ PO\ Box Address\ 3\ -\ Extended\
> Address Address\ 3\ -\ City Address\ 3\ -\ Region Address\ 3\ -\ Postal\ Code
> Address\ 3\ -\ Country Organization\ 1\ -\ Name Birthday Organization\ 1\ -\
> Title Organization\ 1\ -\ Department Website\ 1\ -\ Type Website\ 1\ -\ Value
> LANG TAGS) :colnames ("Given Name" "Family Name" "Name" "Name Prefix" "Name
> Suffix" "Nickname" "E-mail 1 - Value" "Phone 1 - Type" "Phone 1 - Value"
> "Phone 2 - Type" "Phone 2 - Value" "Phone 3 - Type" "Phone 3 - Value" "Phone
> 4 - Type" "Phone 4 - Value" "Address 1 - Type" "Address 1 - Street" "Address
> 1 - PO Box" "Address 1 - Extended Address" "Address 1 - City" "Address 1 -
> Region" "Address 1 - Postal Code" "Address 1 - Country" "Address 2 - Type"
> "Address 2 - Street" "Address 2 - PO Box" "Address 2 - Extended Address"
> "Address 2 - City" "Address 2 - Region" "Address 2 - Postal Code" "Address 2
> - Country" "Address 3 - Type" "Address 3 - Street" "Address 3 - PO Box"
> "Address 3 - Extended Address" "Address 3 - City" "Address 3 - Region"
> "Address 3 - Postal Code" "Address 3 - Country" "Organization 1 - Name"
> "Birthday" "Oganization 1 - Title" "Organization 1 - Department" "Website 1 -
> Type" "Website 1 - Value" "Language" "org-tags") :defaultval "" :inherit
> (TAGS) :conds ((stringp KIND)) :match "-ARCHIVE" :noquote t
Here I forgot to copy the #+END:
Please note that org-collector tries to convert property values from
strings into numbers if possible. For postal codes with leading Zeros
this can lead to unexpected results. I did not find any other way to
solve this problem than to add a national code like in the following
example
:Address_1_Code: 01169
would lead to "1169" in the propview table.
so I replaced it with
:Address_1_Code: DE-01169
--
Michael Strey
mailto:mst...@strey.biz
http://www.strey.biz
https://twitter.com/michaelstrey
Re: [O] Folding in iESS R buffer
Rainer M Krug writes:
> Rainer M Krug writes:
>
>> Thorsten Jolitz writes:
>>
>>> Rainer M Krug writes:
>>>
>>> Hi Rainer,
>>>
>>> sorry for the late reply, I was offline some time.
>>
>> No problem.
>>
>>>
I have modified the variable transfer in ob-R.el so that the variable
transfer code is enclosed as can be seen below.
My idea is that I can fold the R output so that the variable
transfer is
collapsed. I understand that I can use one of the org-outside-org minor
modes [1] (presumibly utshine?) - but I can't figure out how.
My questions are:
1) which enclosing should I use to fold the transfer code away?
>>>
>>> Outshine is like Org, no enclosing, but file structuring with
>>> (outcommented) headlines.
>>
>> So everything after the outcommented headline will be folded - so if I
>> only want to fold one part, I have to use
>>
>> ,
>> | ## * If this is folded
>> | SOME R CODE
>> | ## * This not anymore
>> | SOME R CODE
>> `
>>
>> which I could fold to
>>
>> ,
>> | ## * If this is folded [...]
>> | ## * This not anymore
>> | SOME R CODE
>> `
>>
>> correct?
>
> I just tried it, and get the following:
>
> Unfolded:
>
> ,
> | >
> | + . + ## * Variable Transfer from org
> | ##
> | ## org:variables environment created and in search path
> | ##
> |
> | ## * Back to normal code
> | here it is
> | > >
> `
>
> where "here it is " is output
> From normal R code in a source block evaluated.
>
> Folded:
>
> ,
> | >
> | + . + ## * Variable Transfer from org
> | ##...
> | here it is
> | > >
> `
>
> Is this what is expected?
no, it should look just like a folded subtree in Org-mode.
The problem is probably this
,--
| + . + ## * Variable Transfer from org
`--
because in outshine, just like in Org, a header must (!) start at the
beginning of line to be recognized.
Or is the comment syntax wrong for R-mode? Is it only
,-
| # * Level 1
`-
? I can't check right now, you can try it out by writing an Org header in an
R buffer and then call M-x comment-region on the marked line. Maybe I
got confused because PicoLisp uses ## for comments ...
2) which minor mode should I use for this and how can I configure it?
>>>
>>> I'm not sure if I understand. When you use ob-R.el, you work in Org
>>> files with R source blocks, right?
>>
>> Correct.
>>
>>> When do you want to fold the R output below? When you are in org-mode
>>> or when editing source blocks in R-mode?
>>
>> The evaluated code - not in the source code.
>>
>>>
>>> In the former case, Org-mode is in charge and you don't need
>>> outshine.
>>
>> True.
>>
>>> In the latter case, you could install outshine as described in the
>>> docs and then add outline-minor-mode to the ESS/R mode hook, i.e.
>>
>> That's it.
>>
>>>
>>> ,---
>>> | ;; outline
>>> | (when (require 'outline nil t)
>>> | (add-hook 'ess-mode-hook 'outline-minor-mode)) ; is that the
>>> | hook for R-mode?
>>> |
>>> | ;; outshine
>>> | (when (require 'outshine nil t)
>>> | (add-hook 'outline-minor-mode-hook 'outshine-hook-function)
>>> | (setq outshine-use-speed-commands t))
>>> `---
>>>
>>> Outshine headlines are outcommented Org headlines, i.e.
>>>
>>> ,--
>>> | * Beginning org variable transfer
>>> `--
>>>
>>> becomes
>>>
>>> ,--
>>> | ## * Beginning org variable transfer
>>> `--
>>>
>>> in R-mode.
>>>
>>> The R output would become an outshine-subtree with the header above,
>>> just like in Org-mode, possibly surrounded by other subtrees.
>>
>> Sounds great - thanks a lot. I will try it out,
>>
>> Rainer
>>
>>>
--8<---cut here---start->8---
> ##
## Beginning org variable transfer
try(detach(.org_variables_), silent=TRUE)
.org_variables_ <- new.env()
assign( 'COLUMNS',
read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428U4A",
header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
); lockBinding('COLUMNS', .org_variables_)
assign( 'COLS_TO_EVAL',
read.table("/var/folders/50/wcr5bjwn75q595n6x82gxj28gn/T/babel-74428N93/R-import-74428hCH",
header=TRUE, row.names=1, sep="\t", as.is=TRUE ), envir = .org_variables_
); lockBinding('COLS_TO_EVAL', .org_va
[O] Autoopen TODOs AND checkboxes?
In my "organiser" page I have a mixed bag of TODO lists and also checkbox lists. If I have at the top of the page "#+STARTUP: content" it opens just showing all of the TODO lists and none of the checkbox lists. But if I have "#+STARTUP: showall" it shows everything, including all the hidden dates on the TODOs. How can I get it to just show all the TODOs and all of the checkboxes please? I've looked at the "org manual" and I don’t think its possible, but I could be wrong. Am I? 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.3.91.1 signature.asc Description: PGP signature
[O] org-plus-contrib package upgrade fails
When upgrading my packages from elpa, org-plus-contrib is failing showing this in the messages buffer --8<---cut here---start->8--- Generating autoloads for org-eshell.el...done Generating autoloads for org-eval-light.el...done Generating autoloads for org-eval.el...done Generating autoloads for org-expiry.el...done Generating autoloads for org-faces.el...done hack-local-variables: Local variables entry is missing the suffix Saving file /home/boudiccas/.emacs.d/elpa/org-plus-contrib-20140526/org-plus-contrib-autoloads.el... Wrote /home/boudiccas/.emacs.d/elpa/org-plus-contrib-20140526/org-plus-contrib-autoloads.el --8<---cut here---end--->8--- This means that the package upgrade fails as the replaced packages are not deleted, and the whole thing stops at the generation of "org-plus-contrib-autoloads.el". If it is a failing at my end, where is "hack-local-variables" please and what should the suffix be? 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.3.91.1 signature.asc Description: PGP signature
Re: [O] Folding in iESS R buffer
Thorsten Jolitz writes: > Rainer M Krug writes: > >> Rainer M Krug writes: >> >>> Thorsten Jolitz writes: >>> Rainer M Krug writes: Hi Rainer, sorry for the late reply, I was offline some time. >>> >>> No problem. >>> > I have modified the variable transfer in ob-R.el so that the variable > transfer code is enclosed as can be seen below. > > My idea is that I can fold the R output so that the variable > transfer is > collapsed. I understand that I can use one of the org-outside-org minor > modes [1] (presumibly utshine?) - but I can't figure out how. > > My questions are: > > 1) which enclosing should I use to fold the transfer code away? Outshine is like Org, no enclosing, but file structuring with (outcommented) headlines. >>> >>> So everything after the outcommented headline will be folded - so if I >>> only want to fold one part, I have to use >>> >>> , >>> | ## * If this is folded >>> | SOME R CODE >>> | ## * This not anymore >>> | SOME R CODE >>> ` >>> >>> which I could fold to >>> >>> , >>> | ## * If this is folded [...] >>> | ## * This not anymore >>> | SOME R CODE >>> ` >>> >>> correct? >> >> I just tried it, and get the following: >> >> Unfolded: >> >> , >> | > >> | + . + ## * Variable Transfer from org >> | ## >> | ## org:variables environment created and in search path >> | ## >> | >> | ## * Back to normal code >> | here it is >> | > > >> ` >> >> where "here it is " is output >> From normal R code in a source block evaluated. >> >> Folded: >> >> , >> | > >> | + . + ## * Variable Transfer from org >> | ##... >> | here it is >> | > > >> ` >> >> Is this what is expected? > > no, it should look just like a folded subtree in Org-mode. > The problem is probably this > > ,-- > | + . + ## * Variable Transfer from org > `-- > > because in outshine, just like in Org, a header must (!) start at the > beginning of line to be recognized. I changed it in the buffer, so that it now reads: , | > | ## * Variable Transfer from org | ## | ## org:variables environment created and in search path | ## | | ## * Back to normal code | here it is | > > ` but the folding still results in , | > | ## * Variable Transfer from org | ##... | here it is | > > ` If it helps, here is the buffer: , | R version 3.1.0 (2014-04-10) -- "Spring Dance" | Copyright (C) 2014 The R Foundation for Statistical Computing | Platform: x86_64-apple-darwin13.1.0 (64-bit) | | R is free software and comes with ABSOLUTELY NO WARRANTY. | You are welcome to redistribute it under certain conditions. | Type 'license()' or 'licence()' for distribution details. | | Natural language support but running in an English locale | | R is a collaborative project with many contributors. | Type 'contributors()' for more information and | 'citation()' on how to cite R or R packages in publications. | | Type 'demo()' for some demos, 'help()' for on-line help, or | 'help.start()' for an HTML browser interface to help. | Type 'q()' to quit R. | | During startup - Warning messages: | 1: Setting LC_CTYPE failed, using "C" | 2: Setting LC_COLLATE failed, using "C" | 3: Setting LC_TIME failed, using "C" | 4: Setting LC_MESSAGES failed, using "C" | 5: Setting LC_MONETARY failed, using "C" | > > options(STERM='iESS', str.dendrogram.last="'", editor='emacsclient', show.error.locations=TRUE) | > | ## * Variable Transfer from org | ## | ## org:variables environment created and in search path | ## | | ## * Back to normal code | here it is | > > ` I figured it out: The problems are the comment lines - if I delete these, it is working. I can work around this. Cheers and thanks, Rainer > > Or is the comment syntax wrong for R-mode? Is it only > > ,- > | # * Level 1 > `- > > ? I can't check right now, you can try it out by writing an Org header in an > R buffer and then call M-x comment-region on the marked line. Maybe I > got confused because PicoLisp uses ## for comments ... > > 2) which minor mode should I use for this and how can I configure it? I'm not sure if I understand. When you use ob-R.el, y
Re: [O] New worg page: Publishing beamer slideshows and articles from one source
Hi Rasmus, Bastien, On Mon, May 26, 2014 at 05:56:38PM +0200, Rasmus wrote: > > I have attached a quick patch with a text that I think is more > accurate and that tries to explain the issue. I think the tone may be > too "academic"/dry. > > Since Suvayu put the initial effort into the answer I will wait for > his approval before submitting it. Sorry I was a bit sloppy. The origin of the hack is from LaTeX export. I did not test it extensively for other backends. Now I realise why it worked for me; I always export with no toc for html and ascii. and LaTeX takes care of toc. Your patch looks good, however I think the language is indeed too academic and could be simplified and made more accesible. It is Worg after all :). > >> To deal with the tricky part you need an additional filter. Or you > >> need a filter on the final output and you'd probably need to make some > >> accounting of what's present and what is not so that you can update > >> counters and TOCs. > > > > That's why I say it's tricky. > > > > Let's keep this constructive and move forward -- maybe that was not > > your intention, but the tone of your first email was a bit harsh. > > I'm sure Suvayu is open to suggestions on how to improve the filter. > > That was not the intention. For that I appoligize. In fact, I'm always of the opinion, if the change is minor, or corrects a mistake, or simplifies things, just go ahead with it. It is a community resource! I won't have time to work on this any time soon (now I'm at a workshop, review deadline next week, holiday the week after). Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Adding source location information when tangling
Something like " Jumping between code and Org here? http://orgmode.org/manual/Extracting-source-code.html#Extracting-source-code Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Sun, May 25, 2014 at 11:28 AM, Thomas Morgan wrote: > Dear Org hackers, > > I have a question about tangling LilyPond code blocks. > > Is there a way to put the commands `\sourcefilename' and > `\sourcefileline' in the tangled file before each block, > perhaps in place of the comment that includes the same information? > (These commands are equivalent to the `#line LINENUM "FILE"' > directive in C.) If possible I'd like to let LilyPond know how > to give error messages that refer to the originating Org file. > > Thanks, > Thomas >
Re: [O] Interesting way to send notifications from emacs (OSX)
http://melpa.milkbox.net/#/alert provides a nice abstractions across platforms, and even just GUI or no GUI. Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi g...@wisdomandwonder.com | http://www.wisdomandwonder.com/ “Wisdom begins in wonder.” --Socrates ((λ (x) (x x)) (λ (x) (x x))) “Life has become immeasurably better since I have been forced to stop taking it seriously.” --Thompson On Tue, May 27, 2014 at 2:57 AM, Rainer M Krug wrote: > Hi > > Just found this blogpost [1] on how to send notifications from emacs without > growl - might be useful for reminders and longer running computations in > babel? > > Cheers, > > Rainer > > > Footnotes: > [1] > http://justinsboringpage.blogspot.fr/2014/05/sending-notifications-from-emacs.html > > -- > 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
Re: [O] Insert calc vector directly into spreadsheet cells?
Michael, This is great. I wish I had seen this earlier. I did not know about the subscr function, but I had basically gotten to the same point by writing an equivalent custom calc function. I understand that using a calc function in a table formula is inefficient, since it is executed for every table cell. But for small tables, I think the combination of table formulas and calc functions is extremely powerful. Here are two examples of mine: 1. I wrote a custom calc function called tailsInARow that uses the calc random function to simulate a coin toss and return the number of tails in a row. I used this function to fill a 20x20 table of values. I then used the calc histogram function in a table formula to read the table values, histogram the number of tails in a row, then write the histogram to a new table. 2. I calculated a rotation matrix as a succession of individual rotations about x, y, and z axes. I then wrote the resulting matrix to a table. I then wrote a table function to read the matrix, take the inverse, and write the result to a new table. I think calc is well suited for small problems like this for which I want to have a record of what I did later. But I am always looking for better approaches, if you have any to suggest. Steven On May 21, 2014, at 3:29 AM, Michael Brand wrote: > Hi Steven > >> Steven Adrian writes: >>> #+TBLFM: @1$1..@1$10=index(10) >>> >>> But the formula above just puts the whole vector in each cell. Can anyone >>> tell me how to put the vector values in individual cells? > > The vector elements can be accessed with Calc subscr() and Org "field > coordinates": > http://orgmode.org/manual/References.html > > | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | > #+TBLFM: @1$1..@1$10 = subscr(index(10), $#) > > In a TBLFM I would not use Calc vector functions like index() but a > calculation of $#, here simply f(x) = x: > > | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | > #+TBLFM: @1$1..@1$10 = $# > > Or is there an interesting Calc vector function that is not easy to > mimic? > > Michael >
Re: [O] Insert calc vector directly into spreadsheet cells?
Michael, Here is the custom calc function that is similar to subscr. It will work for both vectors and matrices: (defmath getElem (indices m) (let (i j) (if (vectorp indices) (progn (setq i (cadr indices)) (setq j (nth 2 indices)) (nth j (nth i m)) ) (progn (setq i indices) (nth i m) ) ) ) ) Here is the table function to get matrix data from a table, take the inverse, and write the result to a new table: #+TBLFM: @1$1..@3$3=getElem([@#,$#],inv(arrange(remote(matrixTable,@1$2..@3$4),3)) Thanks for the tip about orgtbl-ascii-plot. I have been working on a set of notes about using calc and org mode that I am migrating over to read more like a tutorial, and I am now thinking about changing the histogram example to use orgtbl-ascii-plot instead of just writing the bin values in a table. Steven On May 26, 2014, at 4:43 PM, Michael Brand wrote: > Hi Steven > > On Mon, May 26, 2014 at 9:39 PM, Steven Adrian > wrote: >> This is great. I wish I had seen this earlier. I did not know about >> the subscr function, but I had basically gotten to the same point by >> writing an equivalent custom calc function. > > With the Calc function defmath? How does it look like? > >> 1. I wrote a custom calc function called tailsInARow that uses the >> calc random function to simulate a coin toss and return the number >> of tails in a row. I used this function to fill a 20x20 table of >> values. I then used the calc histogram function in a table formula >> to read the table values, histogram the number of tails in a row, >> then write the histogram to a new table. > > Didn't know that Calc has a histogram function. The histogram values > would fit perfectly to the ASCII plot within an Org table: > http://orgmode.org/worg/org-contrib/orgtbl-ascii-plot.html > >> 2. I calculated a rotation matrix as a succession of individual >> rotations about x, y, and z axes. I then wrote the resulting matrix >> to a table. I then wrote a table function to read the matrix, take >> the inverse, and write the result to a new table. > > Interesting. How does the "function to read the matrix" look like? > > Michael >
Re: [O] Insert calc vector directly into spreadsheet cells?
Hi Steven On Tue, May 27, 2014 at 11:12 AM, Steven Adrian wrote: > Here is the custom calc function that is similar to subscr. It will > work for both vectors and matrices: > > (defmath getElem (indices m) > (let (i j) > (if (vectorp indices) > (progn > (setq i (cadr indices)) > (setq j (nth 2 indices)) > (nth j (nth i m)) > ) > (progn > (setq i indices) > (nth i m) > ) > ) > ) > ) > > Here is the table function to get matrix data from a table, take the > inverse, and write the result to a new table: > > #+TBLFM: > @1$1..@3$3=getElem([@#,$#],inv(arrange(remote(matrixTable,@1$2..@3$4),3)) Very nice. I didn't know the Calc function arrange([a, b, c, d], 2) to get [[a, b], [c, d]]. I always thought that when a TBLFM range spans more than one row and column like in @1$2..@2$3 it should learn to result in [[a, b], [c, d]] instead of the current [a, b, c, d]. Thanks for showing how to deal with this. Michael
[O] LaTex export questions
Hi, I'm trying to export an org-mode doc to LaTex and subsequently to PDF. This is a literary novel, written in prose. Right now when I run the export command, the resulting file is incorrectly formatted for the literary world, and I'm not sure how to change it. Is there a dialog or "customize" menu that allows users to eliminate some default settings, and add others? Thank you! Steven Arntson
Re: [O] Adding source location information when tangling
Envoyé de mon iPhone > Le 25 mai 2014 à 18:28, Thomas Morgan a écrit : > > Dear Org hackers, > > I have a question about tangling LilyPond code blocks. > > Is there a way to put the commands `\sourcefilename' and > `\sourcefileline' in the tangled file before each block, > perhaps in place of the comment that includes the same information? Yes - Check out the header option concerning tangling with comment. So links are inserted as comments which contain information about the filename And the header from which it was tangled. Cheers, Rainer > (These commands are equivalent to the `#line LINENUM "FILE"' > directive in C.) If possible I'd like to let LilyPond know how > to give error messages that refer to the originating Org file. > > Thanks, > Thomas >
Re: [O] LaTex export questions
Steven Arntson writes: > Hi, I'm trying to export an org-mode doc to LaTex and subsequently to > PDF. This is a literary novel, written in prose. Right now when I run > the export command, the resulting file is incorrectly formatted for the > literary world, and I'm not sure how to change it. Is there a dialog or > "customize" menu that allows users to eliminate some default settings, > and add others? Maybe you can configure it with M-x customize-group org But I think a look at the manual is pretty useful and you can configure it in your .emacs without very much complication: http://orgmode.org/manual/Export-settings.html#Export-settings http://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export -- :: Igor Sosa Mayor :: joseleopoldo1...@gmail.com :: :: GnuPG: 0x1C1E2890 :: http://www.gnupg.org/ :: :: jabberid: rogorido ::::
[O] Define resources in ox-taskjuggler
Hi all I try to use ox-taskjuggler but I'm doing something wrong. I want to allocate resources to different tasks (see sample code below) but I get the error: "Error: crc is not a defined resource" I've read some documentation/tutorials and I've searched this list but I did not find an answer. Can anyone of you gurus see emmediately what is wrong or at least point me in the right direction? Best regards Johan Activities :taskjuggler_project: :PROPERTIES: :start:2014-03-31 :END: * Project Management :0010: :PROPERTIES: :start:2014-03-31 :Duration: 200d :allocate: crc :END: Resources :taskjuggler_resource: * CRC :PROPERTIES: :resource_id: CRC :END:
Re: [O] LaTex export questions
Igor Sosa Mayor writes: > Steven Arntson writes: > >> Hi, I'm trying to export an org-mode doc to LaTex and subsequently to >> PDF. This is a literary novel, written in prose. Right now when I run >> the export command, the resulting file is incorrectly formatted for the >> literary world, and I'm not sure how to change it. Is there a dialog or >> "customize" menu that allows users to eliminate some default settings, >> and add others? > > Maybe you can configure it with > M-x customize-group org > > But I think a look at the manual is pretty useful and you can configure > it in your .emacs without very much complication: > > http://orgmode.org/manual/Export-settings.html#Export-settings > http://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export I may be barking up the wrong tree, but to me the problem seems to be not so much what org does, but what latex does. If that is so, then perhaps what is needed is a latex style file that formats prose "correctly for the literary world". That may be a non-trivial undertaking (but maybe not: typographical demands for a novel are trivial compared to say mathematics). Integrating such a hypothetical style file into org would be pretty easy. But perhaps the OP can clarify: what does "incorrectly formatted for the literary world" mean? Nick
Re: [O] LaTex export questions
Hi Steven, Steven Arntson wrote: Hi, I'm trying to export an org-mode doc to LaTex and subsequently to PDF. This is a literary novel, written in prose. Right now when I run the export command, the resulting file is incorrectly formatted for the literary world, and I'm not sure how to change it. Is there a dialog or "customize" menu that allows users to eliminate some default settings, and add others? Thank you! Steven Arntson In addition to Igor's suggestion you may want to check out http://orgmode.org/worg/org-tutorials/org-latex-export.html As mentioned in the title the following is for the earlier version of org-export; however I used the Thomas Dye's examples and made the appropriate changes for the new exporter in Org v8. Again, please note, that you will have to make adjustments. Also, search this list; for instance Dr. Dye's posts concerning this subject. Regards, Charlie Millar --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
Re: [O] Folding in iESS R buffer
Rainer M Krug writes: > I changed it in the buffer, so that it now reads: > > , > | > > | ## * Variable Transfer from org > | ## > | ## org:variables environment created and in search path > | ## > | > | ## * Back to normal code > | here it is > | > > > ` > > but the folding still results in > > , > | > > | ## * Variable Transfer from org > | ##... > | here it is > | > > > ` these long comment lines have been a problem for headline fontification in outshine buffers before, making the regexp matcher freeze emacs, but this should be fixed. I havn't seen this problem with folding - when I'm on a machine with ESS installed I try it out ... > If it helps, here is the buffer: > > , > | R version 3.1.0 (2014-04-10) -- "Spring Dance" > | Copyright (C) 2014 The R Foundation for Statistical Computing > | Platform: x86_64-apple-darwin13.1.0 (64-bit) > | > | R is free software and comes with ABSOLUTELY NO WARRANTY. > | You are welcome to redistribute it under certain conditions. > | Type 'license()' or 'licence()' for distribution details. > | > | Natural language support but running in an English locale > | > | R is a collaborative project with many contributors. > | Type 'contributors()' for more information and > | 'citation()' on how to cite R or R packages in publications. > | > | Type 'demo()' for some demos, 'help()' for on-line help, or > | 'help.start()' for an HTML browser interface to help. > | Type 'q()' to quit R. > | > | During startup - Warning messages: > | 1: Setting LC_CTYPE failed, using "C" > | 2: Setting LC_COLLATE failed, using "C" > | 3: Setting LC_TIME failed, using "C" > | 4: Setting LC_MESSAGES failed, using "C" > | 5: Setting LC_MONETARY failed, using "C" > | > > options(STERM='iESS', str.dendrogram.last="'", > | > > editor='emacsclient', show.error.locations=TRUE) > | > > | ## * Variable Transfer from org > | ## > | ## org:variables environment created and in search path > | ## > | > | ## * Back to normal code > | here it is > | > > > ` > > I figured it out: > > The problems are the comment lines - if I delete these, it is > working. > > I can work around this. ok, nice -- cheers, Thorsten
Re: [O] LaTex export questions
On 28/05/14 07:42, Nick Dokos wrote: Igor Sosa Mayor writes: Steven Arntson writes: Hi, I'm trying to export an org-mode doc to LaTex and subsequently to PDF. This is a literary novel, written in prose. Right now when I run the export command, the resulting file is incorrectly formatted for the literary world, and I'm not sure how to change it. Is there a dialog or "customize" menu that allows users to eliminate some default settings, and add others? Maybe you can configure it with M-x customize-group org But I think a look at the manual is pretty useful and you can configure it in your .emacs without very much complication: http://orgmode.org/manual/Export-settings.html#Export-settings http://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export I may be barking up the wrong tree, but to me the problem seems to be not so much what org does, but what latex does. If that is so, then perhaps what is needed is a latex style file that formats prose "correctly for the literary world". That may be a non-trivial undertaking (but maybe not: typographical demands for a novel are trivial compared to say mathematics). Integrating such a hypothetical style file into org would be pretty easy. But perhaps the OP can clarify: what does "incorrectly formatted for the literary world" mean? Nick I think this is right. Try #+LATEX_CLASS: book and then modify the defaults in org-export-latex-classes by deleting the \part as the first item in the Levels of the 'book' entry. This will make all your top level headings 'Chapters' which is probably what you want for a novel. Cheers, Alan -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:typh...@iptel.org
Re: [O] LaTex export questions
Nick Dokos writes: > Igor Sosa Mayor writes: > >> Steven Arntson writes: >> >>> Hi, I'm trying to export an org-mode doc to LaTex and subsequently to >>> PDF. This is a literary novel, written in prose. Right now when I run >>> the export command, the resulting file is incorrectly formatted for the >>> literary world, and I'm not sure how to change it. Is there a dialog or >>> "customize" menu that allows users to eliminate some default settings, >>> and add others? >> >> Maybe you can configure it with >> M-x customize-group org >> >> But I think a look at the manual is pretty useful and you can configure >> it in your .emacs without very much complication: >> >> http://orgmode.org/manual/Export-settings.html#Export-settings >> http://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export > > I may be barking up the wrong tree, but to me the problem seems to be > not so much what org does, but what latex does. If that is so, then > perhaps what is needed is a latex style file that formats prose > "correctly for the literary world". That may be a non-trivial > undertaking (but maybe not: typographical demands for a novel are > trivial compared to say mathematics). Integrating such a hypothetical > style file into org would be pretty easy. > > But perhaps the OP can clarify: what does "incorrectly formatted for > the literary world" mean? > > Nick Full disclosure: I'm a beginning emacs user, and I know nothing about LaTex at all! I'm not producing a "book" per se, but a manuscript that will be printed on 8.5 x 11 pages and read by my agent or a publisher. The conventions are simple, but thus far I haven't been able to understand much of what I'm reading in the customize menu for org-mode. Until now I've done this formatting with MS Word or Libre Office. I dislike those programs, but I know how to use them. Simplest has been to take my raw org-mode txt files and convert them manually. It's a tedious last step before sending downstream, which I'd love to replace, and I've seen some beautiful LaTex examples online, so I know it's possible ... Literary format redux: + 12 point text + Title page has title and author name, centered both horizontally and vertically. Contact info for agent is in the bottom left, single spaced. + Remaining pages are double-spaced + Page numbers are centered at the bottom of the page (but no page number on title page) + Each page has a right-justified header in the format LASTNAME/TITLE That's it. I guess I'm wondering now--should I be learning more about org-mode, or more about LaTex? Thank you very much for taking the time to read all of this. -Steven
[O] bug: in source block, titles are not seen as source
I've had this bug me a few times when I work with here documents in bash. #+begin_src sh some-command <<'EOF' * some text EOF #+end_src the line beginning with * is treated as a title and folded. The same goes for example blocks, and perhaps other things. as a workaround, I can insert a tab char, and change the redirection operator to <<- to strip leading tabs some-command <<-'EOF' * some text EOF - Ian
Re: [O] LaTex export questions
Hi Steven, You want to learn more about LaTeX, but it's not too much. I wrote a little book called Self-publishing with LyX that will help you set up the title page as well as some of your other problems. This is not a sales pitch -- it's free :-). Self-publishing with LyX ISBN: 978-0-9803-3242-1 http://www.lulu.com/content/1085870 Cheers, Alan On 28 May 2014 13:25, Steven Arntson wrote: > Nick Dokos writes: > > > Igor Sosa Mayor writes: > > > >> Steven Arntson writes: > >> > >>> Hi, I'm trying to export an org-mode doc to LaTex and subsequently to > >>> PDF. This is a literary novel, written in prose. Right now when I run > >>> the export command, the resulting file is incorrectly formatted for the > >>> literary world, and I'm not sure how to change it. Is there a dialog or > >>> "customize" menu that allows users to eliminate some default settings, > >>> and add others? > >> > >> Maybe you can configure it with > >> M-x customize-group org > >> > >> But I think a look at the manual is pretty useful and you can configure > >> it in your .emacs without very much complication: > >> > >> http://orgmode.org/manual/Export-settings.html#Export-settings > >> > http://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export > > > > I may be barking up the wrong tree, but to me the problem seems to be > > not so much what org does, but what latex does. If that is so, then > > perhaps what is needed is a latex style file that formats prose > > "correctly for the literary world". That may be a non-trivial > > undertaking (but maybe not: typographical demands for a novel are > > trivial compared to say mathematics). Integrating such a hypothetical > > style file into org would be pretty easy. > > > > But perhaps the OP can clarify: what does "incorrectly formatted for > > the literary world" mean? > > > > Nick > > Full disclosure: I'm a beginning emacs user, and I know nothing about > LaTex at all! > > I'm not producing a "book" per se, but a manuscript that will be > printed on 8.5 x 11 pages and read by my agent or a publisher. The > conventions are simple, but thus far I haven't been able to understand > much of what I'm reading in the customize menu for org-mode. > > Until now I've done this formatting with MS Word or Libre Office. I > dislike those programs, but I know how to use them. Simplest has been to > take my raw org-mode txt files and convert them manually. It's a tedious > last step before sending downstream, which I'd love to replace, and I've > seen some beautiful LaTex examples online, so I know it's possible ... > > Literary format redux: > + 12 point text > + Title page has title and author name, centered both horizontally and > vertically. Contact info for agent is in the bottom left, single spaced. > + Remaining pages are double-spaced > + Page numbers are centered at the bottom of the page (but no page number > on title page) > + Each page has a right-justified header in the format LASTNAME/TITLE > > That's it. I guess I'm wondering now--should I be learning more about > org-mode, or more about LaTex? > > Thank you very much for taking the time to read all of this. > > -Steven > > > > -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206
[O] completing-read question
Hey everyone,
My init stabilized about a year ago and therefore I've actually been
spending more time working in org-mode than customizing it!
But that comes at a cost. My Emacs Lisp has become quite rusty. Recently I
started customizing again, and I wanted to use the completing-read function
-- but I am curious what the numbers in these lists are used for.
This is an example I found in one of the tutorials online:
(completing-read
"Complete a foo: "
'(("foobar1" 1) ("barfoo" 2) ("foobaz" 3) ("foobar2" 4))
nil t "fo")
This function appears to work fine without the 1, 2, 3, 4.
If this is outside the scope of this particular mailing list, I will gladly
be directed elsewhere.
Re: [O] LaTex export questions
Hi Alan, I downloaded the book and went through it--thank you for putting that together! It was a valuable overview. Nonetheless, some confusions persist for me since I'm using emacs org-mode and not LyX. Should I be putting LaTeX markup into my org-mode doc, for instance, for formatting the title page, &c? Also, right now when I do the "org to latex to pdf" export, I'm given a table of contents, and I don't want one. I'm still perplexed about where defaults like that are kept. Sometimes I worry that my ignorance is invulnerable. Thanks again! -Steven Alan Tyree writes: > Hi Steven, > You want to learn more about LaTeX, but it's not too much. > > I wrote a little book called Self-publishing with LyX that will help > you set up the title page as well as some of your other problems. This > is not a sales pitch -- it's free :-). > > Self-publishing with LyX > ISBN: 978-0-9803-3242-1 > http://www.lulu.com/content/1085870 > > Cheers, > Alan > > On 28 May 2014 13:25, Steven Arntson wrote: > > > Nick Dokos writes: > > > Igor Sosa Mayor writes: > > > >> Steven Arntson writes: > >> > >>> Hi, I'm trying to export an org-mode doc to LaTex and > subsequently to > >>> PDF. This is a literary novel, written in prose. Right now > when I run > >>> the export command, the resulting file is incorrectly > formatted for the > >>> literary world, and I'm not sure how to change it. Is there a > dialog or > >>> "customize" menu that allows users to eliminate some default > settings, > >>> and add others? > >> > >> Maybe you can configure it with > >> M-x customize-group org > >> > >> But I think a look at the manual is pretty useful and you can > configure > >> it in your .emacs without very much complication: > >> > >> http://orgmode.org/manual/Export-settings.html#Export-settings > >> > http://orgmode.org/manual/LaTeX-and-PDF-export.html#LaTeX-and-PDF-export > > > > I may be barking up the wrong tree, but to me the problem seems > to be > > not so much what org does, but what latex does. If that is so, > then > > perhaps what is needed is a latex style file that formats prose > > "correctly for the literary world". That may be a non-trivial > > undertaking (but maybe not: typographical demands for a novel > are > > trivial compared to say mathematics). Integrating such a > hypothetical > > style file into org would be pretty easy. > > > > But perhaps the OP can clarify: what does "incorrectly formatted > for > > the literary world" mean? > > > > Nick > > > Full disclosure: I'm a beginning emacs user, and I know nothing > about > LaTex at all! > > I'm not producing a "book" per se, but a manuscript that will be > printed on 8.5 x 11 pages and read by my agent or a publisher. The > conventions are simple, but thus far I haven't been able to > understand > much of what I'm reading in the customize menu for org-mode. > > Until now I've done this formatting with MS Word or Libre Office. > I > dislike those programs, but I know how to use them. Simplest has > been to > take my raw org-mode txt files and convert them manually. It's a > tedious > last step before sending downstream, which I'd love to replace, > and I've > seen some beautiful LaTex examples online, so I know it's possible > ... > > Literary format redux: > + 12 point text > + Title page has title and author name, centered both horizontally > and > vertically. Contact info for agent is in the bottom left, single > spaced. > + Remaining pages are double-spaced > + Page numbers are centered at the bottom of the page (but no page > number > on title page) > + Each page has a right-justified header in the format > LASTNAME/TITLE > > That's it. I guess I'm wondering now--should I be learning more > about > org-mode, or more about LaTex? > > Thank you very much for taking the time to read all of this. > > -Steven
Re: [O] LaTex export questions
Am 28.05.2014 um 08:07 schrieb Steven Arntson : > Hi Alan, > > I downloaded the book and went through it--thank you for putting that > together! It was a valuable overview. Nonetheless, some confusions > persist for me since I'm using emacs org-mode and not LyX. Should I be > putting LaTeX markup into my org-mode doc, for instance, for formatting > the title page, &c? > > Also, right now when I do the "org to latex to pdf" export, I'm given a > table of contents, and I don't want one. I'm still perplexed about where > defaults like that are kept. I had exactly the same question yesterday. Putting #+OPTIONS: toc:nil into the org file will suppress the toc. You should read the chapter "Markup for rich export" in the Org Manual. This may answer some of you questions about markup. Axel
