Re: [O] How to change color of (part of) agenda header

[Sebastien Vauban]

Hello Nick,

Nick Dokos wrote:
> Sebastien Vauban writes:
>> I'm trying to get part of the agenda header in another color, here
>> "TODAY":
>>
>>   (add-to-list 'org-agenda-custom-commands
>>`("f" "Today"
>>  (;; list of all TODO entries with deadline today
>>   (tags-todo "DEADLINE=\"<+0d>\""
>>  ((org-agenda-overriding-header
>>(concat "DUE " #("TODAY" 0 4 (face 
>> (:foreground "red")
>>   (org-agenda-skip-function
>>'(org-agenda-skip-entry-if 'notdeadline)
>>  ((org-agenda-format-date ""))) t)
>>
>> The goal is to make what's unique and different from the next agenda
>> blocks very outstanding.
>>
>> Though, it does not work: text is simply copied, as if text properties
>> did not exist.
>>
>> Am I missing something, or writing it in a buggy way?
>
> The limits should be 0 and 5 to get the whole word,

I had doubts on this, and as I couldn't see the results of my change...

> but that's not the problem here: if you do C-c a f to display the
> agenda and then do C-u C-x = on (say) the T of "Today", you will see
> that the face is org-agenda-structure. Doing a grep for that in the
> org lisp directory will quickly lead you to this:
>
> ,
> |   (if org-agenda-overriding-header
> |   (insert (org-add-props (copy-sequence 
> org-agenda-overriding-header)
> |   nil 'face 'org-agenda-structure) "\n")
> `
>
> so it doesn't matter what face property the header had to begin with:
> what is inserted into the buffer is given a different face property.

IIUC, you mean there's absolutely no way to do what I'd like to have?

Except, for example, setting a background if `org-agenda-structure' does
not have one already?  Not of much use, though.

What a pity.

Can't I add a face (should be easy, like above), and get mine applied
"above" `org-agenda-structure'?

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] Emacs-orgmode Digest, Vol 102, Issue 5

[Sebastien Vauban]

Nick Dokos wrote:
> Nick Dokos  writes:
>> "Salome "Södergran\""  writes:
 "Salome "S?dergran\"" wrote:
 > I'm looking for a way to make orgmode export quote signs to LaTeX's 
 > \enquote{}.
 > On stackoverflow.com (1) I found a solution that uses 
 >   (setq org-export-with-smart-quotes t)
 >   (add-to-list 'org-export-smart-quotes-alist .)
 > but on my system I find neither the variable 
 > org-export-with-smart-quotes nor
 > org-export-smartcodes-alist.
 >
 > Am I missing something or has the procedure been changed in the 
 > meanwhile?
 
 You don't use Org mode 8, don't you?  Well, that'd explain...
>>>
>>> With M-x org-version I get: 
>>>   Org-mode version 8.2.7b (8.2.7b-2-g798733-elpaplus @
>>> /home/salome/.emacs.d/elpa/org-plus-contrib-20140721/)
>>>
>>> So the version ought to be ok. What else could be the reason for the 
>>> missing variables?
>>
>> The variable is defined in ox.el. Try
>>
>>   M-x locate-library RET ox RET
>>
>> and if that shows the right provenance, try
>
> M-x load-libary RET ox RET

I wonder as well if it's not related to the LaTeX babel package *and*
the #+LANGUAGE: keyword.

FWIW, I do have this in my .emacs:

#+begin_src emacs-lisp
;; include the `babel' package for language-specific hyphenation and
;; typography
(add-to-list 'org-latex-packages-alist '("french" "babel") t)
#+end_src

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] HTML export of - [ ] does not display box anymore

[Rainer Stengele]

Am 05.08.2014 um 15:39 schrieb Rick Frankel:
> On 2014-08-05 08:25, Rainer Stengele wrote:
>> Hi,
>>
>> doing an html export of
>>
>> * headline
>> - [ ] checkbox
>> - item
>>
>> I do not see the checkbox box anymore as I did in older versions.
>> I tried to find an export setting, tried several settings related to
>> todos but I cannot find a setting stopping the box to be exported.
>>
>> Any hint where I could search for?
>
> Checkbox export is handled by a constant and a custom variable:
>
> - `org-html-checkbox-types' :: A constant defining the output for
> unicode (entity), ascii, and html (form) versions of the
> checkboxes.
> - `org-html-checkbox-type' :: A customizable variable defining
> which version of the above to use. The default is "ascii",
> which should result in backwards compatible output.
>
> Here's the output i get for your list above (using the default ascii
> option):
>
> 
> [ ] checkbox
> 
> item
> 
> 
>
> which seems correct to me.


Hi,

I have these set correctly. What I get is: (I run Org-mode version 8.3beta 
(release_8.3beta-167-g003edd)


http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml"; lang="de" xml:lang="de">

headline




 


/*
@licstart  The following is the entire license notice for the
JavaScript code in this tag.

Copyright (C) 2012-2013 Free Software Foundation, Inc.

The JavaScript code in this tag is free software: you can
redistribute it and/or modify it under the terms of the GNU
General Public License (GNU GPL) as published by the Free Software
Foundation, either version 3 of the License, or (at your option)
any later version.  The code is distributed WITHOUT ANY WARRANTY;
without even the implied warranty of MERCHANTABILITY or FITNESS
FOR A PARTICULAR PURPOSE.  See the GNU GPL for more details.

As additional permission under GNU GPL version 3 section 7, you
may distribute non-source (e.g., minimized or compacted) forms of
that code without the copy of the GNU GPL normally required by
section 4, provided you include this license notice and a URL
through which recipients can access the Corresponding Source.


@licend  The above is the entire license notice
for the JavaScript code in this tag.
*/
8---

Thanks for your help.

Regards,
 Francesco

[O] MobileOrg

[Noah Slater]

Hello folks,

Does anyone know what's happening to MobileOrg? It seems like the project
was taken over by a new maintainer and then subsequently abandoned.

I'd love to use MobileOrg, but I always feel wary about starting to use new
software which likely wont receive any updates.

Thanks,

Noah

Re: [O] Can't execute the introductory code: take table as input to produce mean

[Sebastien Vauban]

jenia.ivlev wrote:
>  Its the first time I use this type of mail system. I connected here
>  using gmane and gnus. I;m not sure how to answer the thread "Can't
>  execute the introductory code: take table as input to produce mean".
>  So i'll just try to answer the best way I can who means I'll answer to:
>  emacs-orgmode@gnu.org.
>
>  Thanks Sebastien. Tell me though please, how do I define R-mean(x) to
>  take any x? How do I run R-mean in the following form:
>  R-mean(my-table1), R-mean(my-table2)...
>  Cause here, it seems that R-mean is defined with the variable "x"
>  hard-wired to  a specific value, namely x=tbl-example-data.

Adding `:var x=something' serves 2 purposes:

- Defining the `x' parameter (to the code block)
- Setting its default value

>  So again, how do I call R-mean with x=tbl-example-data2 lets say
>  (without redefining R-mean)?

#+call: R-mean(x=tbl-example-data2)

Best regards,
  Seb

-- 
Sebastien Vauban

Re: [O] (Maybe) enhance `org-element-src-block-interpreter'?

[Thorsten Jolitz]

Nicolas Goaziou  writes:

> Thorsten Jolitz  writes:
>
>> I see, thanks. I'm still getting used to the 'org-element API', but it
>> seems to be much easier than I thought: just use
>> org-element-at-point' and
>> `org-element-interpret-data' in most cases ...
>
> Correct.
>
> For completeness, if you're working at the local level (i.e. with
> `org-element-at-point'), available accessors are
>
>   - `org-element-type'
>   - `org-element-property'
>
> When you're working at the global level (i.e. with
> `org-element-parse-buffer'), you get another accessor,
> `org-element-contents', and some tools to modify the parse tree
>
>   - `org-element-put-property'
>   - `org-element-adopt-element'
>   - `org-element-insert-before'
>   - `org-element-extract-element'
>   - `org-element-set-element'
>
> In both cases, `org-element-interpret-data' is the only way to turn data
> back into Org syntax.

That makes things much clearer, thanks.

I definitely would have used `org-element-put-property' to modify a
'local' parse-tree too, but I can just as well directly use `plist-put'
on the raw plist in its cdr - would that be the correct way?

-- 
cheers,
Thorsten

Re: [O] HTML export of - [ ] does not display box anymore

[Rick Frankel]

On Wed, Aug 06, 2014 at 10:05:25AM +0200, Rainer Stengele wrote:
>Am 05.08.2014 um 15:39 schrieb Rick Frankel:
>
>I do not see the checkbox box anymore as I did in older versions.
>I tried to find an export setting, tried several settings related to
>todos but I cannot find a setting stopping the box to be exported.
>

>I have these set correctly. What I get is: (I run Org-mode version 8.3beta
>(release_8.3beta-167-g003edd)

You are correct. This was broken in commit c9ca0b6... ox-html: Use options
instead of hard-coded variables.

I will look into a fix later.

rick

[O] Large numbers of named variables in Babel

[Brett Witty]

Hi,

I'm trying to write my RPG adventures in org-mode and would like to bring
character sheets into that fold. Is there a way in Babel to have a vast
number of named variables that I can feed into source blocks? Are macros
the way to achieve this?

As an example, I'd like something like a big (hidden) table:
#+NAME: stats
| STR | 13 |
| DEX | 12 |
| CON | 11 |

and then later I can use that like:
#+NAME: AC
#+begin_src python :var dex=table[DEX] :var armour=table[ARMOUR]
return dex + armour
#+end_src

I know I can make explicit cell references, but it'd be neat to just use
keys for values.

Cheers,

BrettW

Re: [O] HTML export of - [ ] does not display box anymore

[Rick Frankel]

On Wed, Aug 06, 2014 at 10:05:25AM +0200, Rainer Stengele wrote:
>Am 05.08.2014 um 15:39 schrieb Rick Frankel:
>  On 2014-08-05 08:25, Rainer Stengele wrote:
>doing an html export of
> 
>* headline
>- [ ] checkbox
>- item
> 
>I do not see the checkbox box anymore as I did in older versions.
>I tried to find an export setting, tried several settings related to
>todos but I cannot find a setting stopping the box to be exported.
> 

The fix was easier than i thought. Please pull master and retry.

rick

Re: [O] (Maybe) enhance `org-element-src-block-interpreter'?

[Thorsten Jolitz]

Thorsten Jolitz  writes:

> Nicolas Goaziou  writes:
>
>> Thorsten Jolitz  writes:
>>
>>> I see, thanks. I'm still getting used to the 'org-element API', but it
>>> seems to be much easier than I thought: just use
>>> org-element-at-point' and
>>> `org-element-interpret-data' in most cases ...
>>
>> Correct.
>>
>> For completeness, if you're working at the local level (i.e. with
>> `org-element-at-point'), available accessors are
>>
>>   - `org-element-type'
>>   - `org-element-property'
>>
>> When you're working at the global level (i.e. with
>> `org-element-parse-buffer'), you get another accessor,
>> `org-element-contents', and some tools to modify the parse tree
>>
>>   - `org-element-put-property'
>>   - `org-element-adopt-element'
>>   - `org-element-insert-before'
>>   - `org-element-extract-element'
>>   - `org-element-set-element'
>>
>> In both cases, `org-element-interpret-data' is the only way to turn data
>> back into Org syntax.
>
> That makes things much clearer, thanks.
>
> I definitely would have used `org-element-put-property' to modify a
> 'local' parse-tree too, but I can just as well directly use `plist-put'
> on the raw plist in its cdr - would that be the correct way?

I tried it out, works very nicely in this buffer:

* ORG SCRATCH

#+name: myPicoBlock
#+header: :var X=5
#+begin_src picolisp :results value raw :tangle no
  (+ 3 X)
#+end_src

#+results:
8

Evaluating the following src-block with C-c C-c gives an error:
 
,
| split-string: Wrong type argument: stringp, nil
`

but it can be copied to the *scratch* buffer and evaluated there.

#+begin_src emacs-lisp :results
(defun tj/try-parser-api ()
  (let (ptree)
(org-babel-map-src-blocks nil
  (when (string= lang "picolisp")
(setq ptree
  (delq nil
(list (org-element-at-point) ptree)
(org-element-put-property (car ptree) :value " (* 5 X)\n")
(message "%S" ptree)
(mapconcat 
 'org-element-interpret-data
 ptree "\n")))
#+end_src

Then interpreting works as expected:

#+begin_src emacs-lisp :results raw
(tj/try-parser-api)
#+end_src

#+results:
#+NAME: myPicoBlock
#+HEADER: :var X=5
#+BEGIN_SRC picolisp :results value raw :tangle no
   (* 5 X)
#+END_SRC

#+results: myPicoBlock
25


and I can actually use `org-element-put-property' on the car of the
local parse-tree (but need to add an "\n"). 

-- 
cheers,
Thorsten

Re: [O] Highlighting text for HTML tag export?

[Thomas Herbert]

Thanks Sebastien, unfortunately this is not that useful if you simply
want to highlight words or a sentence in a paragraph.

BTW for anyone who is interested I discovered "Wrap Region" 
(https://github.com/rejeep/wrap-region.el) which is pretty
useful. You can select a region, hit a key and it will pair it.

I was using this for example:

   (wrap-region-add-wrapper "" "" "m")

Unfortunately using HTML markup in an org file, org-ruby doesn't parse
these tags.

Might be an interesting feature request to to coinside with _underline_,
*bold*, etc

Sebastien Vauban  writes:

> 'Mash wrote:
>> Just been looking around and I have not come across a way to "highlight"
>> text in org-mode to be HTML exported as the ... tags?
>>
>> Anyone know if this exists?
>
> You could use org-macros.
>
> Or simply:
>
> #+HTML: 
> ...
> #+HTML: 
>
> Best regards,
>   Seb

--
Thomas Herbert

[O] Clocksums are not computed for custom agenda views

[Barton]

Hi,

I have several custom agenda commands of this form:

(setq org-agenda-custom-commands
  '(("c" . "Custom views")
("cw" "Work" agenda ""
 ((org-agenda-files '(
  ;; work files
  ))

Whenever I try to view these in column view, the CLOCKSUM is blank
unless I go into the specific buffer with the file and run
org-clock-sum.

On the other hand, org-clock-sum seems to happen automatically for all
agenda file buffers if the same files are added to org-agenda-files
directly and then accessed with org-agenda-list, org-agenda-columns.

What would be the correct way to automate this CLOCKSUM computation for
the files in my custom agenda views?


My org-columns-default-format is "%25ITEM(Item) %5Effort(t est){:}
%5CLOCKSUM_T(t today){:} %SCHEDULED(ON) %DEADLINE(BY)".

--
Barton

Re: [O] Large numbers of named variables in Babel

[John Kitchin]

Brett Witty  writes:

This is close to what you want I think.

#+TBLNAME: stats
| STR | 13 |
| DEX | 12 |
| CON | 11 |


#+BEGIN_SRC python :results value :var data=stats
d = dict(data)
return d['DEX'] + d['CON']
#+END_SRC

#+RESULTS:
: 23


> Hi,
>
> I'm trying to write my RPG adventures in org-mode and would like to
> bring character sheets into that fold. Is there a way in Babel to have
> a vast number of named variables that I can feed into source blocks?
> Are macros the way to achieve this?
>
> As an example, I'd like something like a big (hidden) table:
> #+NAME: stats
> | STR | 13 |
> | DEX | 12 |
> | CON | 11 |
>
> and then later I can use that like:
> #+NAME: AC
> #+begin_src python :var dex=table[DEX] :var armour=table[ARMOUR]
> return dex + armour
> #+end_src
>
> I know I can make explicit cell references, but it'd be neat to just
> use keys for values.
>
> Cheers,
>
> BrettW
>

-- 
---
John Kitchin
Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu

[O] Creating a new contacts style for org-vcard [was: Re: ANN: org-vcard. ...]

[Alexis]

Feng Shu wrote:

> Is this "tree" style possible?

> #+begin-comment
> * People
> ** Joan Smith
> :PROPERTIES:
> :KIND: individual
> :FIELDTYPE: name
> :END:
> *** Cell
> :PROPERTIES:
> :FIELDTYPE: cells-folder
> :END:
>   999 991
>   999 992
>   999 993
>   999 994
>   999 995
> *** Email 
> :PROPERTIES:
> :FIELDTYPE: emails-folder
> :END:
>  address@hidden
>  address@hidden
>  address@hidden
>  address@hidden
>  address@hidden

> #+end-comment

Here's what i've come up with. :-)

(a) Please make sure you have the latest version of org-vcard
installed!

(b) For clarity, i've made use of the `s-repeat` function from the
`s` library; if you don't already have it installed, you can install it
from MELPA or Marmalade.

(c) Assuming you've installed org-vcard from MELPA, copy the 'tree'
folder from the elpa/org-vcard-[date]/styles/ folder to the
~/.emacs.d/org-vcard-styles/ folder; the latter should already have been
created for you automatically. Then rename:

~/.emacs.d/org-vcard-styles/tree

to

~/.emacs.d/org-vcard-styles/fengshu

(d) Open the file:

~/.emacs.d/org-vcard-styles/fengshu/functions.el

Delete its entire contents, and replace it with the text between the
BEGIN and END markers:

--- BEGIN ---
(defun org-vcard-export-from-fengshu (source destination)
  "Export fengshu-style SOURCE to vCard format, sending output
to DESTINATION.

SOURCE must be \"buffer\", \"region\" or \"subtree\".
DESTINATION must be either \"buffer\" or \"file\"."
  (let* ((in-contact-entry nil)
 (fengshu-style-properties
  (or (cadr (assoc org-vcard-active-version
   (cadr (assoc org-vcard-active-language
(cadr (assoc "fengshu" 
org-vcard-styles-languages-mappings))
  (error "No mapping available for specified vCard version")))
 (encoding (cond
((string= "4.0" org-vcard-active-version) 'utf-8)
((string= "3.0" org-vcard-active-version) 'utf-8)
((string= "2.1" org-vcard-active-version) 'us-ascii)))
 (output (encode-coding-string "" encoding)))
(if (not (member source '("buffer" "region" "subtree")))
(error "Invalid source type"))
(save-excursion
  (let ((search-result nil))
(cond
 ((string= "region" source)
  (narrow-to-region (region-beginning) (region-end)))
 ((string= "subtree" source)
  (org-narrow-to-subtree)))
(goto-char (point-min))
(setq case-fold-search t)
(while (re-search-forward "\\s *:FIELDTYPE:\\s *name" nil t)
  (let ((content (concat (org-vcard-export-line "BEGIN:VCARD" "" t)
 (org-vcard-export-line "VERSION" 
org-vcard-active-version)))
(end-vcard nil))
(setq content (concat content
  (org-vcard-export-line "FN" (org-get-heading 
t t
(if (or (string= "3.0" org-vcard-active-version)
   (string= "2.1" org-vcard-active-version))
(setq content (concat content
  (org-vcard-export-line "N" ""
(while (and (setq search-result (re-search-forward "\\s 
*:FIELDTYPE:\\s *\\(\\(?:\\w\\|-\\)+\\)" nil t))
  (not end-vcard))
  (let ((fieldtype (match-string 1)))
(if (not (string= "name" (downcase fieldtype)))
;; BEGIN main changes
(if (or (string= "cell" (downcase fieldtype))
   (string= "email" (downcase fieldtype)))
(let ((done nil)
  (heading-levels (let ((l nil)
(n (1+ 
(org-current-level
(while (> n 0)
  (setq l (append l 
`(,(s-repeat n "\\*"
  (setq n (1- n)))
l)))
  (while (and (not done)
  (re-search-forward (concat (nth 0 
heading-levels) " +\\([^\n]+\\)\n") nil t))
(setq content (concat content
  (org-vcard-export-line
   (cdr (assoc (downcase 
fieldtype) fengshu-style-properties))
   (match-string 1
(dolist (level (cdr heading-levels))
  (if (or (looking-at (concat level " +"))
 (looking-at "^ +$")
 (looking-at "^$"))
  (setq done t)
  ;; END main changes
  (setq content (

Re: [O] R code block produces only partial output

[Charles C. Berry]

On Tue, 5 Aug 2014, Aaron Ecay wrote:


Hi Chuck,

2014ko abuztuak 5an, "Charles C. Berry"-ek idatzi zuen:

[...]




Here is the docstring from ESS's inferior-S-prompt:

inferior-S-prompt is a variable defined in `ess-custom.el'.
Its value is "[]a-zA-Z0-9.[]*\\([>+.] \\)*> "

[snip]




Note that there is a space *required* after the [>+.], but the hard coded
regex in `org-babel-R-evaluate-session' lets the space be optional.

I am guessing the a-zA-Z stuff is there to strip 'Browse[1]> ' prompts and
such, which probably isn't an issue for babel.


Why doesn’t org just use the value of inferior-S-prompt?  (which would
then need to have the bit concatenated to the end that matches
e.g. [1]).  Another way of putting this might be “does the space that
ESS requires ever turn up missing?”


I don't really know why.

Re the space, do the characters preceeding the [>+.] ever show up 
in Babel output?






Just before the defcustom for inferior-S-prompt, I see this comment
in ess-custom.el:

;; need to recognise  + + + > > >
;; and "+ . + " in tracebug prompt

Ha! The '.' seems to be for ess-tracebug. I am guessing that nobody will
need to output tracebug sessions from babel. So maybe it is safe to delete
the "." after all - or at least require the space after it.


Tracebug is on by default in ESS – C-h v ess-use-tracebug.  Tracebug
even has babel support: see e.g. line 148 in ess.tracebug.el
.



When I said 'output tracebug sessions' I meant in the sense of using 
`:results output' to save the part of the session pertaining to tracebug 
in the *.org buffer, which seemed like an unusual use case.





Maybe the regex should be put in a defcustom.


Why?


options(prompt="$ ") # for example

Plus, if anything like the case that started this thread ever happens 
again it might be easier to figure out and offer workarounds for special 
cases that would be hazardous as a default setting.



The current mismatch between babel and ESS seems like a bug, but
once that’s fixed I don’t see the use case for configurability here.
(But maybe you have something in mind...)


It looks like the babel regex was copied and intentionally modified for 
some reason --- suggesting the author knows something we do not, e.g. a 
case that would be broken by using `inferior-S-prompt'.


I don't have a handle on all the issues in `comint-use-prompt-regexp' and 
all the `inferior-*-prompt' variables, but those are customizable.


If the mismatch is a bug, why not use 'inferior-S-prompt' as the default 
and allow customization or at least use  `(defvar org-babel-R-prompt 
inferior-S-prompt)'?


HTH,

Chuck

Re: [O] MobileOrg

[Subhan Michael Tindall]

I wish I did.
I’ve tried using it on my Android phone. It appears pretty stable, but the 
documentation is limited and woefully out of date.
There’s also a few areas I’d like to do or see some enhancements on the mobile 
end, for example handling display or edit of properties is very limited, time 
stamp defaults should maybe be set to current time instead of 00:00, etc.
It feels like about 85% of a really good app right now, and I’d love to see it 
get to 95 or 100%, but as it is now it’s mostly useful as a display option 
rather than for capturing anything other than simple data.
I’m not an Android/mobile programmer or I’d try making some modifications 
myself.
Subhan


From: emacs-orgmode-bounces+subhant=familycareinc@gnu.org 
[mailto:emacs-orgmode-bounces+subhant=familycareinc@gnu.org] On Behalf Of 
Noah Slater
Sent: Wednesday, August 06, 2014 7:08 AM
To: emacs-orgmode@gnu.org
Subject: [O] MobileOrg

Hello folks,

Does anyone know what's happening to MobileOrg? It seems like the project was 
taken over by a new maintainer and then subsequently abandoned.

I'd love to use MobileOrg, but I always feel wary about starting to use new 
software which likely wont receive any updates.

Thanks,

Noah


This message is intended for the sole use of the individual and entity to which 
it is addressed and may contain information that is privileged, confidential 
and exempt from disclosure under applicable law. If you are not the intended 
addressee, nor authorized to receive for the intended addressee, you are hereby 
notified that you may not use, copy, disclose or distribute to anyone the 
message or any information contained in the message. If you have received this 
message in error, please immediately advise the sender by reply email and 
delete the message.  Thank you.

Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.

[Eric Abrahamsen]

Alexis  writes:

> Gour writes:
>
>> what do you think about BBDB-v3? Many people like it, but I must admit
>> I haven't take closer look at it?
>
> i haven't tried using BBDB-v3, only BBDB-v2, several years ago. i found
> the latter, hm, 'clunky'. (Similar to how, until the advent of mu4e, i
> found no Emacs-based MUA with maildir support which i found as usable as
> Mutt.) And iirc, part of the problem might have been lack of (full)
> support for Australian phone numbers and/or postcodes, which at the time
> i really didn't want to wrestle with.
>
> In any case, org-contacts.el has nowwhetted my appetite for an Org-based
> contacts solution - given the slogan "Your life in plain text", contacts
> management certainly seems to me to fall within Org's remit. :-)
>
>> However, I wonder whether it's flexible enough to define one's own
>> properties of format of one's contact data and what about syncing?
>
> i've just had a quick scan through the BBDB-v3 source, and
> superficially, it looks like the properties are hard-coded.

If by properties you mean arbitrary key-value data, BBDB does indeed
support that -- properties are known as "fields", and "xfields" are
user-designated fields. Labels and values can be arbitrarily designated
by the user, and with a bit of coding you can format them in unusual
ways, or have them "do things".

> Regarding syncing, the BBDB page on SourceForge suggests that existing
> support for this might be rather limited - i only see mention of
> PalmPilot syncing. i would certainly be interested to know if anyone's
> created CardDAV support for BBDB - given that Google Contacts can be
> accessed via CardDAV, and given (what i imagine to be) the large number
> of people syncing their Android phone's contacts with Google Contacts,
> such support might well be in demand!
>
>> I wish you all the best hoping org-mode users will find decent solution
>> for handling contacts soon.
>
> Thank you! i'm hoping my ongoing work with org-vcard might eventually
> contribute towards this. :-)
>
>
> Alexis.

Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.

[Alexis]

Eric Abrahamsen writes:

> If by properties you mean arbitrary key-value data, BBDB does indeed
> support that -- properties are known as "fields", and "xfields" are
> user-designated fields. Labels and values can be arbitrarily
> designated by the user, and with a bit of coding you can format them
> in unusual ways, or have them "do things".

Ah okay - thanks for clearing that up!


Alexis.

Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.

[Eric Abrahamsen]

Alexis  writes:

> Eric Abrahamsen writes:
>
>> If by properties you mean arbitrary key-value data, BBDB does indeed
>> support that -- properties are known as "fields", and "xfields" are
>> user-designated fields. Labels and values can be arbitrarily
>> designated by the user, and with a bit of coding you can format them
>> in unusual ways, or have them "do things".
>
> Ah okay - thanks for clearing that up!

Not that it really changes the discussion :) But I do feel the need to
stick up for BBDB...

Re: [O] MobileOrg

[Alexis]

Subhan Michael Tindall writes:

> There’s also a few areas I’d like to do or see some enhancements on
> the mobile end, for example handling display or edit of properties is
> very limited

*nod* i started to address this issue with this pull request:

https://github.com/matburt/mobileorg-android/pull/434

which got merged  But given the lack of commits and releases more
generally, i've been reticent to work on this further.


Alexis.

Re: [O] Org equivalent to \chapter*

[Thomas S. Dye]

Aloha Rasmus,

Rasmus  writes:

> Alan L Tyree  writes:
>
>> I'm sure this has been asked before, but I can't seem to find it. Is
>> there an org markup that produces a starred latex heading?
>>
>> In a book, for example, I want the Preface to be at chapter level, but
>> not included in the numbering. Same for HTML export, of course.
>
> You would probably need some sort of filter for this.  Most certainly
> you will be able to find implementations on this list.
>
> Here's something from my init file that works with LaTeX.  Other
> formats such as txt and html are harder since Org generates section
> numbers and the TOC.

Thanks for sharing this.  It will be useful for book authors. 

Do you think it is possible to write a general headline filter that
takes care of all the various LaTeX possibilities?  Right now Iʻm using
tags to ignoreheading, clearpage, and newpage.  In addition to your
nonum filter, Eric S. has a filter that gets rid of a heading and
promotes the content, which I havenʻt had occasion to use, but also has
its own tag.

>From the LaTeX authorʻs point of view, it would be great to have a set
of tags (and options) that "just work."  Do you (and others) think the
"tag and filter" approach can achieve this?  Or, are there too many
moving parts to make it feasible?

All the best,
Tom

-- 
Thomas S. Dye
http://www.tsdye.com

Re: [O] ANN: org-vcard. Export/import vCards. Backwards-compatible with org-contacts.el.

[Charles Philip Chan]

On 6 Aug 2014, flexibe...@gmail.com wrote:

> i haven't tried using BBDB-v3, only BBDB-v2, several years ago. i
> found the latter, hm, 'clunky'. (Similar to how, until the advent of
> mu4e, i found no Emacs-based MUA with maildir support which i found as
> usable as Mutt.)

Personally I find no MUA as usable and feature rich as Gnus. ;-)

> And iirc, part of the problem might have been lack of (full) support
> for Australian phone numbers and/or postcodes, which at the time i
> really didn't want to wrestle with.

I am mainly talking about bbdb3 now, since I can't remember the variable
names in bbdb2. For phone numbers one can use free form style by calling
bbdb-insert-field with a prefix or change the variable bbdb-phone-style:

,[ bbdb-phone-style ]
| bbdb-phone-style is a variable defined in `bbdb.el'.
| Its value is nanp
| 
| Documentation:
| Phone numbering plan assumed by BBDB.
| The value 'nanp refers to the North American Numbering Plan.
| The value nil refers to a free-style numbering plan.
| 
| You can have both styles of phone number in your database by providing a
| prefix argument to the command `bbdb-insert-field'.
`

As for postal codes, either turn the checking off by setting
bbdb-check-postcode to nil or change the variable bbdb-legal-postcodes:

,[ bbdb-legal-postcodes ]
| bbdb-legal-postcodes is a variable defined in `bbdb.el'.
| Its value is
| ("^$" "^[ \n]*[0-9][0-9]?[0-9]?[0-9]?[0-9]?[0-9]?[\n]*$" "^[  
\n]*\\([0-9][0-9][0-9][0-9][0-9]\\)[\n]*-?[ 
\n]*\\([0-9][0-9][0-9][0-9]?\\)[\n]*$" "^[  \n]*\\([A-Za-z0-9]+\\)[ 
\n]+\\([A-Za-z0-9]+\\)[ \n]*$" "^[  \n]*\\([A-Z]+\\)[   
\n]*-?[ \n]*\\([0-9]+ ?[A-Z]*\\)[   \n]*$" "^[  
\n]*\\([A-Z]+\\)[   \n]*-?[ \n]*\\([0-9]+\\)[   
\n]+\\([0-9]+\\)[   \n]*$")
| 
| 
| Documentation:
| List of regexps that match legal postcodes.
| Whether this is used at all depends on the variable `bbdb-check-postcode'.
`

Charles

-- 
I did this 'cause Linux gives me a woody.  It doesn't generate revenue.
(Dave '-ddt->` Taylor, announcing DOOM for Linux)


signature.asc
Description: PGP signature

Re: [O] Org equivalent to \chapter*

[Rasmus]

Thomas,

t...@tsdye.com (Thomas S. Dye) writes:

> Rasmus  writes:
>
>> Alan L Tyree  writes:
>>
>>> I'm sure this has been asked before, but I can't seem to find it. Is
>>> there an org markup that produces a starred latex heading?
>>>
>>> In a book, for example, I want the Preface to be at chapter level, but
>>> not included in the numbering. Same for HTML export, of course.
>>
>> You would probably need some sort of filter for this.  Most certainly
>> you will be able to find implementations on this list.
>>
>> Here's something from my init file that works with LaTeX.  Other
>> formats such as txt and html are harder since Org generates section
>> numbers and the TOC.
>
> Thanks for sharing this.  It will be useful for book authors. 
>
> Do you think it is possible to write a general headline filter that
> takes care of all the various LaTeX possibilities?  

I don't like *one* filter to rule them all.  Of course, if it's a
collection of other function calls that is OK.  As your recent
question showed execution order may matter,
(e.g. with :ignoreheading:clearpage:).

Of course it's possible to bundle a couple of filters generally useful
for ox-latex and provide a "consistent" interface.  Alternatively, one
could make a ox-latex+.el that provides a derived class with extra
options. That's may be more work, and may be harder to hack.

In fact Aaron started ox-extra.el, with the intention of providing
"semi-official" extensions but Worg may be a better means of
communication.

> Right now Iʻm using tags to ignoreheading, clearpage, and newpage.
> In addition to your nonum filter, Eric S. has a filter that gets rid
> of a heading and promotes the content, which I havenʻt had occasion
> to use, but also has its own tag.

Yes, Eric has cool tree-based filter(s).  I want to study them more
carefully.  Quite possibly, it's easier to provide elegant filters
with trees.  For instance, you have direct access to the element
representation.  In my filters I "hack" my way to this using
text-properties.

> From the LaTeX authorʻs point of view, it would be great to have a set
> of tags (and options) that "just work."

Would you want this as a derived class or filters?  Perhaps it's
easier to have a derived class with an alternative headline
function. . .

> Do you (and others) think the "tag and filter" approach can achieve
> this?  Or, are there too many moving parts to make it feasible?

Yes.

The ox-koma-script interface is basically controlled via tags.  I
think it's nice.

—Rasmus

-- 
If you can mix business and politics wonderful things can happen!

Re: [O] Cannot build documentation (release_8.3beta-155-g82b64d)

[Achim Gratz]

Vicente Vera writes:
> Yes, i had an old makeinfo (4.13) that lives in the debian wheezy
> repository. Just now got the latest version and it worked. Didn't
> thought about this since some commits ago the documentation was built
> just fine with makeinfo 4.13.

Glad you've solved it, but makeinfo 4.13 should work just fine (I'm
using it).  So there must still be something else wrong with that
makeinfo.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: [O] exporting quotes

[Achim Gratz]

Salome "Södergran\" writes:
> Indeed! I find an older org-version (7.x) in /usr/share/emacs. I have
> now changed the order in the load-path-list to load the local
> installations first.

When you install from ELPA, leave load-path alone (remove any
alterations in respect to Org or any other package installed via ELPA),
but you must make sure that:

1) The original Org installation that comes with Emacs must not be
loaded in any way when you install from ELPA.  This is most easily done
by doing the install from "emacs -Q", although you may then need to set
up package manager in that session.

2) After installation, the first thing in your init script should be
(package-initialize) so that customization of Org variables doesn't
auto-load the old version that came with Emacs.  You shouldn't require
anything from Org, but if you still want to, it must be after
package-initialize.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: [O] MobileOrg

[Xebar Saram]

Shame

ive been using it for the past few months (took me a loong time to setup as
the documentation is really hard to follow). i really would love to see
mobile org developed as having my orgmode data on the go is really crucial

best

Z


On Wed, Aug 6, 2014 at 7:33 PM, Alexis  wrote:

>
> Subhan Michael Tindall writes:
>
> > There’s also a few areas I’d like to do or see some enhancements on
> > the mobile end, for example handling display or edit of properties is
> > very limited
>
> *nod* i started to address this issue with this pull request:
>
> https://github.com/matburt/mobileorg-android/pull/434
>
> which got merged  But given the lack of commits and releases more
> generally, i've been reticent to work on this further.
>
>
> Alexis.
>
>

Re: [O] HTML export of - [ ] does not display box anymore => solved

[Rainer Stengele]

Am 06.08.2014 um 16:28 schrieb Rick Frankel:
> On Wed, Aug 06, 2014 at 10:05:25AM +0200, Rainer Stengele wrote:
>>Am 05.08.2014 um 15:39 schrieb Rick Frankel:
>>  On 2014-08-05 08:25, Rainer Stengele wrote:
>>doing an html export of
>>
>>* headline
>>- [ ] checkbox
>>- item
>>
>>I do not see the checkbox box anymore as I did in older versions.
>>I tried to find an export setting, tried several settings related to
>>todos but I cannot find a setting stopping the box to be exported.
>>
> The fix was easier than i thought. Please pull master and retry.
>
> rick
Perfect, that brings it back.
Thanks a lot!
Rainer

Re: [O] Org equivalent to \chapter*

[Thomas S. Dye]

Aloha Rasmus,

Rasmus  writes:

> Thomas,
>
> t...@tsdye.com (Thomas S. Dye) writes:
>
>> Rasmus  writes:
>>
>>> Alan L Tyree  writes:
>>>
 I'm sure this has been asked before, but I can't seem to find it. Is
 there an org markup that produces a starred latex heading?

 In a book, for example, I want the Preface to be at chapter level, but
 not included in the numbering. Same for HTML export, of course.
>>>
>>> You would probably need some sort of filter for this.  Most certainly
>>> you will be able to find implementations on this list.
>>>
>>> Here's something from my init file that works with LaTeX.  Other
>>> formats such as txt and html are harder since Org generates section
>>> numbers and the TOC.
>>
>> Thanks for sharing this.  It will be useful for book authors. 
>>
>> Do you think it is possible to write a general headline filter that
>> takes care of all the various LaTeX possibilities?  
>
> I don't like *one* filter to rule them all.  Of course, if it's a
> collection of other function calls that is OK.  As your recent
> question showed execution order may matter,
> (e.g. with :ignoreheading:clearpage:).
>
> Of course it's possible to bundle a couple of filters generally useful
> for ox-latex and provide a "consistent" interface.  Alternatively, one
> could make a ox-latex+.el that provides a derived class with extra
> options. That's may be more work, and may be harder to hack.
>
> In fact Aaron started ox-extra.el, with the intention of providing
> "semi-official" extensions but Worg may be a better means of
> communication.
>
>> Right now Iʻm using tags to ignoreheading, clearpage, and newpage.
>> In addition to your nonum filter, Eric S. has a filter that gets rid
>> of a heading and promotes the content, which I havenʻt had occasion
>> to use, but also has its own tag.
>
> Yes, Eric has cool tree-based filter(s).  I want to study them more
> carefully.  Quite possibly, it's easier to provide elegant filters
> with trees.  For instance, you have direct access to the element
> representation.  In my filters I "hack" my way to this using
> text-properties.
>
>> From the LaTeX authorʻs point of view, it would be great to have a set
>> of tags (and options) that "just work."
>
> Would you want this as a derived class or filters?  Perhaps it's
> easier to have a derived class with an alternative headline
> function. . .
>
>> Do you (and others) think the "tag and filter" approach can achieve
>> this?  Or, are there too many moving parts to make it feasible?
>
> Yes.
>
> The ox-koma-script interface is basically controlled via tags.  I
> think it's nice.

Thanks for this useful overview and the pointers to good examples.

Iʻve been slowly building a set of filters and links that work for me,
but each new project differs a bit from the previous one and I have to
fiddle with the Org mode setup.  Iʻm eager to get to the place Iʻm at
with LaTeX, where I just jump in and start writing.

Thanks again for your help.

All the best,
Tom

-- 
T.S. Dye & Colleagues, Archaeologists
735 Bishop St, Suite 315, Honolulu, HI 96813
Tel: 808-529-0866, Fax: 808-529-0884
http://www.tsdye.com

Re: [O] eliminate creation of backup files in :publishing-directory

[regcl]

> regcl  writes:
>
>> Is there a way to stop org mode from creating backup files in the
>> :publishing-directory?
>
> What are "backup files" exactly?

e.g., the second time you run org-html-export-to-html or
org-html-publish-to-html on README.org you get README.html -plus-
README.html~. I would like to not produce README.html~. I believe there
is a global emacs setting, but I would prefer to disable only those
backups produced by org-html-export-to-html, etc.

Thanks,
regcl

>
> There is `org-publish-after-publishing-hook' which may help cleaning
> up stuff if needed.

Re: [O] :exclude sub folder in org-publish

[regcl]

Bastien  writes:

> Hi,
>
> regcl  writes:
>
>> I could not figure out how to do this from INFO. I found examples of
>> preventing publishing of specific file extensions, but not whole
>> directories.
>
> Unless my memory fails me, :exclude works on names, not just on
> extensions.  So maybe using both :recursive and :exclude can lead
> to what you want.

Yes that matches my understanding and experience. But I could not figure
out how to, for example in this tree ...

~/A
.
+--proj
|  +--.git
|  +--README.org
|  |  +--Manuscript
|  |  |  +--.git
|  |  |  +--README.org
|  |  |  +--drafts
|  |  |  +--GenomicsData
|  |  |  |  +--.git
|  |  |  |  +--README.org

... publish the README's above GenomicsData, but not in GenomicsData.

But maybe this is asking too much of org-mode publish. 

FWIW, I ended up using a recursive sub- make harness with something like
this in the Makefile ...

.PHONY: html
html: README.html

# export org file to html
%.html: %.org
emacs --batch --load=~/.emacs $*.org --eval='(org-html-export-to-html)'


Best,
George

Re: [O] Org equivalent to \chapter*

[Alan L Tyree]

On 07/08/14 05:52, Thomas S. Dye wrote:

Aloha Rasmus,

Rasmus  writes:


Thomas,

t...@tsdye.com (Thomas S. Dye) writes:


Rasmus  writes:


Alan L Tyree  writes:


I'm sure this has been asked before, but I can't seem to find it. Is
there an org markup that produces a starred latex heading?

In a book, for example, I want the Preface to be at chapter level, but
not included in the numbering. Same for HTML export, of course.

You would probably need some sort of filter for this.  Most certainly
you will be able to find implementations on this list.

Here's something from my init file that works with LaTeX.  Other
formats such as txt and html are harder since Org generates section
numbers and the TOC.

Thanks for sharing this.  It will be useful for book authors.

Do you think it is possible to write a general headline filter that
takes care of all the various LaTeX possibilities?

I don't like *one* filter to rule them all.  Of course, if it's a
collection of other function calls that is OK.  As your recent
question showed execution order may matter,
(e.g. with :ignoreheading:clearpage:).

Of course it's possible to bundle a couple of filters generally useful
for ox-latex and provide a "consistent" interface.  Alternatively, one
could make a ox-latex+.el that provides a derived class with extra
options. That's may be more work, and may be harder to hack.

In fact Aaron started ox-extra.el, with the intention of providing
"semi-official" extensions but Worg may be a better means of
communication.


Right now Iʻm using tags to ignoreheading, clearpage, and newpage.
In addition to your nonum filter, Eric S. has a filter that gets rid
of a heading and promotes the content, which I havenʻt had occasion
to use, but also has its own tag.

Yes, Eric has cool tree-based filter(s).  I want to study them more
carefully.  Quite possibly, it's easier to provide elegant filters
with trees.  For instance, you have direct access to the element
representation.  In my filters I "hack" my way to this using
text-properties.


 From the LaTeX authorʻs point of view, it would be great to have a set
of tags (and options) that "just work."

Would you want this as a derived class or filters?  Perhaps it's
easier to have a derived class with an alternative headline
function. . .


Do you (and others) think the "tag and filter" approach can achieve
this?  Or, are there too many moving parts to make it feasible?

Yes.

The ox-koma-script interface is basically controlled via tags.  I
think it's nice.

Thanks for this useful overview and the pointers to good examples.

Iʻve been slowly building a set of filters and links that work for me,
but each new project differs a bit from the previous one and I have to
fiddle with the Org mode setup.  Iʻm eager to get to the place Iʻm at
with LaTeX, where I just jump in and start writing.

Thanks again for your help.

All the best,
Tom


Thanks to everyone who responded.

Several of my books are out of print and I am converting them to ePub 
and to printed form. ePub is pretty smooth by exporting to HTML and then 
using Calibre. LaTeX is the obvious choice for print.


It would be nice to have a single tag that gives the \section*{} 
equivalent for all exports, but I can see that there is some difficulty 
with that. Thanks Rasmus for the LaTeX filter -- I'll have a look at 
adapting it for the HTML.


As Thomas mentioned, having selectively unnumbered sections is pretty 
important for book authors.


Thanks again,
Alan

--
Alan L Tyreehttp://www2.austlii.edu.au/~alan
Tel:  04 2748 6206  sip:typh...@iptel.org

[O] Two potentially useful functions for org-element

[Thorsten Jolitz]

Hi List, 

now that I understand the 'org-element API' a bit better, I think that
the following two functions can be very useful for creating and
modifying Org elements without the usual point movements, regexp
searches and string operations in a buffer:

#+begin_src emacs-lisp
;; might become `org-element-create'
(defun* tj/create-element (&optional insert-p &rest args &key (type 'headline) 
&allow-other-keys)
  "Create Org element, maybe insert at point."
  (let ((strg (org-element-interpret-data
   (list type args
(if insert-p (insert strg) strg)))
#+end_src

#+results:
: tj/create-element


#+begin_src emacs-lisp
;; might become `org-element-rewire'
(defun* tj/rewire-element (&optional replace &rest args &key type 
&allow-other-keys)
  "Rewire element at point, maybe replace it."
  (let* ((elem (org-element-at-point))
 (plist (cadr elem))
 (beg (org-element-property :begin elem))
 (end (org-element-property :end elem))
 strg)
(while args
  (setq plist (plist-put plist (pop args) (pop args
(setq strg (org-element-interpret-data
(list
 (or type (org-element-type elem))
 plist)))
(case replace
  (append (save-excursion (goto-char end) (insert strg)))
  (prepend (goto-char beg) (insert strg))
  (t (if replace
 (let ((marker (save-excursion
 (goto-char end) (point-marker
   (delete-region beg end)
   (goto-char marker)
   (save-excursion (insert strg)))
   strg)
#+end_src

#+results:
: tj/rewire-element

Here are a few usage examples:

#+begin_src emacs-lisp
  (tj/create-element nil
 :type 'src-block
 :language "emacs-lisp"
 :value "(+ 2 2)\n"
 :parameters ":results raw"
 :name "myblock"
 :header '(":var x=5"))
#+end_src

#+results:
: #+NAME: myblock
: #+HEADER: :var x=5
: #+BEGIN_SRC emacs-lisp :results raw
:   (+ 2 2)
: #+END_SRC

#+begin_src emacs-lisp :wrap org
  (tj/create-element nil
 :type 'headline
 :level 2
 :todo-keyword "DONE"
 :priority 66
 :title "Hello World"
 :tags '("tag1" "tag2"))
#+end_src

#+results:
#+BEGIN_org
,** DONE [#B] Hello World :tag1:tag2:
#+END_org

Now eval next src-block


#+begin_src emacs-lisp
  (defun test-fun ()
(tj/rewire-element 'append
   :parameters ":results table :exports both"
   :name (format "random-block-%d" (1+ (random 11)))
   :header '(":var x=5")
   :value (format "%s\n%s\n" '(+ 2 2) '(* 3 x
#+end_src

#+results:
: test-fun

and then, with point at beginning of following src-block, eval 'M-: (test-fun)'

#+BEGIN_SRC emacs-lisp :results raw
  (+ 2 2)
#+END_SRC


#+NAME: random-block-6
#+HEADER: :var x=5
#+BEGIN_SRC emacs-lisp :results table :exports both
  (+ 2 2)
  (* 3 x)
#+END_SRC


-- 
cheers,
Thorsten

Re: [O] MobileOrg documentation?

[John Hendy]

Did you look at the docs?
- https://github.com/matburt/mobileorg-android/wiki/Documentation

Unfortunately, looks like his images are borked at the moment. It's
been a while since I've used it, but you're saying there's not an
intuitive way to add a new heading? Can you just do "** something" (or
similar)?


John

On Mon, Aug 4, 2014 at 11:26 PM, David Masterson  wrote:
> There is not much to the MobileOrg documentation.  For instance, how do
> you 'add' a new heading to an outline?  Any examples around on how to
> use MobileOrg?
> --
> David Masterson
> Programmer At Large
>
>

[O] More detail in the agenda logbook?

[hymie!]

Hi again.

So I've got a few repetitive tasks, for example

* TODO machine backups
** TODO machine 1
*** TODO create backup
*** TODO copy backup to DVD
** TODO machine 2
*** TODO create backup
*** TODO copy backup to DVD
** TODO machine 3
*** TODO create backup
*** TODO copy backup to DVD
** TODO machine 4
*** TODO create backup
*** TODO copy backup to DVD

It's the same set of tasks for each machine.

When I complete these tasks and look at the Agenda Logbook, I see
this:

  State: (DONE) DONE create backup
  State: (DONE) DONE create backup
  State: (DONE) DONE create backup
  State: (DONE) DONE create backup
  State: (DONE) DONE copy backup to DVD
  State: (DONE) DONE copy backup to DVD
  State: (DONE) DONE copy backup to DVD
  State: (DONE) DONE copy backup to DVD

I'd really like to see something along the lines of
  State: (DONE) DONE machine backups / machine 1 / create backup
  State: (DONE) DONE machine backups / machine 2 / create backup
  State: (DONE) DONE machine backups / machine 3 / create backup
  State: (DONE) DONE machine backups / machine 4 / create backup

or

  State: (DONE) DONE machine backups 
 machine 1 
 create backup
  State: (DONE) DONE machine backups 
 machine 2 
 create backup
  State: (DONE) DONE machine backups 
 machine 3 
 create backup
  State: (DONE) DONE machine backups 
 machine 4 
 create backup

Is this possible?

--hymie!http://lactose.homelinux.net/~hymiehy...@lactose.homelinux.net

Re: [O] R code block produces only partial output

[Aaron Ecay]

Hi Eric,

2014ko abuztuak 6an, Eric Schulte-ek idatzi zuen:

[...]

> Perhaps you could begin with a patch for the regexp issue in this
> thread?

I have pushed a patch which allows us to avoid the regex issue
entirely by using a native R method to capture the session output to a
file.

This introduces the change that the output no longer appears in the
session buffer, but I think that’s actually an improvement: we were not
previously echoing the commands to the buffer, such that the output
would show up “out of the blue” without any indication of how it got
there.

-- 
Aaron Ecay