Re: [O] [RFC] Standardized code block keywords

I disagree with Tom on [1]: it should clearly be "srcname", in analogy to #+tblname - and also so I don't have to change my files :-} (but see my question about tblname below). I'll have to change my files, either way. The price one pays for inconsistency. But as I've recently learned from Ca

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

Hi Eric and Nick, Eric Schulte wrote: > Nick Dokos writes: >> Eric Schulte wrote: >> >>> > Other than "colon confusion" (having to specify ``:results silent'' on >>> > the src block header line and ``results silent'' in the #+PROPERTY line >>> > to get the same behavior), this looks better. Not

Re: [O] [RFC] Standardized code block keywords

Hi, > Ideally if we limit each of the above to only one alternative we could > simplify the specification of code blocks in Org-mode making them easier > to learn and use and removing some of the mystery around their syntax. > > What does everyone think? Just to make it as easy as possible for ev

Re: [O] org-contacts or bbdb?

Rasmus writes: > pmli...@free.fr (Peter Münster) writes: > >> Hello, >> >> I would like to manage my contacts, so that I can >> - easily search them >> - add new email addresses from gnus (summary buffer) >> - complete email addresses in gnus (message buffer and prompts in >> mini-buffer) >> -

Re: [O] Patch for bug in adjusting time ranges in Agenda

I have just checked in a slightly modified patch. Thanks, this was really a bug. - Carsten On Oct 17, 2011, at 10:50 AM, Niels Giesen wrote: > > > On Sun, Oct 16, 2011 at 6:43 PM, Nick Dokos wrote: > Niels Giesen wrote: > > > *bump* > > > > Has this one slipped through (as I were posting t

[O] [Accepted] Check marker is valid before use

Patch 994 (http://patchwork.newartisans.com/patch/994/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3Cm1ipnj8mj4.fsf%40gmail.com%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > M

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

Hi again, I can quickly think of two advantages of the late lamented (if only by me) #+BABEL header over using properties. 1. Allowing you to specify multiple buffer-wide options on the same line (keeping things short), in the same colon :syntax as used in a src block header (keeping things

Re: [O] [RFC] Standardized code block keywords

Hi Nick, Tom, Eric and all, Nick Dokos wrote: > Thomas S. Dye wrote: >> Eric Schulte writes: >> [1] I have the same "annoying" feelings with #+SOURCE, #+SRCNAME, #+FUNCTION, #+CALL, #+LOB, and SBE, some of which are interchangeable; some not. I'd prefer deprecating an old f

Re: [O] [RFC] Standardized code block keywords

Hi Torsten, Torsten Wagner wrote: > I tend to #+results: because it fits more to the entire babel syntax. > However, earlier on the mailing list people were pointing out that one > is going to change "results" for a unknown source block (that was the > reason "data" was introduced) and I thin

Re: [O] Asciidoc

Hi Stephen Nelson-Smith writes: > I have a large piece of writing to do, which my publisher wants in > asciidoc. I'd prefer to write in orgmode and export as asciidoc. I used to use asciidoc but much prefer orgmode now. > Is this feasible? Anyone doing this or done this before? Not directl

Re: [O] Patch for bug in adjusting time ranges in Agenda

Hi Carsten Carsten Dominik writes: > I have just checked in a slightly modified patch. I think there is a problem with this checkin. The variable org-agenda-move-date-from-past-immediately-to-today is not defined. Should this be a defcustom somewhere? Debugger entered--Lisp error: (void-variab

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On Fri, Oct 21, 2011 at 10:14 AM, Christian Moe wrote: > Hi again, > > I can quickly think of two advantages of the late lamented (if only by me) > #+BABEL header over using properties. > I also think that keeping the #+BABEL would be a good idea, as it keeps the options for babel separate (as ar

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On 10/21/11 11:12 AM, Rainer M Krug wrote: On Fri, Oct 21, 2011 at 10:14 AM, Christian Moe mailto:m...@christianmoe.com>> wrote: (...) 2. Allowing you to pass multiple buffer-wide arguments with :var. This could make a substantive difference in some applications. The following wil

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On Fri, Oct 21, 2011 at 12:47 PM, Christian Moe wrote: > On 10/21/11 11:12 AM, Rainer M Krug wrote: > >> >> >> On Fri, Oct 21, 2011 at 10:14 AM, Christian Moe > **> wrote: >> > (...) > > 2. Allowing you to pass multiple buffer-wide arguments with :var. >>This

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On 10/21/11 12:59 PM, Rainer M Krug wrote: So, using your above mentioned example, after the first PROPERTY line, euro=1.3795 and SALESTAX not set, while after the second one salestax=.15, and euro is unset? That would be quite bad. That's what I'd expected, but actually, euro is set and sales

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On Fri, Oct 21, 2011 at 1:17 PM, Christian Moe wrote: > On 10/21/11 12:59 PM, Rainer M Krug wrote: > > So, using your above mentioned example, after the first PROPERTY line, >> euro=1.3795 and SALESTAX not set, while after the second one >> salestax=.15, and euro is unset? That would be quite bad

Re: [O] [RFC] Standardized code block keywords

Hello, Eric Schulte writes: > There are currently a number of instances of synonymous keywords when > dealing with code blocks, specifically. > > named code blocks [1] -- "source" "srcname" "function" > calling external functions [2] -- "call" "lob" > named data [3] -- "

[O] Cannot display images inline any more

Hi all, I am no more able to display images inline. I was able when I used Emacs-23-CvsP091103-EmacsW32-1.58.exe. I have for example [[file:c:/img.jpg]] which is exported correctly as html. In Emacs, after "C-c C-x v" Org says: "No images to display inline". Does anybody use Emacs 24.0.90.1

Re: [O] Cannot display images inline any more

On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele wrote: > > I have for example > > [[file:c:/img.jpg]] > > which is exported correctly as html. > > In Emacs, after "C-c C-x v" Org says: "No images to display inline". > > Does anybody use Emacs 24.0.90.1 and is able to display images inline? > My

Re: [O] Cannot display images inline any more

Hi Suvayu and Rainer, suvayu ali wrote: > On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele > wrote: >> >> I have for example >> >> [[file:c:/img.jpg]] >> >> which is exported correctly as html. >> >> In Emacs, after "C-c C-x v" Org says: "No images to display inline". >> >> Does anybody use Emacs

Re: [O] Cannot display images inline any more

Am 21.10.2011 15:33, schrieb Sebastien Vauban: > Hi Suvayu and Rainer, > > suvayu ali wrote: >> On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele >> wrote: >>> >>> I have for example >>> >>> [[file:c:/img.jpg]] >>> >>> which is exported correctly as html. >>> >>> In Emacs, after "C-c C-x v" Org sa

Re: [O] Cannot display images inline any more

Rainer Stengele writes: > Am 21.10.2011 15:33, schrieb Sebastien Vauban: >> Hi Suvayu and Rainer, >> >> suvayu ali wrote: >>> On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele >>> wrote: I have for example [[file:c:/img.jpg]] which is exported correctly as html. >>>

Re: [O] Cannot display images inline any more

> Well, who is telling me "No images to display inline"? Is it Emacs or Org? Should be straight-forward right? How about C-x C-f image.file? --

Re: [O] Cannot display images inline any more

On Oct 21, 2011, at 4:00 PM, Rainer Stengele wrote: > Am 21.10.2011 15:33, schrieb Sebastien Vauban: >> Hi Suvayu and Rainer, >> >> suvayu ali wrote: >>> On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele >>> wrote: I have for example [[file:c:/img.jpg]] which is

Re: [O] "git describe" in version of info file with "make info_git_describe"

Hi, is there an agreement that this is a good patch? I have not followed the discussion. - Carsten On Oct 16, 2011, at 9:12 PM, Michael Brand wrote: > Hi all > > I made a new patch replacing the previous, now considering the > Makefile targets "target" and "help" introduced meanwhile by

Re: [O] outline-demote incorrectly demotes leaf nodes

On Oct 19, 2011, at 5:39 PM, Michael Brand wrote: > Hi Carsten > > On 18.10.2011, at 20:03, Sanjoy Mahajan wrote: >> I do worry about one point, namely that C-c C-> (outline-demote) should still >> work. And it does work in regular outline mode. For example, if I rename my >> test file to c.ot

Re: [O] Cannot display images inline any more => solved

Am 21.10.2011 16:19, schrieb Jambunathan K: > Rainer Stengele writes: > >> Am 21.10.2011 15:33, schrieb Sebastien Vauban: >>> Hi Suvayu and Rainer, >>> >>> suvayu ali wrote: On Fri, Oct 21, 2011 at 2:39 PM, Rainer Stengele wrote: > > I have for example > > [[file:c:/img

Re: [O] outline-demote incorrectly demotes leaf nodes

Hi Michael, Michael Brand writes: > My suggestion is something like > > (define-key org-mode-map [remap outline-promote] 'org-promote-subtree) > (define-key org-mode-map [remap outline-demote] 'org-demote-subtree) I've taken this road and committed the change, thanks for the suggestion. > per

Re: [O] Can't use char ">" in TODO state

Hi Sébastien, "Sebastien Vauban" writes: > I find this behavior not entirely satisfying, even if I can fully accept that > ">" is a forbidden character in the TODO states. For example, we could think > of a warning being generated, or of the state being fully ignored, or ... I agree there is in

Re: [O] property values and timestamps

Hi Skip and Nick, Nick Dokos writes: > Still a proof-of-concept, but better than the first attempt - set > recursive minibuffers locally and use the standard keybinding: > > (defun org-completing-read (&rest args) > "Completing-read with SPACE being a normal character." > (let ((minibuffer-l

Re: [O] org-bibtex org-exp-bibtex tutorial and config needed

Hi Ezequiel, Ezequiel Birman writes: > I am trying to get the most of org-bibtex and org-exp-bibtex. Could > anybody describe briefly his configuration and workflow? Especially with > regards to reftex. What tutorial did you already check? That will help people understand what particular infor

Re: [O] Can't use char ">" in TODO state

Hi, Michael Brand writes: > It works with this patch > http://patchwork.newartisans.com/patch/964 > from Nicolas which I am still using to test it. Has anyone else been using this patch without problems? If so, then Nicolas please apply it. It really simplifies the way headlines are matched i

Re: [O] property values and timestamps

Hi Skip, Skip Collins writes: >> Still a proof-of-concept, but better than the first attempt - set >> recursive minibuffers locally and use the standard keybinding: > > That was easy. I'm looking forward to this making its way into the > main repository. Where else would a recursive minibuffer m

Re: [O] outline-demote incorrectly demotes leaf nodes

Hi Carsten, Carsten Dominik writes: >> permanently built into Org mode (not in org-mode-hook) for these and >> maybe even a few more outline-* bindings to get the incompatible >> outline-* bindings out of the way from within Org mode. >> >> This remap does not affect the bindings in Outline mod

Re: [O] "git describe" in version of info file with "make info_git_describe"

I still have this as a TODO item for review. I'll take a look at it this weekend. -Bernt Carsten Dominik writes: > Hi, > > is there an agreement that this is a good patch? I have not followed the > discussion. > > - Carsten > > On Oct 16, 2011, at 9:12 PM, Michael Brand wrote: > >> Hi al

Re: [O] No updates on git server?

Rainer M Krug writes: > [...] or has org reached a stable state? Is it April fools' day already? :) -- Bastien

[O] [PATCH 1/5] bind org-export-current-backend in generic exporter.

This is needed for org-export-preprocess-string to function correctly. --- contrib/lisp/org-export-generic.el |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index bb42b60..29e90b8 100644 --- a/contri

[O] Patches for org-generic-export

Attached is a set of patches to the org-generic-exporter. They fix a change in the org-preprocess process that means that all uses of the org-generic export facility will crash. They also add rudimentary support for trac wiki and tikiwiki export. Finally, I have removed the HTML exporter from th

[O] [PATCH 4/5] Fixed section-header-prefix for trac wiki.

--- contrib/lisp/org-export-generic.el |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index 15afe6a..5a5af14 100644 --- a/contrib/lisp/org-export-generic.el +++ b/contrib/lisp/org-export-generic.e

[O] [PATCH 5/5] Fix header prefixes for trac wiki.

trac wiki has hard limit on number of headers. Need space before macro characters in trac wiki. Add a couple of TODO comments. --- contrib/lisp/org-export-generic.el |6 -- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/o

[O] [PATCH 2/5] Added trac-wiki and tikiwiki export settings.

--- contrib/lisp/org-export-generic.el | 107 +++- 1 files changed, 93 insertions(+), 14 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index 29e90b8..e3a8680 100644 --- a/contrib/lisp/org-export-generic.el +++ b

Re: [O] [RFC] Standardized code block keywords

> > I disagree with Tom on [1]: it should clearly be "srcname", in analogy > to #+tblname - and also so I don't have to change my files :-} (but see > my question about tblname below). > > I agree on [2] "call". > noted > > I'm confused by [3] so I will say nothing for now, except to ask some > q

Re: [O] [RFC] Standardized code block keywords

t...@tsdye.com (Thomas S. Dye) writes: > Eric Schulte writes: > >>> [1] I have the same "annoying" feelings with #+SOURCE, #+SRCNAME, >>> #+FUNCTION, >>> #+CALL, #+LOB, and SBE, some of which are interchangeable; some >>> not. I'd prefer >>> deprecating an old form when a better one is found. >>

Re: [O] [RFC] Standardized code block keywords

>> I'm confused by [3] so I will say nothing for now, except to ask some >> questions: are we talking about what a human would use to label a piece >> of data for consumption by a block (including perhaps the future >> possibilities of lists and paragraphs that Tom brought up)? what babel >> would

Re: [O] [RFC] Standardized code block keywords

Nicolas Goaziou writes: > Hello, > > Eric Schulte writes: > >> There are currently a number of instances of synonymous keywords when >> dealing with code blocks, specifically. >> >> named code blocks [1] -- "source" "srcname" "function" >> calling external functions [2] -- "call" "lob"

Re: [O] Include does not work when doing org-export-as-org

Carsten Dominik writes: > You are welcome - and I think it might be good in integrate > Nicks function into Org and make it available through the menu > or a key. Indeed -- IIRC the problem is that Nick cannot submit non-tiny patches :( I added Nick's code to Worg/org-hacks.org. Carsten, coul

Re: [O] [RFC] Standardized code block keywords

> > Now, between "srcname" and "source": I'm used to whatever my Yasnippet is > entering for me. That's currently "srcname". I don't have a strong opinion, > though, to choose one over the other, except that I like Nick's argument with > the table analogy. > >> I agree on [2] "call". > > I clearly

Re: [O] org-contacts or bbdb?

> On Fri, 21 Oct 2011 10:21:11 +0800, Eric Abrahamsen > said: EA> As Rasmus mentioned, if you use BBDB you should get version 3, it's EA> significantly better than the previous version. There's a slow movement EA> towards better import/export functions, which I think has been one of EA>

Re: [O] OPatches for org-generic-export

> On Fri, 21 Oct 2011 11:13:24 -0500, "Robert P. Goldman" > said: RPG> Attached is a set of patches to the org-generic-exporter. They fix RPG> a change in the org-preprocess process that means that all uses of RPG> the org-generic export facility will crash. They also add RPG> rudiment

Re: [O] Private flag or property

Karl Voit writes: > Hi! > > I am still in the process of converting (lots!) of old data into > Org-mode format. > > I stumbled over a private-flag PalmOS datebook used to maintain. > > Is there a *common* way of expressing a private flag/property yet? Not that I know of. > > Or is there no pseu

[O] [PATCH 3/5] Kill the HTML exporter.

This is done better in core org-mode. --- contrib/lisp/org-export-generic.el | 41 1 files changed, 0 insertions(+), 41 deletions(-) diff --git a/contrib/lisp/org-export-generic.el b/contrib/lisp/org-export-generic.el index e3a8680..15afe6a 100644 --- a/con

Re: [O] OPatches for org-generic-export

Hi Wes, Wes Hardaker writes: > RPG> Attached is a set of patches to the org-generic-exporter. They fix > RPG> a change in the org-preprocess process that means that all uses of > RPG> the org-generic export facility will crash. They also add > RPG> rudimentary support for trac wiki and tikiwik

Re: [O] Exporting selected tasks (maybe from agenda view) including their body.

Hi Dominik, Dominik Schrempf writes: > Is there a possibility to export tasks including their body (text, > maybe logbook etc.) from the agenda view? Nope. > What I would like to do is the following: I have Tasks with a certain > todo state (e.g. WAITING). I can view all these tasks in an agen

Re: [O] org-protocol and new frames

Hi Tom, Tom Prince writes: > Is there any way to get org-protocol to create a new frame, when it > needs to open a buffer, but otherwise not open one. Can you give a more detailed example? What does your Org protocol look like? Thanks, -- Bastien

Re: [O] OPatches for org-generic-export

On 10/21/11 Oct 21 -12:06 PM, Wes Hardaker wrote: >> On Fri, 21 Oct 2011 11:13:24 -0500, "Robert P. Goldman" >> said: > > RPG> Attached is a set of patches to the org-generic-exporter. They fix > RPG> a change in the org-preprocess process that means that all uses of > RPG> the org-gene

Re: [O] Links to C/C++ source code lines

Hi Rafal, Rafal writes: > I wrote a small hook for creating org-mode links to C/C++ source code lines > in > the form of a regexp so the links stay valid even if the source code changes > > eg. > a source line > while(ptr < ptr_end) > has a link > file:/home/user/src/example.cpp::/whi

Re: [O] OPatches for org-generic-export

> I think also we should try to assemble a single org document with all > kinds of markup that are expected to work, and use that to make tests. > An export facility is actually easy to regression test I just > haven't gotten around to it. Do you know if there is such a document > for one of

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

Christian Moe writes: > Hi again, > > I can quickly think of two advantages of the late lamented (if only by > me) #+BABEL header over using properties. > > 1. Allowing you to specify multiple buffer-wide options on the same > line (keeping things short), in the same colon :syntax as used in a

Re: [O] [RFC] Standardized code block keywords

Hi Eric, Eric Schulte wrote: >> Now, between "srcname" and "source": I'm used to whatever my Yasnippet is >> entering for me. That's currently "srcname". I don't have a strong opinion, >> though, to choose one over the other, except that I like Nick's argument with >> the table analogy. >> >>> I a

Re: [O] [RFC] Standardized code block keywords

"Sebastien Vauban" writes: > Hi Torsten, > > Torsten Wagner wrote: >> I tend to #+results: because it fits more to the entire babel syntax. >> However, earlier on the mailing list people were pointing out that one >> is going to change "results" for a unknown source block (that was the >> reason

Re: [O] org-mac-protocol no remember window and Symbol's function definition is void: caddr from emacs server

Hi David, David Abernethy writes: > Waiting for Emacs... > *ERROR*: Symbol's function definition is void: caddr That's quite weird. > Can anyone spot the cause of the problem please? Sorry, I cannot. (OT comment: I suggest you switch from using remember to using capture.) -- Bastien

Re: [O] org-contacts or bbdb?

Hi Wes and all, Wes Hardaker wrote: >> On Fri, 21 Oct 2011 10:21:11 +0800, Eric Abrahamsen >> said: > > EA> As Rasmus mentioned, if you use BBDB you should get version 3, it's > EA> significantly better than the previous version. There's a slow movement > EA> towards better import/export

Re: [O] [RFC] Standardized code block keywords

Hi Eric and Torsten, Eric Schulte wrote: >> We could open an older file and if it isn't working, we could try >> >> #+PROPERTY: babel-function-set obsolete > > I think that making use of such a feature is almost as onerous as > changing to the new terms (which is a simple search replace, in fact >

Re: [O] [RFC] Standardized code block keywords

So far I have the following. code block names | source | dye | | srcname | dokos | | srcname | moe | | srcname | vauban | | srcname | wagner | | name| goaziou | call lines | call | dye | | call | dokos | | call | moe | | call | vauban | | call | wagner | | call | goaz

Re: [O] Date-centric Clocktable

Hi Rasmus, Rasmus writes: > Is is possible to have a clocktabke with times in the left-most column? > The people I am doing some work for now prefer it that way for unknown > reasons. > > This is an example > > | date | Headline| total | > |

Re: [O] Exporting to Pinboard.in

Hi Aditya, Aditya Mandayam writes: > Could anyone tell me how to do this? Please have a look at Wes generic exporter (in contrib/lisp/org-export-generic.el) which provides a framework for supporting new (simple) export formats. HTH, -- Bastien

Re: [O] [RFC] Standardized code block keywords

Eric Schulte writes: > t...@tsdye.com (Thomas S. Dye) writes: > >> Eric Schulte writes: >> [1] I have the same "annoying" feelings with #+SOURCE, #+SRCNAME, #+FUNCTION, #+CALL, #+LOB, and SBE, some of which are interchangeable; some not. I'd prefer deprecating an old fo

Re: [O] [RFC] Standardized code block keywords

> Just to make it as easy as possible for everyone > Might it be possible to introduce a small flags like "obsolete" and > "stable" (standard) > Old functions, old syntax, etc., might move first to obsolete before > completely removed... > We could open an older file and if it isn't working, we

Re: [O] [RFC] Standardized code block keywords

Hi Eric, Eric Schulte writes: > named code blocks [1] -- "source" "srcname" "function" > calling external functions [2] -- "call" "lob" > named data [3] -- "tblname" "resname" "results" "data" here my votes: [1] -- "srcname" [2] -- "call" [3] -- ? " I would choose ei

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

Eric Schulte wrote: > > > > 2. Allowing you to pass multiple buffer-wide arguments with :var. This > > could make a substantive difference in some applications. The > > following will work: > > > >#+BABEL: :var euro=1.3791 :var salestax=.15 > > > > The following will not, since it tries to s

Re: [O] org-mac-protocol no remember window and Symbol's function definition is void: caddr from emacs server

Bastien wrote: > Hi David, > > David Abernethy writes: > > > Waiting for Emacs... > > *ERROR*: Symbol's function definition is void: caddr > > That's quite weird. > > > Can anyone spot the cause of the problem please? > > Sorry, I cannot. (OT comment: I suggest you switch from using > re

Re: [O] Include does not work when doing org-export-as-org

Bastien wrote: > Carsten Dominik writes: > > > You are welcome - and I think it might be good in integrate > > Nicks function into Org and make it available through the menu > > or a key. > > Indeed -- IIRC the problem is that Nick cannot submit non-tiny > patches :( I added Nick's code to W

[O] Org-mode Standardized Code Block Keywords

I've invited you to be an owner of the Google Moderator series "Org-mode Standardized Code Block Keywords". You can view and edit this series at http://www.google.com/moderator/#16/e=ffe1e

Re: [O] Org-mode Standardized Code Block Keywords

Well…I didn't mean to invite everyone to own it, but rather to invite everyone to vote… :-p Anyway, this should be a good place to tally the votes without filling inboxes. Chris On Oct 21, 2011, at 11:30 AM, chris.m.mal...@gmail.com wrote: > I've invited you to be an owner of the Google Moderat

Re: [O] Current patches to make org-mode run on XEmacs

Hi Michael, thanks for these patches. Next time, could you provide one patch per mail? The patchwork server cannot handle multiple patches and it makes it easier to discuss every patch -- thanks! Some comments below. Michael Sperber writes: > ... are attached. I've run with this for a few w

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On Fri, Oct 21, 2011 at 7:37 PM, Eric Schulte wrote: > Christian Moe writes: > > > Hi again, > > > > I can quickly think of two advantages of the late lamented (if only by > > me) #+BABEL header over using properties. > > > > 1. Allowing you to specify multiple buffer-wide options on the same > >

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

On Fri, Oct 21, 2011 at 8:35 PM, Rainer M Krug wrote: > > > On Fri, Oct 21, 2011 at 7:37 PM, Eric Schulte wrote: > >> Christian Moe writes: >> >> > Hi again, >> > >> > I can quickly think of two advantages of the late lamented (if only by >> > me) #+BABEL header over using properties. >> > >> >

Re: [O] Org-mode Standardized Code Block Keywords

chris.m.mal...@gmail.com writes: > I've invited you to be an owner of the Google Moderator series > "Org-mode Standardized Code Block Keywords". You can view and edit > this series at http://www.google.com/moderator/#16/e=ffe1e I generally feel sad whenever some posts a blob via imgur or pastebin

Re: [O] FYI: Org mode testing framework, Emacs 23 and 22

Hi Eric and David, Eric Schulte writes: > I suppose the next step here would be to talk to Bastien about setting > up such a system on the org-mode server. For the record, I'm all for a server-side setup that will test latest Org on a regular basis. Jason, depending on our server resources, wo

Re: [O] Org-mode Standardized Code Block Keywords

Hi Jambunathan, That is a good point, but I wanted to make the option available. Ignore the Google moderator link if you'd rather the discussion stay on the mailing list. I planned on sending the "results" to the mailing list, perhaps tomorrow, anyhow. Chris On Oct 21, 2011, at 11:43 AM, Jam

[O] [babel] Globally assigning a value to a variable

#+PROPERTY: var myvar="original" * Overview I would like to test a global variable assignment (just done here above) and local ones (on the code block itself). It seems that the global value is not "known". Though, maybe, I don't understand it fully yet. * Test code ** Using the local var #

Re: [O] FYI: Org mode testing framework, Emacs 23 and 22

Hi Bastien, Bastien wrote: > Hi Eric and David, > Eric Schulte writes: > >> I suppose the next step here would be to talk to Bastien about setting >> up such a system on the org-mode server. > > For the record, I'm all for a server-side setup that will test > latest Org on a regular basis. > > Ja

Re: [O] Current patches to make org-mode run on XEmacs

Hi Bastien and Michael, Bastien wrote: > thanks for these patches. Next time, could you provide one patch per > mail? The patchwork server cannot handle multiple patches and it makes > it easier to discuss every patch -- thanks! Just updated Org, and tried to launch my XEmacs 21.5 (beta29) "ga

Re: [O] [RFC] Standardized code block keywords

Eric Schulte writes: >>> I'm confused by [3] so I will say nothing for now, except to ask some >>> questions: are we talking about what a human would use to label a piece >>> of data for consumption by a block (including perhaps the future >>> possibilities of lists and paragraphs that Tom brough

Re: [O] [babel] Globally assigning a value to a variable

Sebastien Vauban wrote: > #+PROPERTY: var myvar="original" > > * Overview > > I would like to test a global variable assignment (just done here above) and > local ones (on the code block itself). It seems that the global value is not > "known". Though, maybe, I don't understand it fully yet. >

Re: [O] [RFC] Standardized code block keywords

Hi Eric, my preferences are: - source for code blocks. I think srcname looks ugly (although not as ugly as tblname). - call - data and results for, well, data and results. With the same semantics as Torsten Wagner suggested, i.e. a source block cannot change the contents of a data block. It

Re: [O] [babel] Globally assigning a value to a variable

Hi Nick, Nick Dokos wrote: > Sebastien Vauban wrote: >> #+PROPERTY: var myvar="original" >> >> * Overview >> >> I would like to test a global variable assignment (just done here above) and >> local ones (on the code block itself). It seems that the global value is not >> "known". Though, maybe

Re: [O] Org-mode Standardized Code Block Keywords

With many people making suggestions and voting It can be a lot of work for someone to collect all of the votes. In fact, I was going to suggest using Doodle for this (http://www.doodle.com/), but Chris was faster with the google moderator. Anyway, if the final result is sent to the list, including

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

Hi, Yes, that works nicely, and should solve Rainer's problem. I haven't been able to think of anything else that can't be handled by properties. And I do think it's a good idea to winnow down the syntax a bit, even if things break. I just like to grumble. :-) Yours, Christian On 10/21/11

Re: [O] [ANN] BREAKING CHANGE -- removing #+BABEL file-wide property lines

It's excellent that now babel understands multiple values in the "var" property (I was one of the people that wanted this), but "There Is One More Thing". Would it be feasible to inherit variables from parent sub-trees? Effectively, I'd like to append new values in lower level sub-trees, but AFA

[O] BUG: Export images to LaTeX

Hi List, I've run into a strange problem with the latest org pull. Exporting inlined images with the LaTeX exporter works or not depending on whether I include org-jsinfo in org-modules(!). This is with emacs -q on the 24.0.90.1 emacs recent release. Can someone please try to reproduce this to

Re: [O] Current patches to make org-mode run on XEmacs

Hi Michael, I have checked these in, with the following exceptions: - Somewhere you have a call to `org-ref', I guess this must be `org-re' - The special hunk you are mentioning is not longer in org.el, I guess it was removed somehow in some other commit... Hope this makes XEmacs run smoothly

Re: [O] Recurring events with exceptions

On Wed, Oct 19, 2011 at 6:02 AM, Eric S Fraga wrote: > Yes, I have been informed that we are moving to Outlook/exchange in the > new year, something I am dreading...  Matthieu Lemerre, on this list > back in late June (Message-ID: <871uygg1fs@free.fr>), posted a > (partial?) solution that help

Re: [O] Private flag or property

Hi Eric! * Eric S Fraga wrote: > Karl Voit writes: > >> Is there a *common* way of expressing a private flag/property yet? > > Not that I know of. OK. >> Or is there no pseudo-standard and I should stick to my «:PRIVATE: >> True» property I am thinking of? (Is there a necessity for the >> «Tru

[O] Source blocks for tiny snippets

Hi everyone, I was wondering what people do when they need to put a few (1 or 2) lines of code snippets in org files? I like the syntax highlighting one gets in an org buffer and in HTML export with code blocks. Is there some work around other than have code blocks for every line I want to include

Re: [O] Patch for bug in adjusting time ranges in Agenda

Same here. By the way, you don't necessarily have to mark the patch as a TINYCHANGE: I have signed the papers with the FSF, but I just have problems updating http://orgmode.org/worg/org-contribute.html. (problem is: "error: unable to create temporary sha1 filename ./objects/3e: Permission denied"

Re: [O] Patch for bug in adjusting time ranges in Agenda

On 22.10.2011, at 08:00, Niels Giesen wrote: > Same here. > > By the way, you don't necessarily have to mark the patch as a TINYCHANGE: I > have signed the papers with the FSF, but I just have problems updating > http://orgmode.org/worg/org-contribute.html. > > (problem is: "error: unable to

Re: [O] Patch for bug in adjusting time ranges in Agenda

On 21.10.2011, at 10:54, Christian Egli wrote: > Hi Carsten > > Carsten Dominik writes: > >> I have just checked in a slightly modified patch. > > I think there is a problem with this checkin. The variable > org-agenda-move-date-from-past-immediately-to-today is not defined. > Should this be

Re: [O] direct link to mails in gmail

> > Since any mail can be found under the All label by definition the > simplest solution is extracting the message id from the end of > the current url and then creating a new url pointing to All. > This URL should always work unless the mail is deleted: > > https://mail.google.com/mail/?shva=1#al