Re: [O] Bug: Org-Babel Mode R Plot Output to LaTeX File [Babel] [7.5]
Hi Sebastien, "Sebastien Vauban" writes: > Shouldn't it more appropriate to give that var such a default: > > "width=0.9\\linewidth" > > 10em seems to me much to small in *all* cases, no? Yes, you're right. I've just applied a patch changing the default to what you suggest. Thanks! -- Bastien
[O] Time calculation: vsum?
Hi, Time calculations don't seem to work with vsum (or vmean). |Time | |-| | 1:06:00 | | 0:52:30 | | 2:00:00 | |-| | 3 | #+TBLFM: @5$1=vsum(@I..@II);T Am I doing something wrong? Could this be made to work? Yours, Christian
Re: [O] Makefile restructuring
Branch is rebased onto current master. I'm now using a sub-make for ./lisp. Compiling and making the org-install.el in ./lisp rather than from toplevel also ensures that both the new (Emacs24) and old autoload.el produces the correct result. It is now possible to copy default.mk to local.mk and then alter the definitions in local.mk — make will automatically use the definitions in local.mk if it is present. 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] ODT Charset/Encoding issues (was question about ODT export behavior)
Renzo > I just want to add one point that I did not find in the org-manual. I tested > some of my org-files and exported them to the OpenOffice format. When I tried > to > open these documents in OpenOffice, they were corrupt and could not be opened. > > I soon found out why. If you want to export an org-mode file to .odt, you need > to explicitly set the file encoding to UTF-8 (I usually use iso-8859-1 > encoding > for my files), like: > #-*- mode: org; coding: utf-8; -*- > After that OpenOffice could open the files without any problems. I use English for communication and I have to admit that I have zero understanding of things like character sets, encodings etc. Thanks for the above note. I surely see is a bug but my poor understanding prevents me from quantifying it further. Could you please send me a minimal iso-8859-1 test.org file and the associated corrupted test.odt file? I will look in to this issue. 1. Do you have any specific requirement on how the component xml files be encoded? A cursory look at the odt exporter suggests that it could actually be emitting xml files in iso-8859-1 format while wrongly claiming UTF-8 encoding as below --8<---cut here---start->8--- --8<---cut here---end--->8--- 2. Should the xml file be always ejected in UTF-8 irrespective of how the original Org file is encoded. [Notes to Self] [Notes from odbook] Para 3 of http://books.evc-cit.info/odbook/apa.html#appc-11-fm2xml says --8<---cut here---start->8--- OpenDocument files are always encoded in UTF-8. --8<---cut here---end--->8--- Para 2 of http://books.evc-cit.info/odbook/apa.html#xml-other-char-encodings-section says --8<---cut here---start->8--- XML 1.0 allows a document to be encoded in any character set registered with the Internet Assigned Numbers Authority (IANA). European documents are commonly encoded in one of the ISO Latin character sets, such as ISO-8859-1. Japanese documents commonly use Shift-JIS, and Chinese documents use GB2312 and Big 5. --8<---cut here---end--->8--- Para 4 of http://books.evc-cit.info/odbook/apa.html#xml-other-char-encodings-section says --8<---cut here---start->8--- XML processors are not required by the XML 1.0 specification to support any more than UTF-8 and UTF-16, but most commonly support other encodings, such as US-ASCII and ISO-8859-1. --8<---cut here---end--->8--- [Notes from XMLmind XSL-FO Converter] XFC supports outputting of content.xml and styles.xml in UTF-8 as well as ISO-8859-1. http://xml.web.cern.ch/XML/www.xmlmind.com/xfc_perso_java-4_4_0/doc/user/command_line_java.html says , [see outputEncoding section] | For OpenDocument output (.odt), this option specifies the encoding of | XML content (files styles.xml and content.xml) in the output | document. All encodings available in the current JVM are supported. The | option value may be either the encoding name (e.g. ISO8859_1) or the | charset name (e.g. ISO-8859-1). The default value is UTF8. ` --
[O] Broken link on Worg
Aloha all, A link in the An Babel Demo section of http://orgmode.org/worg/org-contrib/babel/uses.html appears to have broken. I'm not sure why and don't know how to fix it. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Bug: Org-Babel Mode R Plot Output to LaTeX File [Babel] [7.5]
Hi Eric and Stephen, Eric Schulte wrote: >> why is the default width 10em for latex graphics? (Or at least, how can >> I change this default? > > See the `org-export-latex-image-default-option' variable. > > Generally in such situation you can run the `describe-variable' function > and tab-complete your way to the name of the relevant variable. The > `apropos' function is also useful for suss out this sort of information. Shouldn't it more appropriate to give that var such a default: "width=0.9\\linewidth" 10em seems to me much to small in *all* cases, no? Best regards, Seb -- Sebastien Vauban
Re: [O] Formal description of Org files
suvayu ali wrote: > On Sat, Jul 16, 2011 at 7:09 PM, Nick Dokos wrote: > > There was a discussion about this on the list a few months ago, but I > > can't get to search.gmane.org to find the thread atm, although I can get > > to news.gmane.org: is that me or is gmane's search on the fritz? > > > > I think you are replying to that same thread. > Right you are! I blitzed on the fact that Marcelo was replying in that thread: I thought it was a new one. Sorry about the noise, Nick
Re: [O] Formal description of Org files
On Sat, Jul 16, 2011 at 7:09 PM, Nick Dokos wrote: > There was a discussion about this on the list a few months ago, but I > can't get to search.gmane.org to find the thread atm, although I can get > to news.gmane.org: is that me or is gmane's search on the fritz? > I think you are replying to that same thread. And about Gmane search, maybe try something like this Google trick: "Formal description of Org files" site:http://lists.gnu.org/archive/html/emacs-orgmode/ > Nick > -- Suvayu Open source is the future. It sets us free.
Re: [O] bulk relative time shift (in org file)?
Bastien writes:
> My Gnus .overview has been corrupted and I lost track of the question.
> Can you restate it shortly here?
,[ Original request as short as I can get it ]
| Michael is looking for a way to "bulk re'timestamp'" items
| relativ to the timestamp the item has currently.
| This should work on region, subtree etc.
| He wants to avoid cloning and would prefer doing this
| directly in the file, not with the agenda.
`
Example:
--8<---cut here---start->8---
Before:
* Project A
** Task A
SCHEDULED: <2011-07-16 Sa>
** Taks B
SCHEDULED: <2011-07-19 Di>
** Task C
SCHEDULED: <2011-07-21 Do>
After "Bulk re-timestamp schedule +7d scope subtree" :
* Project A
** Task A
SCHEDULED: <2011-07-23 Sa>
** Taks B
SCHEDULED: <2011-07-26 Di>
** Task C
SCHEDULED: <2011-07-28 Do>
--8<---cut here---end--->8---
I said that the agenda seems to me the easiest way to do it.
>But the agenda is in many ways another interface to the org file.
(i.e. Agenda can be more than a calendar like presentation)
>And it supports limiting to: Region, Subtree, etc.
out of the box!
Prototype bulkshift by date:
#+begin_src emacs-lisp
(defun my-org-bulkshift-deadline ()
"Shift the deadline of marked items in the agenda by
n days. Set n via Prefix Arg!"
(interactive "P")
(let* ((marker (or (org-get-at-bol 'org-hd-marker)
(org-agenda-error)))
(buffer (marker-buffer marker)))
(with-current-buffer buffer
(save-excursion
(save-restriction
(widen)
(goto-char marker)
(org-back-to-heading t)
(when (and (org-entry-get (point) "DEADLINE") ; There is a deadline
there
(numberp current-prefix-arg)) ; And
current-prefix-arg is a number
(re-search-forward org-deadline-time-regexp)
(org-timestamp-change current-prefix-arg 'day)))
#+end_src
Use: "M-15 B f my-org-bul"
in the agenda (limited to what you want, then marking the items.)
> I did only minimal testing so far, but the prototype
> seems to work and my-org-bulkshift-scheduled, -plain et al. can be easily
> added and/or combined into one function.
Memnon "This is not really short :(" Anon
[O] Searching the org list (was: Formal description of Org files)
Nick Dokos writes: > There was a discussion about this on the list a few months ago, but I > can't get to search.gmane.org to find the thread atm, although I can get > to news.gmane.org: is that me or is gmane's search on the fritz? I had some trouble with gmane search for days, too. Alternatives: http://www.mail-archive.com/emacs-orgmode@gnu.org/ http://lists.gnu.org/archive/html/emacs-orgmode/ Memnon
Re: [O] Formal description of Org files
Nick Dokos writes: > There was a discussion about this on the list a few months ago, but I > can't get to search.gmane.org to find the thread atm, although I can get > to news.gmane.org: is that me or is gmane's search on the fritz? Looks like gmane search is down, I can't use it either. -- Bastien
Re: [O] bulk relative time shift (in org file)?
Hi Memnon, Memnon Anon writes: >>> Any guidance? >> Oh, guidance would be great: I'm curious what others will propose. > > Anyone? > This question might have gone down in the prerelease turmoil ... My Gnus .overview has been corrupted and I lost track of the question. Can you restate it shortly here? Thanks! -- Bastien
Re: [O] [PATCH]
Hi Evgeny, thanks a lot for the analysis and the patch, I just applied it. If you can, please use git format-patch when submitting patch and make sure the subject line of the email containing the patch is a short description of it -- it will help me a lot. Best, -- Bastien
Re: [O] error writing agenda view to html file
Jambunathan K writes: > +(defface org-default > + (org-compatible-face 'default nil) > + "Face used for default text." > + :group 'org-faces) > > authorBastien Guerry >Wed, 6 Jul 2011 15:25:29 + (17:25 +0200) > committer Bastien Guerry >Wed, 6 Jul 2011 15:25:29 + (17:25 +0200) > commit7a88eaec295d50a6e27cc1d6b6f1a725ace01076 > tree 91e803908793a91bb614a775c599dda172c72385tree | snapshot > parentc6b22dee33fa418b344fa68bf36bb496db473a89 > > Revback your commit to c6b22d level and see if the problem persists. Yes, doing this will also be useful, on top of letting us know how to reproduce the problem. Thanks, -- Bastien
Re: [O] Formal description of Org files
Bastien wrote: > Hi Marcelo, > > Marcelo de Moraes Serpa writes: > > > I'm creating a web app that interacts with orgmode files and allows > > you to edit orgmode files on the browser. The edit part is not done. > > Wow, this would be a really useful tool. Can't wait to test this! > > > I'm quite good at Javascript, and I wouldn't mind hacking something > > akin to orgmode elisp code and this will be what I'll do if > > everything else fails, but wouldn't using a grammar be a cleaner and > > more elegant solution? > > Can you tell more about what you mean by "grammar"? > A formal grammar of some sort I presume: BNF or EBNF. > Back in february, at FOSDEM, someone asked for a description of the > org-mode format specification. This is still something that needs to be > done. Any stab at this (on Worg) would be really nice. You can start > anywhere (headlines, TODO keywords, etc.) > > If the "grammar" needs to be described in a specific format (more than > just a formal description of the various syntactic elements of an Org > file), let us know. > There was a discussion about this on the list a few months ago, but I can't get to search.gmane.org to find the thread atm, although I can get to news.gmane.org: is that me or is gmane's search on the fritz? Nick
Re: [O] Worg update
Bastien wrote: > Hi Nick, > > Nick Dokos writes: > > > Did the handling of ``#+INCLUDE:'' change recently? There seem > > to be quoting problems because of lines like this: > > > > #+include: "theindex.inc" > > > > in the file ``theindex.org'' and > > > > #+INCLUDE: "../code/awk/ical2org.awk" src sh > > > > in org-tutorials/org-google-sync.org, where the quotes are not > > stripped - they are taken as part of the filename, and eventually when > > the filename is checked against the cache of last mode times, the name > > includes the quotes . That function then blows up because there is no > > file called ``"theindex.org"'' > > This should have been fixed around midday -- please double-check and > report any problem. > Indeed: problem fixed. Thanks, Nick
Re: [O] error writing agenda view to html file
Hi Rainer, Rainer Stengele writes: > In agenda view doing a C-x C-w produces a face related error. I cannot reproduce this. C-x C-w works fine in the agenda views I could test. > Can somebody help me out finding the issue in this debug message? Please send a small file.org with the agenda config to reproduce this problem with latest Org. Thanks! -- Bastien
Re: [O] Formal description of Org files
Hi Marcelo, Marcelo de Moraes Serpa writes: > I'm creating a web app that interacts with orgmode files and allows > you to edit orgmode files on the browser. The edit part is not done. Wow, this would be a really useful tool. Can't wait to test this! > I'm quite good at Javascript, and I wouldn't mind hacking something > akin to orgmode elisp code and this will be what I'll do if > everything else fails, but wouldn't using a grammar be a cleaner and > more elegant solution? Can you tell more about what you mean by "grammar"? Back in february, at FOSDEM, someone asked for a description of the org-mode format specification. This is still something that needs to be done. Any stab at this (on Worg) would be really nice. You can start anywhere (headlines, TODO keywords, etc.) If the "grammar" needs to be described in a specific format (more than just a formal description of the various syntactic elements of an Org file), let us know. Thanks, -- Bastien
Re: [O] Worg update
Jon Anders Skorpen wrote: > On Sat 2011-07-16 at 11:39, Nick Dokos wrote: > > > > Did the handling of ``#+INCLUDE:'' change recently? There seem > > to be quoting problems because of lines like this: > > > > #+include: "theindex.inc" > > > > in the file ``theindex.org'' and > > > > #+INCLUDE: "../code/awk/ical2org.awk" src sh > > > > in org-tutorials/org-google-sync.org, where the quotes are not > > stripped - they are taken as part of the filename, and eventually when > > the filename is checked against the cache of last mode times, the name > > includes the quotes . That function then blows up because there is no > > file called ``"theindex.org"'' > > > > Yes it did. org-publish crashed when included files was double > quoted. But it should be fixed in commit: > 920cf53e686daea4f406aa237b48fe2ef4730426 > Thanks: I pulled org just now to get this fix and I can publish Worg locally without error. Nick
Re: [O] Worg update
Hi Nick, Nick Dokos writes: > Did the handling of ``#+INCLUDE:'' change recently? There seem > to be quoting problems because of lines like this: > > #+include: "theindex.inc" > > in the file ``theindex.org'' and > > #+INCLUDE: "../code/awk/ical2org.awk" src sh > > in org-tutorials/org-google-sync.org, where the quotes are not > stripped - they are taken as part of the filename, and eventually when > the filename is checked against the cache of last mode times, the name > includes the quotes . That function then blows up because there is no > file called ``"theindex.org"'' This should have been fixed around midday -- please double-check and report any problem. Thanks, -- Bastien
Re: [O] Worg update
Hi Tom, t...@tsdye.com (Thomas S. Dye) writes: > I think Worg hasn't updated for several days. Yes, since this commit: http://orgmode.org/w/?p=org-mode.git;a=commit;h=8834bde39f90e0fa54d998f107af07e545d1165e > The last three lines in log say this: > > Publishing file /home/emacs/git/Worg/org-faq.org using > `org-publish-org-to-html' > Exporting... > Wrong type argument: arrayp, nil I fixed a problem in ob.el and just republished Worg manually. Thanks for spotting this! -- Bastien
Re: [O] Worg update
On Sat 2011-07-16 at 11:39, Nick Dokos wrote: > > Did the handling of ``#+INCLUDE:'' change recently? There seem > to be quoting problems because of lines like this: > > #+include: "theindex.inc" > > in the file ``theindex.org'' and > > #+INCLUDE: "../code/awk/ical2org.awk" src sh > > in org-tutorials/org-google-sync.org, where the quotes are not > stripped - they are taken as part of the filename, and eventually when > the filename is checked against the cache of last mode times, the name > includes the quotes . That function then blows up because there is no > file called ``"theindex.org"'' > Yes it did. org-publish crashed when included files was double quoted. But it should be fixed in commit: 920cf53e686daea4f406aa237b48fe2ef4730426 -Jon Anders Skorpen
Re: [O] Worg update
Matthew Sauer wrote: > I just did a pull and org-issues updated (about 10K some deletions and > around the same amount of insertions. > The problem is not that worg is down: pulls/pushes work fine. It's the publishing that fails. Nick
Re: [O] New backend for org-agenda: (Was Calendar-like view of the org-agenda)
Hi Bastien, At Tue, 12 Jul 2011 09:37:21 +0200, Bastien wrote: > : > The question is: would an API for the whole agenda mechanism (and not > just scheduled items) be useful? > > I've never been a big fan of caching Org files information, because Org > files are often modified in impredictible ways. But if we can update > the cache quickly, then it will certainly be useful. I'm sure that the caching mechanism is useful, but I'm not sure that we should do it with paying the large cost of rewrite whole codes. Because the orgmode is the center of information for the many Emacs users, I think it is very interesting for not only elisp codes but also the other applications to access the information of the orgmode via emacsclient or D-Bus messaging. If the interface for the mode of orgmode items and modification hooks is defined, one would send todo items to one's mobile terminal immediately, or share the items on the SNS. Of course, it is just a trivial idea, not my request. > I will let you know about progress about this. > > Thanks again for raising this idea! I'm glad to be able to share my idea. It was difficult for me to discuss the abstract topic quickly in English. Thank you -- SAKURAI, Masashi (family, given) m.saku...@kiwanami.net
Re: [O] Worg update
I just did a pull and org-issues updated (about 10K some deletions and around the same amount of insertions. On Sat, Jul 16, 2011 at 11:02 AM, Nick Dokos wrote: > Nick Dokos wrote: > >> Also, even though somehow I had ``theindex.org'' in my clone of worg, it >> does not seem to be git-controlled, but it also does not seem to be a >> derived file. What's up with that? >> > > Scratch this: org-publish creates theindex.org if :makeindex is set. > > Nick > > >
Re: [O] Worg update
Nick Dokos wrote: > Also, even though somehow I had ``theindex.org'' in my clone of worg, it > does not seem to be git-controlled, but it also does not seem to be a > derived file. What's up with that? > Scratch this: org-publish creates theindex.org if :makeindex is set. Nick
Re: [O] Attachments and refiling
I use org-attach regularly and consider it to be a great feature of
org-mode. Since I only attach to the sub-tree (instead of to a different
file) I have not this problem. However, sometimes a set the attach
directory of two different headings to the same folder (when it makes
sense) and if org always moved the attached files it would break the other
sub-tree.
An alternative is to change the attach directory in the archived entry to
point to the original attach directory where the files are. When archiving
to a file in a different folder org could ask if it should also move the
attached files or simply change the attach directory accordingly (I would
prefer this as the default if "ask" as the default was considered too
annoying).
--
Darlan
At Fri, 15 Jul 2011 16:55:06 +0200,
Gustav Wikström wrote:
>
> [1 ]
> Hello Bastien!
>
> To clarify a bit. Lets say I have a file c:\temp\agenda.org (I'm calling it
> file 'a').
>
> When marked with TODO item: done, headings in this file are archived to
> another file called c:\temp\archive\agenda.org_archive ('b')
>
> If i use C-c C-a to attach a file to a certain topic in 'a' and then refile
> this topic to 'b', when done the attachment still resides in c:\temp\data
> and will not be found when looking at the attachment in 'b'.
>
> Thus my question is if it is possible to also refile the attachment so the
> attachment-folder resides in c:\temp\archive\data and is avaliable in 'b'?
>
> /Gustav
>
> 2011/7/15 Bastien
>
> > Hi Gustav,
> >
> > Gustav Wikström writes:
> >
> > > Is it possible to make attachment-folders move with the headings when
> > > refiling them to other locations?
> >
> > I'm not sure what you mean.
> >
> > Can you give an example?
> >
> > --
> > Bastien
> >
> [2 ]
>
Re: [O] Worg update
Thomas S. Dye wrote: > I think Worg hasn't updated for several days. > > The last three lines in log say this: > > Publishing file /home/emacs/git/Worg/org-faq.org using > `org-publish-org-to-html' > Exporting... > Wrong type argument: arrayp, nil > Did the handling of ``#+INCLUDE:'' change recently? There seem to be quoting problems because of lines like this: #+include: "theindex.inc" in the file ``theindex.org'' and #+INCLUDE: "../code/awk/ical2org.awk" src sh in org-tutorials/org-google-sync.org, where the quotes are not stripped - they are taken as part of the filename, and eventually when the filename is checked against the cache of last mode times, the name includes the quotes . That function then blows up because there is no file called ``"theindex.org"'' Also, even though somehow I had ``theindex.org'' in my clone of worg, it does not seem to be git-controlled, but it also does not seem to be a derived file. What's up with that? Nick
Re: [O] Calendar-like view of the org-agenda
Hi Bastien, At Tue, 12 Jul 2011 09:24:25 +0200, Bastien wrote: > : > > One question, is it fixed variable for an user? I mean, one often > > changes the argument parameter to change the filtering in a single > > Emacs session. > > It would actually be nice to be able to change this parameters on the > fly -- even for org agendas. That's not currently possible but I will > consider implementing this for Org. I see. > > If one frequently changes it, should I design the UI to change it and > > re-draw the calendar? > > I think you can already do this independantly from Org's implementation. Ok. I will try to design the customization. I think it should be done together with the filter function discussed at another thread. -- SAKURAI, Masashi (family, given) m.saku...@kiwanami.net
Re: [O] Worg update
Thomas S. Dye wrote: > I think Worg hasn't updated for several days. > > The last three lines in log say this: > > Publishing file /home/emacs/git/Worg/org-faq.org using > `org-publish-org-to-html' > Exporting... > Wrong type argument: arrayp, nil > Did the handling of ``#+INCLUDE:'' change recently? There seem to be quoting problems because of lines like this: #+include: "theindex.inc" in the file ``theindex.org'' and #+INCLUDE: "../code/awk/ical2org.awk" src sh in org-tutorials/org-google-sync.org, where the quotes are not stripped - they are taken as part of the filename, and eventually when the filename is checked against the cache of last mode times, the name includes the quotes . That function then blows up because there is no file called ``"theindex.org"'' Also, even though somehow I had ``theindex.org'' in my clone of worg, it does not seem to be git-controlled, but it also does not seem to be a derived file. What's up with that? Nick
Re: [O] Calendar-like view of the org-agenda
Hi Manuel, Thank you for your example. I have to study a lot of customize variables of org-agenda. The org-mode is very deep world! At Mon, 11 Jul 2011 21:02:48 +0200, Manuel Hermenegildo wrote: > : > Currently, both tasks will appear in the calfw view. > > In the normal org agenda views the necessary filtering is done via the > "org-agenda-custom-commands" variable, defining a "custom agenda > command" with a filter (this is the recommended way of creating > different agendas and todo lists in org). For example, to get an > agenda view with only my tasks, which I identfy with the tag "MH" I > use (this is my normal agenda view): > > (setq org-agenda-custom-commands > (list > (list >"a" "Agenda with (only) my tasks (those that have my tag and a date)" >'((agenda > "" > ((org-agenda-skip-function '(my-skip-by-tags "MH")) >(org-agenda-overriding-header > "Agenda -- with (only) my tasks (those that have my tag and a > date)") >)) > : > The particular filter that I use (my-skip-by-tags) is a function that > checks for inherited tags. I am not sure this can be done with > org-agenda-get-day-entries. This is why I was suggesting perhaps > using a modified version of org-agenda (a back-end) that would feed > the data computed to calfw (the same could be used for all the other > agenda exports). Or perhaps org-agenda-get-day-entries can be made to > call a filter function like the one above? I think org-agenda-get-day-entries uses the customize function org-agenda-skip-function via org-agenda-get-xxx functions. So, I can display schedules filtered by the my-skip-by-tags, like following ad-hoc code. == (defun cfw:org-collect-schedules-period (begin end) "[internal] Return org schedule items between BEGIN and END." (let ((org-agenda-prefix-format "") (span 'day) (org-agenda-skip-function '(my-skip-by-tags "MH"))) ;; Added here!! (org-compile-prefix-format nil) (loop for date in (cfw:enumerate-days begin end) append (loop for file in (org-agenda-files nil 'ifmode) append (progn (org-check-agenda-file file) (apply 'org-agenda-get-day-entries file date cfw:org-agenda-schedule-args)) == I will think about the customization of such filters. If someone has a good idea or patch, please let me know. Thank you, -- SAKURAI, Masashi (family, given) m.saku...@kiwanami.net
Re: [O] Makefile restructuring
Bastien writes: > I think the proliferation of *.mk files can confuse the user. > Can we try to reduce this to the maximum? Nothing is set in stone at this point and there will certainly be changes to make sure things are useful both for users and maintainers of org-mode. If something doesn't "feel" right, it probably isn't and we can try something else before commiting to any changes. Since this depends on getting feedback, please keep it coming. > Ideally, there will be no *.mk file at all, just one Makefile > in which the maintainer can include a maint.mk file that will > only live on orgmode.org server (since we are releasing from > there.) It would be easy enough to hide the *.mk files in some subdirectory (a new one or perhaps UTILITIES) to unclutter the main directory. I've split off the verious parts for now based on function, and yes, some of these may be re-integrated later. At the moment this is only there to make these different functions visible since calling make still reads them in all at once and acts as if they were a single file. > But maybe you're already heading in this direction, or my > suggestion goes against your goal. Let me elaborate: The original goal was that I would not need to change the Makefile when doing my local setup since I frequently change it for testing. Right now I'm rebasing a short branch with my local setup onto whatever branch I'm working on so I don't clutter the history with these changes. Splitting off an optional file local.mk is what achieves that goal most cleanly, IMHO. I can now just link to whatever setup I need at the moment in the testing branches or register a stable setup in other branches. The Makefile has indeed been shortened to the extreme based on the idea that it should fit onto a single screen when someone does a 'cat Makefile' and not contain anything that needs to be prefixed with an explanation. Ideally the Makefile would be clear enough to obsolete the necessity for an INSTALL file (which doesn't currently exist anyway). The default.mk has been introduced to be an easy template from which to create a local.mk by copying. This is not strictly necessary, but to me it looks easier than to tell people to copy the right part of the Makefile into local.mk. But both options will need to be accompanied by instructions and it's mainly a question of them being easy to follow. Come to think of it, I'll probably add a target that creates local.mk… so that issue likely becomes moot. The server part of the Makefile could actually be included from local.mk, so it would not need to exist in the standard distribution (at least not in the top level directory). The existence of both targets.mk and maint-targets.mk is transitory until things sort cleanly into one or the other category. User visible targets could then wander back into the Makefile, while the maintainer targets would become part of another optional include. The dependencies have been split off since ideally they would be auto-generated by make. PS: I've just completed the install of Emacs24 in parallel to the Emacs23.3, so I should can make sure that make will succeed with both. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
[O] Worg update
Aloha all, I think Worg hasn't updated for several days. The last three lines in log say this: Publishing file /home/emacs/git/Worg/org-faq.org using `org-publish-org-to-html' Exporting... Wrong type argument: arrayp, nil All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Bug: Org-Babel Mode R Plot Output to LaTeX File [Babel] [7.5]
See the `org-export-latex-image-default-option' variable. Generally in such situation you can run the `describe-variable' function and tab-complete your way to the name of the relevant variable. The `apropos' function is also useful for suss out this sort of information. Best -- Eric Stephen Eglen writes: >> however they do not affect the generated latex code. Luckily Org-mode >> does support passing information like image width to latex figures. See >> my attached version of your test file which uses #+ATTR_LaTeX lines to >> specify the width during LaTeX export. > > hi Eric, > why is the default width 10em for latex graphics? (Or at least, how can > I change this default? > > thanks, > Stephen > > -- Eric Schulte http://cs.unm.edu/~eschulte/
[O] [Accepted] org-publish: Fix regexp for include files
Patch 833 (http://patchwork.newartisans.com/patch/833/) is now "Accepted". Maintainer comment: none This relates to the following submission: http://mid.gmane.org/%3C1310818927-25567-1-git-send-email-jonas%40ifi.uio.no%3E Here is the original message containing the patch: > Content-Type: text/plain; charset="utf-8" > MIME-Version: 1.0 > Content-Transfer-Encoding: 7bit > Subject: [O] org-publish: Fix regexp for include files > Date: Sat, 16 Jul 2011 17:22:07 - > From: Jon Anders Skorpen > X-Patchwork-Id: 833 > Message-Id: <1310818927-25567-1-git-send-email-jo...@ifi.uio.no> > To: emacs-orgmode@gnu.org > Cc: Jon Anders Skorpen > > * org-publish.el (org-publish-cache-file-needs-publishing): Regexp did > not find includes with double quoted file names. > > TINYCHANGE > > --- > lisp/org-publish.el |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/lisp/org-publish.el b/lisp/org-publish.el > index b8e932d..9654a6d 100644 > --- a/lisp/org-publish.el > +++ b/lisp/org-publish.el > @@ -1108,7 +1108,7 @@ so that the file including them will be republished as > well." >(when (equal (file-name-extension filename) "org") > (find-file (expand-file-name filename)) > (goto-char (point-min)) > - (while (re-search-forward "^#\\+INCLUDE: \\(.+\\)[ ^\t]*$" nil t) > + (while (re-search-forward "^#\\+INCLUDE:[ \t]+\"?\\([^ \t\"]*\\)\"?[ > \t]*.*$" nil t) > (let* ((included-file (expand-file-name (match-string 1 > (add-to-list 'included-files-ctime >(org-publish-cache-ctime-of-src included-file) t) >
Re: [O] [PATCH] Adding support for :results output for clojure src blocks.
Eric Schulte writes: > However, in this particular case, you could easily sneak your patch into > under 10 lines by replacing the `cond' with a nested `if', and I would > be happy to include such a patch immediately. I just applied Robert's patch in a way that makes his contribution short enough... in size, not in significance! Thanks again, -- Bastien
Re: [O] how to change the headline starter *
On Fri, 15 Jul 2011 12:21:01 +0200, Philipp Haselwarter wrote: > No need to go all flaming because someone thinks the looks of the > software matter. TBH I don't see what's wrong with that or in what way > that's the opposite of efficiency. What I considered "wrong" about it was the OP implying -twice- that a frivolous feature request such as this could be marked as being a full-caps "BUG" [1,2]. Considering all the time and effort Org-mode's selfless developers have sacrificed to deliver this mindblowing piece of software to us, this could easily be perceived as an insult in my opinion, regardless of whether or not it was intentional. I know that this doesn't justify the tone of my impulsive reply in any way whatsoever, and I do apologize for disrupting the serene atmosphere which characterizes this list, but... I sent it, and I stand behind it 100%. Besides, how could someone who cares about how slick and shiny their software looks *possibly* end up using Emacs? > Abstracting the user interface from the logic is an important paradigm, > especially for something like org-mode that you want to run on a wide > range of devices – think 24" monitors vs 3" mobile devices. You don't > want to have too much of the looks hardcoded. Exactly! That is, believe it or not, the whole point. What the OP is suggesting effectively nullifies the separation between model and view in that it would allow changing Org-mode's outlining markup at its very core, potentially leading to a wildgrowth of "custom" markup formats which could hardly be called "plain text" anymore, not to mention the avalanche of PEBCAK-related bug reports it may unleash. > Now if you don't find that to be one of /your/ personal top priorities – > fine, don't bother. But going all bashing because someone insists on his > opinion that this is important? I don't see what you're trying to > achieve here. Pretty much since the very beginning, Org-mode has been described as: "Org is a mode for keeping notes, maintaining TODO lists, and doing project planning with a fast and effective plain-text system." Seeing as how this description hasn't changed ever since, one can safely assume that keeping the markup format sane (i.e. plain-text) and consistent (i.e. semi-standardized, so as not to complicate joint project planning) is a top priority for the entire Org-mode community. As for my personal priorities: I didn't start using Emacs solely because Org-mode *requires* me to, but because I care about getting my work done, as efficiently as possible. Mac/Windows-influenced non-features (and the code overhead they introduce) will undoubtedly interfere with that. IOW, a lack of certain "features" is an essential feature in and of itself. I guess what I'm trying to achieve is to keep Org-mode from slowly and inconspicuously devolving into something featuring transparent blinking 3D unicorn overlays with cherries on top. That's a gross exaggeration of course (one would hope), but I'm sure you catch my drift. > > -- > Philipp Haselwarter > > Peace -- Pieter [1] id:"101625.2577651310651584384.javamail.r...@zimbra29-e5.priv.proxad.net" [2] id:"1240511841.2591431310664738370.javamail.r...@zimbra29-e5.priv.proxad.net"
Re: [O] Org-mode on GNU ELPA
Hi Jambunathan, Jambunathan K writes: > Yes. Please obsolete all the earlier submissions. Done. > I will re-submit a re-based patch. May be I can pick a thing or two from > Achim's changes. I will be happy to have him review the "make pkg" > changes and suggest improvements to the same. Great! Thanks, -- Bastien
Re: [O] Problem with autoloads
Bastien writes: > Can someone send me this patch again so that I apply it? Forget it -- I just found and applied the patch. Thanks, -- Bastien
Re: [O] Org-mode on GNU ELPA
>> I have a patch to Makefile which permits this to be done. I have not >> been able to spend much time hacking for the last week or so but I plan >> to nudge it forward as soon as my spirit is willing. > > I guess your new patch will obsolete this one: > > http://patchwork.newartisans.com/patch/377/ > > Can you confirm, so that I mark the patch above as obsolete? Yes. Please obsolete all the earlier submissions. > I'm looking forward to reading the new patch. > > Achim is also working on the Makefile and IMHO the issue he will > solve is more pressing. I suggest we wait for his change to apply > your new patch. I will re-submit a re-based patch. May be I can pick a thing or two from Achim's changes. I will be happy to have him review the "make pkg" changes and suggest improvements to the same. Jambunathan K. > Thanks a lot,
Re: [O] Problem with autoloads
Achim Gratz writes: > Meanwhile the patch that has been posted fixes the issue and does not > break on older Emacsen, so this should probably be applied by Bastien. I somehow lost track of this patch (my .overview in Gnus got corrupted) and I cannot access Gmane as the search.gmane.org seems to be down. Can someone send me this patch again so that I apply it? Thanks in advance, -- Bastien
Re: [O] Web bookmarks in ORG?
Hi Angel, Angel de Vicente writes: > Thanks for the suggestion. I'm very busy right now, so I didn't look at > this, but I will certainly come back to it, and report back. (There was > also a Emacs Database, EDB, which I never used, but which perhaps could > also be used, but I'm not sure if that is still maintained...) Great -- let us know about your progress, it can boost any org/recutils gateway. Thanks, -- Bastien
[O] [PATCH] org-publish: Fix regexp for include files
* org-publish.el (org-publish-cache-file-needs-publishing): Regexp did not find includes with double quoted file names. TINYCHANGE --- lisp/org-publish.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-publish.el b/lisp/org-publish.el index b8e932d..9654a6d 100644 --- a/lisp/org-publish.el +++ b/lisp/org-publish.el @@ -1108,7 +1108,7 @@ so that the file including them will be republished as well." (when (equal (file-name-extension filename) "org") (find-file (expand-file-name filename)) (goto-char (point-min)) - (while (re-search-forward "^#\\+INCLUDE: \\(.+\\)[ ^\t]*$" nil t) + (while (re-search-forward "^#\\+INCLUDE:[ \t]+\"?\\([^ \t\"]*\\)\"?[ \t]*.*$" nil t) (let* ((included-file (expand-file-name (match-string 1 (add-to-list 'included-files-ctime (org-publish-cache-ctime-of-src included-file) t) -- 1.7.4.1
Re: [O] Org-mode on GNU ELPA
matt...@safe-mail.net writes: > Org-mode on GNU ELPA does not distribute the contrib-directory. Is there > any chance this could be added? No, because the GNU ELPA policy requires that the authors of a GNU ELPA file sign the FSF assignment. One of the reasons we have a contrib/ directory is that we don't want to limit Org's distribution to files from authors who signed this agreement. > Other than that, I think the GNU ELPA > archive is synced with the trunk/master rather than with the actual > releases. Correct. > I often encounter minor bugs when working with org which usually > disappear after updating from GNU ELPA again. Is is possible that the > mainline release (7.6) is distributed via ELPA rather than a bleeding edge > development version? The main reason we have an Org tarball in GNU ELPA is to let users easily access to the bleeding edge version of Org. If GNU ELPA contains the exact same version than Emacs, then there is no real advantage of distributing Org in both channels. So I think it's better to stick to the current scheme. Thanks, -- Bastien
Re: [O] Using org-mode for Research and Notetaking
Hi all, Nicolas Goaziou writes: >> 1. people want inline tasks with possibly no TODO keyword >> 2. people prefer to detect them *very easily* >> 3. changing the syntax of inline tasks from changing todos >>(like !TODO) is too complicated code-wise > > 4. people do not want to break the main flow of text. By default, the >text in the inline task starts at the 15th column. Of course, you're right. >> My proposal is this: >> >> - enforce the use of TODO keywords in inline tasks (wrt 1) > > I think it is an unnecessary restriction. I remember some people use > inline tasks without even a title (they only write the stars). Yes. > IMO, inline tasks are used in two distinct fashions. Obviously, one is > to use them as tasks. The other one is to use them as marginal notes, > like drawers with a title. Let's not forget that second category, unless > we provide an alternative solution for them, i.e. an annotation system. > >> - make a special face for inline tasks (wrt 2) > > I think it is a good idea. Okay, TODO added. Thanks, -- Bastien
Re: [O] Makefile restructuring
Hi Achim, Achim Gratz writes: > Bastien writes: >> Okay - I'll follow that branch till the change becomes mature. > > I've set up the feature branch "Makefile" in my org-mode clone on > repo.or.cz. Assuming you already have orgmode.git cloned (it does not > really matter where from), do a > > git remote add -t Makefile remote-tableheadings > git://repo.or.cz/org-mode/org-tableheadings.git > git fetch remote-tableheadings Makefile:local-Makefile > git checkout local-Makefile > > to get it (change remote-tableheadings and local-Makefile to suit > your naming conventions for remotes and local branches, respectively). > I will be _rebasing_ against master during development, so expect > history in this branch to be volatile. > > As always, testers and their comments are welcome. Thanks a lot for this. Here is some feedback: I think the proliferation of *.mk files can confuse the user. Can we try to reduce this to the maximum? Ideally, there will be no *.mk file at all, just one Makefile in which the maintainer can include a maint.mk file that will only live on orgmode.org server (since we are releasing from there.) But maybe you're already heading in this direction, or my suggestion goes against your goal. Thanks for any answer! Best, -- Bastien
Re: [O] ThoughtBack
Guys, AFAIU, the fun of using ThoughtBack is to get *random* ideas from the past. This actually could fit in Org: get a random agenda based on selected criteria. Would that be useful? For the record, we already have some randomness through the bulk command "scatter" -- where items are scattered randomly over a definite period of time. -- Bastien
Re: [O] how to change the headline starter *
Hi Harven, harven writes: > Let me apologize for having started the thread then. Well, no one hurt! It's sometimes a good things to try to rephrase old problems. In this case it led me to have another perspective about this issue, so thank *you* for starting it. -- Bastien
Re: [O] Performance problem when switching agenda views - need for cache?
Hi Rainer, Rainer Stengele writes: > so yes - the main part of the time is taken by the big org file. Still > 5 seconds is not a keypress ... And of course I will need a certain > part of the excluded file. So going into any kind of caching might > speed up things quite a bit. Yes. Sorry to read about such performance problems (again). One thing I've used to speed up my own setup is to reduce the scope of `org-agenda-get-day-entries' by restricting agenda view with (org-agenda-entry-types '(:scheduled)) where it makes sense. Otherwise `org-agenda-get-day-entries' can loop over too many possibilities. Keep us informed of any further analysis, progress. Thanks! -- Bastien
Re: [O] how to change the headline starter *
Hi Nicolas, Nicolas Goaziou writes: > I do not disagree. :) > My point is that it could be hard-coded in > a consistent way, i.e. all references to an headline could look for > `org-outline-regexp' instead of some custom string (even though it may > be shorter and easier to write). I do agree. -- Bastien
Re: [O] Org-mode on GNU ELPA
Dear Jambunathan, Jambunathan K writes: > matt...@safe-mail.net writes: > >> Org-mode on GNU ELPA does not distribute the contrib-directory. Is >> there any chance this could be added? > > I have a patch to Makefile which permits this to be done. I have not > been able to spend much time hacking for the last week or so but I plan > to nudge it forward as soon as my spirit is willing. I guess your new patch will obsolete this one: http://patchwork.newartisans.com/patch/377/ Can you confirm, so that I mark the patch above as obsolete? I'm looking forward to reading the new patch. Achim is also working on the Makefile and IMHO the issue he will solve is more pressing. I suggest we wait for his change to apply your new patch. Thanks a lot, -- Bastien
Re: [O] how to change the headline starter *
Hi Carsten, Carsten Dominik writes: > Org-mocde has many syntax elements using many characters, and > any modification of the headline character would likely > lead to conflicts in other areas. So I do not recommend > even trying to change this. Outline-mode is a general mode > to do outlining and can change this. Org-mode is a specific > file format. This confirms my intuition that the "*" should be hardcoded. I will work on a patch to this effect and submit it to the list, I even expect there will be some performance boost. Thanks for your input! -- Bastien
Re: [O] how to change the headline starter *
Hi Achim, Achim Gratz writes: > I don't know if having a regexp a compile-time > constant is advantageous in terms of performance. I think it is. > In any case it would > be quite some effort to clean up all regexp to only use symbols. Harven's question convinced me to undertake this effort, stay tuned. > So it would > seem to make more sense to me to keep the org syntax as is and perhaps > allow some more visual sugar by adding overlays (for those that don't > miond their performance impact). Yes, that'd be also the route I favor, although I'm afraid performance will be hugely impacted. -- Bastien
Re: [O] how to change the headline starter *
Hi Harven, harven writes: > I am assuming that the org files all start with a org- prefix. Am I > right ? There are also ob-* files in recent version of Org. I did a quick check and could not find references to outline-regexp or org-outline-regexp in those files, but maybe "^\\*" is hardcoded in some places too. Thanks for digging into this issue, I'll need your help when I'll try to hardcode the "*" character! Best, -- Bastien
[O] entering a date through C-c ! or C-c . in "edit" mode of column view does not work
I get the message: "C-c ! is undefined" Actually, I need to record a date for each item, and I would like to enter the date using the column mode. Any idea on how to do it? Jean Wallemacq jean.wallem...@skynet.be
Re: [O] Bug: Org-Babel Mode R Plot Output to LaTeX File [Babel] [7.5]
> however they do not affect the generated latex code. Luckily Org-mode > does support passing information like image width to latex figures. See > my attached version of your test file which uses #+ATTR_LaTeX lines to > specify the width during LaTeX export. hi Eric, why is the default width 10em for latex graphics? (Or at least, how can I change this default? thanks, Stephen
Re: [O] [PATCH] fix compiler warning in org-footnote.el for not known to be defined function org-combine-plists defined in org.el but not declared in org-footnote.el
Hello, Matthew Sauer writes: > diff --git a/lisp/org-footnote.el b/lisp/org-footnote.el > index 03e6369..3a30575 100644 > --- a/lisp/org-footnote.el > +++ b/lisp/org-footnote.el > @@ -54,6 +54,7 @@ > (declare-function org-fill-paragraph "org" (&optional justify)) > (declare-function org-export-preprocess-string "org-exp" > (string &rest parameters)) > +(declare-function org-combine-plists "org" (&rest plists)) > (defvar org-odd-levels-only) ;; defined in org.el > (defvar org-bracket-link-regexp) ; defined in org.el > (defvar message-signature-separator) ;; defined in message.el I have applied it. Thank you. Regards, -- Nicolas Goaziou
