Re: [O] [ANN][RFC] org-odt.texi/org-odt.pdf preview (was Re: Org-odt table format)

Hi, Great, I'll just wait for your revised draft so we don't get versions mixed up. Yours, Christian On 10/28/11 6:19 AM, Jambunathan K wrote: I will work on your suggestions and circulate a revised draft shortly. Once an initial org.texi gets in to the repo, improving it would be a breeze.

Re: [O] Feature Request: Disable auto-insert-mode exporting

On 28.10.2011, at 06:49, Darlan Cavalcante Moreira wrote: > > Thanks Nick, > > You right, the master file question comes from auctex. But with your code > it's simple to add the relevant variable to solve the issue. The final > function is > --8<---cut here---start--

Re: [O] "Clocktable summary at ..." line not showing up right in export

Herbert Sitz writes: Hi, Herbert, > I'm exporting exporting-to-what ? > a file with a clocktable and the first line of the Clocktable > shows up with no date or time info, just: > > "Clock summary at" [followed by nothing] > | Headline| Time | > |-

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

Michael Brand writes: > If set-version.pl would be obsolete my patch would be much shorter and > I would use something even more portable than perl to change the > version in /tmp/org.texi like the POSIX/SUS ed command, used inline in > the Makefile. Would you agree? I don't know if it is still u

[O] [PATCH] Adding features to contrib/lisp/org-collector.el (propview)

Hi there, I did a small patch for org-collector. Here are the changes : - Adding a :colnames property, allowing to give the column names (instead of displaying the function used to populate the table) - Adding a :noquote property, allowing to remove the double quotes around strings I hope some

Re: [O] Makefile restructuring

Is someone still tracks this thread: I'm still working on the fork, recent changes have been the elimination of the dependencies. I've found no simple way to automatically generate them and even then it would have been really difficult to keep Emacs from picking up stale byte-compiled files. Whi

Re: [O] Elisp programming style

On Thu, 27 Oct 2011 20:03:22 +0200 Thorsten wrote: > Hi List, > doing some Elisp programming (in an orgmode context) recently, the > following question with regards to the 'accepted programming style' for > Elisp concerned me: > > How independent and self-sustained should helper functions be? >

[O] Columns view for org-tags-view

Hello! First of all I want say thank you for great emacs mode, which I using for planning my life and job. Org-mode is the best! I used 7.7 version with some patches from development version. For example, patch

[O] How to install contributions to org-mode such as org-contacts?

Hi, I downloaded and successfully installed the latest version org-mode (M-x org-version shows 7.7). I was hoping to get org-contacts with it, too, but when putting (require 'org-contacs) in .emacs, I obtain: Warning (initialization): An error occurred while loading `/Users/mhofert/.emacs': F

Re: [O] How to install contributions to org-mode such as org-contacts?

On 28 October 2011 14:07, Marius Hofert wrote: > Hi, > > I downloaded and successfully installed the latest version org-mode (M-x > org-version shows 7.7). I was hoping to get org-contacts with it, too, but > when putting (require 'org-contacs) in .emacs, I obtain: > > Warning (initialization):

[O] export subtree-specific headers?

I want to use particular LaTeX headers when I export a subtree. Is there a way to do this? (EXPORT_TEXT is close, but I need stuff in the LaTeX preamble, not in the document itself.) --Colin

Re: [O] Columns view for org-tags-view

Hello Ilya, correct analysis, thanks, this is fixed in the git repo. - Carsten On 28.10.2011, at 12:59, Ilya Zonov wrote: > Hello! > > First of all I want say thank you for great emacs mode, which I using for > planning my life and job. Org-mode is the best! > > I used 7.7 version with some

Re: [O] How to install contributions to org-mode such as org-contacts?

Dear Brian, thanks a lot. It's working now. I followed the instructions, but (erroneously) thought that the copying to some folder and using load-path is not required. Cheers, Marius On 2011-10-28, at 14:23 , Brian van den Broek wrote: > On 28 October 2011 14:07, Marius Hofert wrote: >> Hi

[O] [PATCH] Fix holidays symbol in org-class

* lisp/org-agenda.el: (org-class): Fix holidays symbol in org-class. This was resulting in an "Bad sexp..." warning. --- lisp/org-agenda.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el index 66686f9..cbf8407 100644 --- a/lisp/

[O] [Accepted] Fix holidays symbol in org-class

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

Re: [O] Elisp programming style

Štěpán Němec writes: > On Thu, 27 Oct 2011 20:03:22 +0200 > Thorsten wrote: > >> Hi List, doing some Elisp programming (in an orgmode context) >> recently, the following question with regards to the 'accepted >> programming style' for Elisp concerned me: >> >> How independent and self-sustained s

[O] OT: collage of scripts [was: Re: table alignment failed for Asian char

Jambunathan wrote: > Book seems like an interesting read. For me to go from frame message -> > outer message -> inner message, I think I need to read the whole book > and not just a fragment of it > > Just curious, is the book a standard regular or supplementary reading > for courses in US. If yes

Re: [O] Elisp programming style

Thorsten wrote: > Štěpán Němec writes: > > > On Thu, 27 Oct 2011 20:03:22 +0200 > > Thorsten wrote: > > > >> Hi List, doing some Elisp programming (in an orgmode context) > >> recently, the following question with regards to the 'accepted > >> programming style' for Elisp concerned me: > >> > >

Re: [O] [PATCH] Adding features to contrib/lisp/org-collector.el (propview)

Hi Jonathan, Jonathan BISSON writes: > I did a small patch for org-collector. Thanks for this -- can you resend the patch by attaching it, instead of inserting it in the body of the email? It is not readable here. Thanks! -- Bastien

Re: [O] Text preceding first headline is well/not exported

Hi Sébastien, "Sebastien Vauban" writes: > But, anyway, be it nil or not, I'd expect the behavior to be the same in both > exporters. Me too :) > Can someone confirm this behavior? I cannot reproduce this behavior with your test file. Can you reproduce this with emacs -Q? -- Bastien

Re: [O] Elisp programming style

Thorsten writes: >> Too bad you didn't give any concrete examples. > > The problem can be described easily: > > problem-specific helper-funcions (some redundancy avoided) > ,--- > | (defun main-function (args)

Re: [O] Elisp programming style

> > The problem can be described easily: > > problem-specific helper-funcions (some redundancy avoided) > ,--- > | (defun main-function (args) > | (let ((var (assoc :key1 args))) ; extracting var once > | ...

Re: [O] [PATCH] Adding features to contrib/lisp/org-collector.el (propview)

Hi Jonathan, This does sound useful. Unfortunately your email client seems to have mangled the patch, could you resend with the patch attached rather than pasted inline? Thanks -- Eric Jonathan BISSON writes: > Hi there, > > > I did a small patch for org-collector. > > Here are the changes :

Re: [O] Elisp programming style

Tassilo Horn writes: > Thorsten writes: > >>> Too bad you didn't give any concrete examples. >> >> The problem can be described easily: >> >> problem-specific helper-funcions (some redundancy avoided) >> ,--- >> | (defun main-function (arg

Re: [O] [PATCH] Adding features to contrib/lisp/org-collector.el (propview)

On 10/28/2011 04:32 PM, Bastien wrote: > Hi Jonathan, > > Jonathan BISSON writes: > >> I did a small patch for org-collector. > > Thanks for this -- can you resend the patch by attaching > it, instead of inserting it in the body of the email? It > is not readable here. > > Thanks! > Here

Re: [O] Bug? in the latest revision of org

Hi Paul, Paul Sexton writes: > The code needs to change to something like: > >((and org-return-follows-link > (let ((tprop (get-text-property (point) 'face))) > (or (eq tprop 'org-link) > (and (listp tprop) (memq 'org-link tprop) thanks for the analysis an

Re: [O] Patch: Mark org-diary-class as obsolete and skip entries on holidays in org-class

Achim Gratz writes: > This change introduced a new warning: > > In end of data: > org-agenda.el:8536:1:Warning: the function `calendar-check-holidays' is not > known to be defined. Fixed, thanks. -- Bastien

Re: [O] [PATCH] Adding features to contrib/lisp/org-collector.el (propview)

Jonathan BISSON writes: > Here it is, Thanks for the quick reply -- since Eric also replied, I let him decide about this! Best, -- Bastien

Re: [O] [PATCH] org-crypt: when running org-decrypt-entry, only run auto-save-mode check if on an encrypted entry

Hi Pieter, Pieter Praet writes: > BTW, my FSF copyright assignment is completed (assignment number > #705083) so I should probably be added to the list of signees [1]. I just added you -- thanks for the reminder! -- Bastien

Re: [O] Bug: [testing] missing dependency [7.7 (release_7.7.340.ga342)]

Hi Dave, Dave Abrahams writes: >> `org-test-load' works fine here without requiring the ESS package. >> >> Can you check again? > > I probably don't have time, sorry. Did you try this with a fresh > emacs -Q? Yes -- and there is no ESS dependancy, unless I missed something. Best, -- Bastie

Re: [O] Byte compiler warnings

Hi Andrei, Andrei Jirnyi writes: > A few warnings from Emacs 23.2.1 here: Thanks. I fixed most of them. > Compiling file /home/xx/.emacs.d/elpa/org-20111024/ob-C.el at Mon Oct > 24 18:20:36 2011 > Entering directory `/home/xx/.emacs.d/elpa/org-20111024/' > > Compiling file /home/

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

Hi Rafal, Rafal writes: > Bastien altern.org> writes: > >> Looks nice, thanks. Just wondering: are you aware of the "A.3 Adding >> hyperlink types" section in the manual? You core uses advice instead >> of the `org-add-link-type' function -- is that on purpose? > > No, I missed that paragrap

Re: [O] org-lrn

Hi Johannes, Johannes Hess writes: > Hah, of course i did not know about org-drill, that one looks pretty > good. :) You just need to make org-lrn better than org-drill now :) In any case, if you feel like org-lrn should be listed here http://orgmode.org/worg/org-contrib/index.html please

Re: [O] Bug: [testing] missing dependency [7.7 (release_7.7.340.ga342)]

Bastien writes: > Hi Dave, > > Dave Abrahams writes: > >>> `org-test-load' works fine here without requiring the ESS package. >>> >>> Can you check again? >> >> I probably don't have time, sorry. Did you try this with a fresh >> emacs -Q? > > Yes -- and there is no ESS dependancy, unless I miss

Re: [O] [PATCH] Stealth org-link-search

Hi Nicolas, Nicolas Goaziou writes: > I don't think there is a decent way to search for a link destination > without modifying buffer's visibility around match. This can be very > annoying when resolving links in background. Indeed -- I've just applied this patch, thanks for it! -- Bastien

Re: [O] Elisp programming style

Eric Schulte writes: Hi Eric, > Hmmm, this looks suspiciously like the case in some Babel functions :) well ... ;) > in which we originally has instances of the first style and then had to > manually transition to the second. IMO the first is very poor form, the > variables are technically "

Re: [O] Elisp programming style

Nick Dokos writes: > Not a problem - you can't predict the future. You do the best you can > with your current knowledge. You can always refactor in the future: > that's one reason that having the source code around is important. When > you refactor, you may be cursing the original author for th

Re: [O] Elisp programming style

Tassilo Horn writes: > And I wouldn't tell multiple similar let-bindings duplicate code. I have to get used to that, at first sight it looks like there is redundancy everywhere. But its more from the Java perspective, from the more functional perspective it makes sense. cheers -- Thorsten

Re: [O] Feature Request: Disable auto-insert-mode exporting

Thanks Carsten, That's great. I tested without the advice it worked as expected for both exporters. I would be surprised if anyone could give a reason to keep the AUCTeX query or the auto-insert stuff, at least without modifying org-export. That's because the export process replaces anything in

Re: [O] Feature Request: Disable auto-insert-mode exporting

Darlan Cavalcante Moreira wrote: > > Thanks Carsten, > That's great. > > I tested without the advice it worked as expected for both exporters. > > I would be surprised if anyone could give a reason to keep the AUCTeX query > or the auto-insert stuff, at least without modifying org-export. That

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

The attached patch implements these changes, please see the patch comment as it contains all of the pertinent information. If any brave volunteers would be willing to test this patch locally before I apply it to the Org-mode git repository that would be greatly appreciated. Thanks to the test sui

Re: [O] Feature Request: Disable auto-insert-mode exporting

On 28.10.2011, at 18:45, Nick Dokos wrote: > Darlan Cavalcante Moreira wrote: > >> >> Thanks Carsten, >> That's great. >> >> I tested without the advice it worked as expected for both exporters. >> >> I would be surprised if anyone could give a reason to keep the AUCTeX query >> or the auto-

Re: [O] OT: collage of scripts [was: Re: table alignment failed for Asian char

* One of my favorite Hofstadter books is: "Le Ton beau de Marot: In Praise of the Music of Language (ISBN 0-465-08645-4), published by Basic Books in 1997, is a book by Douglas Hofstadter in which he explores the meaning, strengths, failings, and beauty of translation." ** "Translation between fra

Re: [O] [PATCH] Adding features to contrib/lisp/org-collector.el (propview)

Bastien writes: > Jonathan BISSON writes: > >> Here it is, > > Thanks for the quick reply -- since Eric also replied, I let > him decide about this! > [Eric] touches his nose only to realize it is already too late... Hi Jonathan, Sorry to ask for yet another re-submission, but would you mind

[O] Patch to customize output of tables in LaTeX exporter.

Dear list, Attached is a patch that allows some customization of tables in LaTeX export. It adds three new customizable with default values: org-export-latex-tables-tstart : nil org-export-latex-tables-hline : "\\hline" org-export-latex-tables-tend : nil These variables allows users to

Re: [O] Elisp programming style

Perhaps ,--- | (defun main-function (args) | (let ((var (assoc :key1 args))) ; extracting var once | ... | (helper-function1 ... var ...) ; inside let

[O] emacs 24.1 and org compatibility

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

The attached updated patch fixes a bug in the original. >From 0e43d59ee8d46a63f86780a502de726271bc39de Mon Sep 17 00:00:00 2001 From: Eric Schulte Date: Fri, 28 Oct 2011 10:44:21 -0600 Subject: [PATCH] removing code block, results and call-line synonyms -- BREAKING CHANGE Following a round of on

[O] Problem after updating org: C-c a a broken

Hello all, just pulled from git. When I type C-c a a to pull up the agenda, I get the error shown below. This used to work prior to the update. Org version is 7.7, pulled 5 min ago on emacs 23.3.1. Help please, can't access my agenda anymore :( Thanks Markus Debugger entered--Lisp error: (wr

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

Eric Schulte wrote: > The attached updated patch fixes a bug in the original. > Minor problem in applying: , | $ git apply ~/Mail/inbox/724 | /home/nick/Mail/inbox/724:671: trailing whitespace. | #+name: | /home/nick/Mail/inbox/724:599: new blank line at EOF. | + | warning: 2 lines add wh

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

Nick Dokos writes: > Eric Schulte wrote: > >> The attached updated patch fixes a bug in the original. >> > > Minor problem in applying: > > , > | $ git apply ~/Mail/inbox/724 > | /home/nick/Mail/inbox/724:671: trailing whitespace. > | #+name: > | /home/nick/Mail/inbox/724:599: new blank li

Re: [O] Problem after updating org: C-c a a broken

Markus Heller wrote: > Hello all, > > just pulled from git. > > When I type C-c a a to pull up the agenda, I get the error shown below. > > This used to work prior to the update. > > Org version is 7.7, pulled 5 min ago on emacs 23.3.1. > > Help please, can't access my agenda anymore :( > >

Re: [O] Problem after updating org: C-c a a broken

Nick Dokos writes: > Markus Heller wrote: > >> Hello all, >> >> just pulled from git. >> >> When I type C-c a a to pull up the agenda, I get the error shown below. >> >> This used to work prior to the update. >> >> Org version is 7.7, pulled 5 min ago on emacs 23.3.1. >> >> Help please, can

Re: [O] Problem after updating org: C-c a a broken

Markus Heller wrote: > Nick Dokos writes: > > > Markus Heller wrote: > > > >> Hello all, > >> > >> just pulled from git. > >> > >> When I type C-c a a to pull up the agenda, I get the error shown below. > >> > >> This used to work prior to the update. > >> > >> Org version is 7.7, pulled 5

Re: [O] Problem after updating org: C-c a a broken

Markus Heller writes: > Nick Dokos writes: > >> Markus Heller wrote: >> >>> Hello all, >>> >>> just pulled from git. >>> >>> When I type C-c a a to pull up the agenda, I get the error shown below. >>> >>> This used to work prior to the update. >>> >>> Org version is 7.7, pulled 5 min ago on

Re: [O] Problem after updating org: C-c a a broken

Markus Heller wrote: > Hm, so ok, restarting emacs actually solved it. > > Kinda weird, because I never had to do this when updating org (I don't > compile the sources, I just do C-c C-x !). > > Seems a bit odd to me but it's working again so I'm happy :) > > I apologize for the noise. > >

Re: [O] Problem after updating org: C-c a a broken

Nick Dokos wrote: > Markus Heller wrote: > > > > Hm, so ok, restarting emacs actually solved it. > > > > Kinda weird, because I never had to do this when updating org (I don't > > compile the sources, I just do C-c C-x !). > > > > Seems a bit odd to me but it's working again so I'm happy :)

Re: [O] Problem after updating org: C-c a a broken

Hi Nick and Markus, Nick Dokos wrote: > Nick Dokos wrote: >> Markus Heller wrote: >> >> > Hm, so ok, restarting emacs actually solved it. >> > >> > Kinda weird, because I never had to do this when updating org (I don't >> > compile the sources, I just do C-c C-x !). >> > >> > Seems a bit odd

Re: [O] emacs 24.1 and org compatibility

Tassilo Horn writes: > Michael Bach writes: > >> [nothing] > > I agree with all that you've said. :-) > Hm. Since my subject line is the only thing I said, that was easy. :-) So for the actual issue: After pulling emacs from bzr and org mode from git today, org-capture failed with error: vo

[O] Evaluation on export has stopped working, org-export-blocks hook was culprit?

I had a system that was working fine, but it seems to have stopped processing babel source blocks on export. I've switched between Org 7.4 and 7.7 on Win32 Emacs 23.1 and both have the problem. As I was writing this up I discovered that the problem was caused by a line I had added to my .emacs.

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

And, revising the files before Worg updates the Org-mode it uses will break them, right? Tom Nick Dokos writes: > I'm trying to add a note to Worg hacks but before I push, I use my local > org setup to publish Worg locally and take a look at it (not entirely reliable > since my org version is u

Re: [O] [odt] Support for annotations/comments

Jambunathan K gmail.com> writes: > > I needed an excuse for adding support for annotations. Exporting the > below org will produce the attached odt/pdf files. Note that the pdf > file is produced by LibreOffice pdf export. > > Annotations is a ODT only feature right now and will not work with ot

[O] Bug in pdf export of tables with latest development version

I'm having problems exporting to pdf with a source block that generates a table result. If the table has enough rows to get to bottom of page, it seems, the rest of the table output disappears/is discarded and the pdf document skips to text after the source block output. Everything works fine wit

Re: [O] Bug in pdf export of tables with latest development version

Herbert Sitz gmail.com> writes: > I'm having problems exporting to pdf with a source block that generates a table > result. If the table has enough rows to get to bottom of page, it seems, the > rest of the table output disappears/is discarded and the pdf document skips to > text after the sou

Re: [O] Elisp programming style

[...] >> Would that be considered bad style from the original author, or is that >> up to personal choice and not considered a problem? >> > > Not a problem - you can't predict the future. You do the best you can > with your current knowledge. You can always refactor in the future: > that's one

Re: [O] Bug in pdf export of tables with latest development version

Herbert Sitz wrote: > Herbert Sitz gmail.com> writes: > > I'm having problems exporting to pdf with a source block that generates a > table > > result. If the table has enough rows to get to bottom of page, it seems, > the > > rest of the table output disappears/is discarded and the pdf docum

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

Thomas S. Dye wrote: > And, revising the files before Worg updates the Org-mode it uses will > break them, right? Yup - they got to be done at the same time. Nick > > Tom > > Nick Dokos writes: > > > I'm trying to add a note to Worg hacks but before I push, I use my local > > org setup to

Re: [O] Bug in pdf export of tables with latest development version

Nick Dokos hp.com> writes: > > You probably should try using a long table: section 12.6.4 in the manual > or evaluate > > (info "(org) Tables in LaTeX export") > > Nick > Nick --- Thanks, that did the trick. Sorry to trouble you, upgrading to 7.7 development version and could have sworn