Re: [Orgmode] [PATCH] Docstring fixes
On Jul 18, 2010, at 10:30 PM, Carsten Dominik wrote: Hi Phil, I cannot get this patch to apply cleanly. Could you update it, please? Never mind, I went through it and applied it by hand. Thanks! - Carsten On Jul 18, 2010, at 6:28 PM, Phil Rooke wrote: This is the ninth patch in a series that makes some straightforward corrections to a number of docstrings. Each change is normally to: - correct a typo, or - fix up hyperlinks to function or variable names, or - ensure slightly better conformance with the documentation guidelines and tips given in the Elisp manual --- This is a partial patch, mainly focused on fixing some references to C-u. Given the pending release deadline I thought I may as well send this now, hopefully it is useful in its own right. diff --git a/lisp/org.el b/lisp/org.el index acd7031..f8c2026 100644 --- a/lisp/org.el +++ b/lisp/org.el @@ -818,7 +818,8 @@ This can also be set in on a per-file basis with (defcustom org-cycle-global-at-bob nil Cycle globally if cursor is at beginning of buffer and not at a headline. This makes it possible to do global cycling without having to use S- TAB or -C-u TAB. For this special case to work, the first line of the buffer +\\[universal-argument] TAB. For this special case to work, the first line \ +of the buffer must not be a headline - it may be empty or some other text. When used in this way, `org-cycle-hook' is disables temporarily, to make sure the cursor stays at the beginning of the buffer. @@ -1640,7 +1641,6 @@ file identifier are that does not use any of the group matches, this case is handled identically to the second one (i.e. match against file name only). - In a custom lisp form, you can access the group matches with (match-string n link). @@ -1660,7 +1660,7 @@ file identifier are `system' The system command to open files, like `open' on Windows and Mac OS X, and mailcap under GNU/Linux. This is the command that will be selected if you call `C-c C-o' with a double - `C-u C-u' prefix. + \\[universal-argument] \\[universal-argument] prefix. Possible values for the command are: `emacs' The file will be visited by the current Emacs process. @@ -5925,7 +5925,7 @@ in special contexts. ;;;###autoload (defun org-global-cycle (optional arg) Cycle the global visibility. For details see `org-cycle'. -With C-u prefix arg, switch to startup visibility. +With \\[universal-argument] prefix arg, switch to startup visibility. With a numeric prefix, show all headlines up to that level. (interactive P) (let ((org-cycle-include-plain-lists @@ -6259,7 +6259,7 @@ point nowhere. (make-variable-buffer-local 'org-hide-block-overlays) (defun org-block-map (function optional start end) - Call function at the head of all source blocks in the current buffer. + Call FUNCTION at the head of all source blocks in the current buffer. Optional arguments START and END can be used to limit the range. (let ((start (or start (point-min))) (end (or end (point-max @@ -6548,10 +6548,12 @@ With numerical prefix ARG, go up to this level and then take that tree. If ARG is negative, go up that many levels. If `org-indirect-buffer-display' is not `new-frame', the command removes the indirect buffer previously made with this command, to avoid proliferation of -indirect buffers. However, when you call the command with a `C-u' prefix, or +indirect buffers. However, when you call the command with a \ +\\[universal-argument] prefix, or when `org-indirect-buffer-display' is `new-frame', the last buffer is kept so that you can work with several indirect buffers at the same time. -If `org-indirect-buffer-display' is `dedicated-frame', the C-u prefix also +If `org-indirect-buffer-display' is `dedicated-frame', the \ +\\[universal-argument] prefix also requests that a new frame be made for the new buffer, so that the dedicated frame is not changed. (interactive P) @@ -9554,7 +9556,8 @@ entry for this file type, and if yes, the corresponding command is launched. If no application is found, Emacs simply visits the file. With optional prefix argument IN-EMACS, Emacs will visit the file. -With a double C-c C-u prefix arg, Org tries to avoid opening in Emacs +With a double \\[universal-argument] \\[universal-argument] \ +prefix arg, Org tries to avoid opening in Emacs and to use an external application to visit the file. Optional LINE specifies a line to go to, optional SEARCH a string @@ -10039,7 +10042,8 @@ below it are allowed. With prefix arg GOTO, the command will only visit the target location, not actually move anything. -With a double prefix `C-u C-u', go to the location where the last refiling +With a double prefix arg \\[universal-argument] \\[universal- argument], \ +go to the location where the last refiling operation has
[Orgmode] Org-mode release 7.01
Hi everyone, I have just released version 7.01 of Org mode. This is a major release, and we have worked months on getting it together. Most important is of cause the complete integration of Org Babel into Org mode. Many thanks to Eric Schulte and Dan Davison who have worked tirelessly to make this happen. Thomas S. Dye gets credit here as well because he did a lot of work on documentation and function/variable docstrings. Also, I need to shout out my gratitude to the increasing number of volunteers in the project. John Wiegley's patchwork server has done wonders for streamlining the process of reviewing and applying patches. I have applied dozens of patches though this process, just in the last week. The issue tracker by David Maus has finally brought some structure into the stream of ideas and reports on this mailing list, at a moment when I was about to falter under the amount of work maintaining this project means for me. Frankly, right now I don't know how I would do things without David's competent and efficient help - he has effectively and silently become co-maintainer of this project. Below these tips above the waterline, there is an iceberg of contributions large and small by so many people. We have 54 people with FSF papers now, and more contributors of tiny patches. Also there are the volunteers that manage the mailing list, Worg, and the FAQ. I am truly humbled and made proud at the same time by each and every contribution that the Org mode projects receives. These contributions made Org mode the phenomenon it now is. Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. P.P.S. The feature freeze is over now. Changes in Version 7.01 === Incompatible Changes ~ Emacs 21 support has been dropped == Do not use Org mode 7.xx with Emacs 21, use [version 6.36c] instead. [version 6.36c]: http://orgmode.org/org-6.36c.zip XEmacs support requires the XEmacs development version === To use Org mode 7.xx with XEmacs, you need to run the developer version of XEmacs. I was about to drop XEmacs support entirely, but Michael Sperber stepped in and made changes to XEmacs that made it easier to keep the support. Thanks to Michael for this last-minute save. I had hoped to be able to remove xemacs/noutline.el from release 7 by moving it into XEmacs, but this is not yet done. Org-babel configuration changes Babel took the integration into Org-mode as an opportunity to do some much needed house cleaning. Most importantly we have simplified the enabling of language support, and cleared out unnecessary configuration variables -- which is great unless you already have a working configuration under the old model. The most important changes regard the /location/ and /enabling/ of Babel (both core functionality and language specific support). Babel: Babel is now part of the core of Org-mode, so it is now loaded along with the rest of Org-mode. That means that there is /no configuration/ required to enable the main Babel functionality. For current users, this means that statements like (require 'org-babel) or (require 'org-babel-init) that may by lying around in your configuration must now be removed. load path: Babel (including all language specific files -- aside from those which are located in the =contrib/= directory for reasons of licencing) now lives in the base of the Org-mode lisp directory, so /no additional directories/ need to be added to your load path to use babel. For Babel users this means that statements adding babel-specific directories to your load-path should now be removed from your config. language support: It is no longer necessary to require language specific support on a language-by-language basis. Specific language support should now be managed through the `org-babel-load-languages' variable. This variable can be customized using the Emacs customization interface, or through the addition of something like the following to your configuration (note: any language not mentioned will /not/ be enabled, aside from =emacs-lisp= which is enabled by default) (org-babel-do-load-languages 'org-babel-load-languages '((R . t) (ditaa . t) (dot . t) (emacs-lisp . t) (gnuplot . t) (haskell . nil) (ocaml . nil) (python . t) (ruby . t) (screen . nil) (sh . t) (sql . nil) (sqlite . t)))
[Orgmode] Patchwork: Patch 148 Accepted
Patch 148 (http://patchwork.newartisans.com/patch/148/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3Cm2k4ou6wor.fsf%40bo.yax.org.uk%3E ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Patchwork: Patch 145 Accepted
Patch 145 (http://patchwork.newartisans.com/patch/145/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3C1279347713-29950-1-git-send-email-dmaus%40ictsoc.de%3E ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Patchwork: Patch 150 Accepted
Patch 150 (http://patchwork.newartisans.com/patch/150/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3C878w59a163.fsf%40dynapse.com%3E ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Patchwork: Patch 146 Accepted
Patch 146 (http://patchwork.newartisans.com/patch/146/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3C87vd8ebohm.wl%25dmaus%40ictsoc.de%3E ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Patchwork: Patch 139 Accepted
Patch 139 (http://patchwork.newartisans.com/patch/139/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3C8739vjbg92.wl%25dmaus%40ictsoc.de%3E ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: [PATCH] org-capture with LISP function template
Hi Juan, the function must be a symbol in this setup, not a string. I am rejecting this patch. Cheers. - Carsten On Jul 19, 2010, at 3:45 AM, Juan Pechiar wrote: Hi Carsten + crowd, Below is a patch for org-capture when the template is given by a LISP function. Problem was that the function is inside a string (not a LISP form), so the string has to be evaluated explicitly. Now it's working for me. I use it to get a template formed by URL/title and selected text from Opera browser (on Mac OSX). I´ll publish this after polishing the code. I've also been testing exotic org-capture templates and I've found no other errors yet. Best regards, .j. 8 diff --git a/lisp/org-capture.el b/lisp/org-capture.el index 2a3a1b8..409427f 100644 --- a/lisp/org-capture.el +++ b/lisp/org-capture.el @@ -440,8 +440,8 @@ bypassed. (setq txt (org-file-contents file)) (setq txt (format * Template file %s not found (nth 1 txt) ((and (listp txt) (eq (car txt) 'function)) - (if (fboundp (nth 1 txt)) - (setq txt (funcall (nth 1 txt))) + (if (eval (concat fboundp (nth 1 txt))) + (setq txt (eval (read (nth 1 txt (setq txt (format * Template function %s not found (nth 1 txt) ((not txt) (setq txt )) ((stringp txt)) - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [babel] feature request - tangle-and-evaluate-tangled-file
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17/07/2010 00:58, Eric Schulte wrote: Hi Rainer, I've just pushed up a fix for the org-babel-post-tangle-hook. With a minimal org-babel configuration, if I open the following file. --8---cut here---start-8--- ** tangle R and load :PROPERTIES: :tangle: to-load.r :END: evaluate this #+begin_src emacs-lisp :results silent :tangle no (add-hook 'org-babel-post-tangle-hook (lambda () (message I'm in %s (buffer-file-name #+end_src then tangle #+begin_src R :comments yes x - 8 #+end_src #+begin_src R y - 9 #+end_src --8---cut here---end---8--- evaluate the emacs-lisp code block to initialize my post-tangle-hook, and then tangle the very same file, I see the following in my messages buffer, indicating that the correct file is now being visited. --8---cut here---start-8--- Wrote /home/eschulte/Desktop/to-load.r [2 times] tangled 2 code blocks I'm in /home/eschulte/Desktop/to-load.r --8---cut here---end---8--- Hopefully this will now work for you as well. Great - thanks a lot - it does. I especially like the idea of putting the setting of the hook in the .org file - I had it in my emacs.org, but it is MUCH nicer to have it in the .org file. Cheers and thanks a lot, Rainer Thanks -- Eric Rainer M Krug r.m.k...@gmail.com writes: On 13/07/2010 10:14, Dr Rainer M Krug wrote: On 12/07/2010 19:51, Eric Schulte wrote: Rainer M Krug r.m.k...@gmail.com writes: Hi Eric, On Fri, Jul 9, 2010 at 5:44 PM, Eric Schulte schulte.e...@gmail.com wrote: Hi Rainer, Rainer M Krug r.m.k...@gmail.com writes: On Thu, Jul 8, 2010 at 9:03 PM, Eric Schulte schulte.e...@gmail.com wrote: [...] (add-hook 'org-babel-post-tangle-hook (lambda () (ess-load-file (buffer-file-name Unfortunately, this does not work. I put the code above into my emacs.organd nothing happens - not even an error message. I tried to use the C-h v to customise the variable, but I don't manage it. If the variable isn't registered with C-h v, then it sounds like maybe you need to update Org-mode, and/or re-run make clean make. OK - that is working now. In addition, The filename for es-load-file shoud not be the buffer name, but the buffer name with the extension replaced with R. `buffer-file-name', returns the name of the file that the buffer is visiting, so wouldn't this already be the case if the filename ends with .R? Isn't the buffer from which I am tangling the org buffer, and not the result from the tangling? (see below for further remarks. No this hook is run from /within/ a buffer visiting the file of tangled code, so in the example hook function above (buffer-file-name) will equal the name of the file of tangled R code. From your later message it looks like the issues below have been resolved. Thanks a lot for a very useful addition, and I will see abut the buffer-name and come back if it is still the org-file buffer for me, I finally tried it out, and it is still the same: when I tangle an org file, for the hook as defined above, buffer-file-name is the org file. Cheers, Raienr Rainer Best -- Eric This minimal example with the hook defined as above works for me. After tangling I can jump to the *R* buffer where both x and y are defined. --8---cut here---start-8--- ** tangle R and load :PROPERTIES: :tangle: to-load.r :END: #+begin_src R :comments yes x - 8 #+end_src #+begin_src R y - 9 #+end_src --8---cut here---end---8--- Not here - Emacs and org-mode version: GNU Emacs 23.2.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1) Org-mode version 6.36trans (release_6.36.603.g227b) 1) if no R process is running, I get the following message: ess-start-process-specific: No ESS processes running; not yet implemented to start (Initial,nil) No problem 0 I can start an R process manually. 2) when an R session is running, I get the following error message from ESS: Errors: Use C-c ` to find error. Symbol's function definition is void: with-temp-filebuffer and from ESS: Error in source(/home/rkrug/tmp/R.org) : /home/rkrug/tmp/R.org:1:1: unexpected '^' 1: ** it seems to submit the org file (the buffer is saved as R.org) to R. So buffer-file-name should actually be replaced with the name from the file name resulting from the tangling, in the easiest case (which would be fine with me) the org buffer name with .org replaced with .R. So I did the following (my firs elisp code!): (add-hook 'org-babel-post-tangle-hook (lambda () (ess-load-file (replace-regexp-in-string .org .R buffer-file-name and it is working - except that I still get the Symbol's function
[Orgmode] Re: Behavior of Gnus when called from an hyperlink
Sébastien Vauban wxhgmqzgw...@spammotel.com writes: Hi Sébastien, The function `nnimap-request-article-part' gets called several times. --8---cut here---start-8--- (defun nnimap-request-article-part (article part prop optional group server to-buffer detail) (when (nnimap-possibly-change-group group server) (let ((article (if (stringp article) (car-safe (imap-search (format HEADER Message-Id \%s\ article) nnimap-server-buffer)) article))) (when article ;; [...] --8---cut here---end---8--- The first couple of times happen quickly, with `article' 140579, then 140580, then 140581. After that, (real) things happen: --8---cut here---start-8--- IMAP split moved mc:INBOX:140581 to INBOX.scorpios nnimap: Updating info for nnimap+mc:INBOX.mc...done Retrieving newsgroup: nnimap+mc:INBOX.mc... nnimap: Updating info for nnimap+mc:INBOX.mc...done Fetching headers for nnimap+mc:INBOX.mc...done Scoring...done Making sparse threads...done Sorting threads...done Generating summary...done No more unread articles --8---cut here---end---8--- and I have the top buffer displaying the subject of the linked article I'm after. Already something... What follows is stepping another time in the function `nnimap-request-article-part', this time with `article' 871vbrxzo6@mundaneum.com (not a number anymore). I'm then directed in the then part of the if-then-else (testing if `article' is a string or not). And, then, what stops me for 5 mins is the `imap-search' call. Hm, ok. So it seems that fetching an article by its Message-id is the slow part. And of course, org-gnus *always* fetches by message-ids, couse that's the message attribute you can rely on. Article numbers are not that static: for example when moving messages to another group and back again... (Some people do that to fill gaps in the article numbers and fix the wrong unread count issue.) I guess I will have to dive that side (not now -- going to sleep). Don't know if that gives hints yet, or not... Well, now we know that there are issues when searching for a message-id. Please go on edebugging `imap-search'. ;-) Please check, if that function is that slow for all message-ids or if that's only for some. The function has a FIXME: Should this try to use CHARSET? -- fx, and maybe this answer has to be answered with Yes! And check what's in the buffer that function operates on: `nnimap-server-buffer'. As a side-node: Since lately, my gnus hangs when I try to post to our university's newsserver using a TLS or SSL connection. Without an encrypted connection, it works again. I don't have a clue what's going wrong, but somehow there's a miscommunication between gnus and the server... Bye, Tassilo ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
Congratulations and thanks for this amazing software. Yours, Christian Moe Carsten Dominik wrote: Hi everyone, I have just released version 7.01 of Org mode. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
Carsten, as always, thanks for an incredible job! The announcement of this new release has motivated me to back up to speed with org-babel and the changes that have been done to simplify it. I had previously written interfaces for jython, ledger and maxima. These have not worked since the simplification work on org-babel started and I haven't had the time to do anything about it. I would now like to get these working again and hopefully contribute them to org. However, there does not appear to be any documentation on writing support for new languages. Before I delve into existing codes (which is what I did last time), I just want to confirm that this is indeed the case? Thanks again, eric -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: word wrap preferences in org-mode buffers
Eric S Fraga ucec...@ucl.ac.uk writes: On Fri, 16 Jul 2010 14:37:54 -0500, Erik Iverson er...@ccbr.umn.edu wrote: Hello, As I use org-mode more and more for actually writing things, I'm wondering what your favorite Emacs word/line-wrapping mode is. Basically, I see two main ways of doing this, auto-fill-mode and visual-line-mode. Any others that you all use? If you use auto-fill-mode or visual-line-mode, are there any obvious drawbacks, particularly regarding org-tables and source code blocks. I'm sure I'll run into the main issues eventually, but thought I'd ask up front. Thanks, Erik ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode I use auto-fill-mode most of the time. However, if I'm mixing code and text, I tend to turn it off. In that case, it's an easy matter of hitting M-q (fill-paragraph) every now and again to re-format the current paragraph. I often do this without even realising... (just did it now, in fact :-). I always faced this problem and I didn't know that there is this key binding. Thank you! Thanks and Regards Noorul ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
On 19.07.2010, at 10:22, Christian Moe wrote: Congratulations and thanks for this amazing software. Yours, Christian Moe +1 Carsten Dominik wrote: Hi everyone, I have just released version 7.01 of Org mode. -- Dr. Stefan Vollmar, Dipl.-Phys. Head of IT group Max-Planck-Institut für neurologische Forschung Gleuelerstr. 50, 50931 Köln, Germany Tel.: +49-221-4726-213 FAX +49-221-4726-298 Tel.: +49-221-478-5713 Mobile: 0160-93874279 Email: voll...@nf.mpg.de http://www.nf.mpg.de smime.p7s Description: S/MIME cryptographic signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [babel] show R commands in html export
Is it possible that org-babel shows not just the output of R commands but also R commands themselves in the html output? I could perhaps write the commands twice, once outside the code block (to make the commands appear as they are), and once inside the codeblock to display output of those commands. But is there a better solution? If using them twice is the only way, what would be the best way to set the code (when typed outside the codeblock) so that it is formatted properly in the html output? Vikas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Patchwork: Patch 65 Accepted
Patch 65 (http://patchwork.newartisans.com/patch/65/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3C20100622.143610.09007983.mikelygee%40no8wireless.co.nz%3E ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Estimate ranges in column view
Michael,
I have applied the patch - please check it if it is still working
correctly.
Thanks!
- Carsten
On Jun 22, 2010, at 4:36 AM, Michael Gauland wrote:
Carsten,
Here is a patch for a new 'est+' summary type, including
corresponding changes for xemacs and the manual. I've done basic
testing on the GNU emacs version, but not the xemacs code.
I'm not sure the change to the manual provides the right amount of
information
in the right place; I'd be happy to re-write to make it find in
better. Similarly, the name of the summary type is entirely up to you.
I didn't know whether to send this directly to you, or to the list;
if it should go to the list I'd be happy to send it there directly.
Thanks for the chance to contribute,
Mike
diff --git a/doc/org.texi b/doc/org.texi
index 17615e0..529be4d 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -4723,9 +4723,10 @@ optional. The individual parts have the
following meaning:
@{:m...@}@r{Smallest time value in column.}
@{:m...@}@r{Largest time value.}
@{:m...@} @r{Arithmetic mean of time values.}
-@{@@m...@} @r{Minimum age (in days/hours/mins/
seconds).}
-@{@@m...@} @r{Maximum age (in days/hours/mins/
seconds).}
-@{@@m...@} @r{Arithmetic mean of ages (in days/
hours/mins/seconds).}
+@{@@m...@}@r{Minimum age (in days/hours/mins/
seconds).}
+@{@@m...@}@r{Maximum age (in days/hours/mins/
seconds).}
+@{@@m...@} @r{Arithmetic mean of ages (in days/
hours/mins/seconds).}
+@{e...@}@r{Add low-high estimates.}
@end example
@noindent
@@ -4733,6 +4734,22 @@ Be aware that you can only have one summary
type for any property you
include. Subsequent columns referencing the same property will all
display the
same summary information.
+The 'est+' summary type requires further explanation. It is used for
+combining task estimates, expressed as low-high ranges. For
example, instead
+of estimating a particular task will take 5 days, you might
estimate it as
+5-6 days if you're fairly confident you know how much woark is
required, or
+1-10 days if you don't really know what needs to be done. Both
ranges
+average at 5.5 days, but the first represents a more predictable
delivery.
+
+When combining a set of such estimates, simply adding the lows and
highs
+produces an unrealistically wide result. Instead, 'est+' adds the
statistical
+mean and variance of the sub-tasks, generating a final estimate
from the sum.
+For example, suppose you had ten tasks, each of which was estimated
at 0.5 to
+2 days of work. Straight addition produces an estimate of 5 to 20
days,
+representing what to expect if everything goes either extremely
well or
+extremely poorly. In contrast, 'est+' estimates the full job more
+realistically, at 10-15 days.
+
Here is an example for a complete columns definition, along with
allowed
values.
diff --git a/lisp/org-colview-xemacs.el b/lisp/org-colview-xemacs.el
index 152d9fe..90bf4c4 100644
--- a/lisp/org-colview-xemacs.el
+++ b/lisp/org-colview-xemacs.el
@@ -917,7 +917,8 @@ around it.
(@max max_age max (lambda (x) (- org-columns-time x)))
(@mean mean_age
(lambda (rest x) (/ (apply '+ x) (float (length x
- (lambda (x) (- org-columns-time x
+ (lambda (x) (- org-columns-time x)))
+(est+ estimate org-estimate-combine))
Operator - format,function,calc map.
Used to compile/uncompile columns format and completing read in
interactive function org-columns-new.
@@ -1206,6 +1207,7 @@ Don't set this, this is meant for dynamic
scoping.)
(defun org-columns-number-to-string (n fmt optional printf)
Convert a computed column number to a string value, according to
FMT.
(cond
+ ((memq fmt '(estimate)) (org-estimate-print n printf))
((not (numberp n)) )
((memq fmt '(add_times max_times min_times mean_times))
(let* ((h (floor n)) (m (floor (+ 0.5 (* 60 (- n h))
@@ -1250,9 +1252,9 @@ Don't set this, this is meant for dynamic
scoping.)
(setq sum (+ (string-to-number (pop l)) (/ sum 60
sum))
((memq fmt '(checkbox checkbox-n-of-m checkbox-percent))
- (if (equal s [X]) 1. 0.01))
- (t (string-to-number s)))
-0))
+(if (equal s [X]) 1. 0.01))
+ ((memq fmt '(estimate)) (org-string-to-estimate s))
+ (t (string-to-number s)
(defun org-columns-uncompile-format (cfmt)
Turn the compiled columns format back into a string
representation.
@@ -1693,6 +1695,42 @@ This will add overlays to the date lines, to
show the summary for each day.
(format %dd %02dh %02dm %02ds days hours minutes seconds))
))
+(defun org-estimate-mean-and-var (v)
+ Return the mean and variance of an estimate.
+ (let* ((low (float (car v)))
+ (high (float (cadr v)))
+ (mean (/ (+ low high) 2.0))
+
Re: [Orgmode] Re: Behavior of Gnus when called from an hyperlink
Tassilo Horn wrote: I guess I will have to dive that side (not now -- going to sleep). Don't know if that gives hints yet, or not... Please check, if that function is that slow for all message-ids or if that's only for some. The function has a FIXME: Should this try to use CHARSET? -- fx, and maybe this answer has to be answered with Yes! I think this is not very likely: With the CHARSET argument a client can inform the server that the search string is in a charset different than the default 7bit ASCII (Cf. rfc3501, 6.4.4). You could rule out the server being the culprit by performing the search manually: gnutls-cli --crlf --port 993 your.mail.host.here 0x1 LOGIN user password 0x2 SELECT Inbox.work 0x3 SEARCH HEADER Message-ID message id w/o angle brackets 0x4 LOGOUT My main account uses Courier on Debian, too and search for a particular message id within ~7000 messages is quite fast. Couldn't find this information in the tread: Is it slow for a particular message or slow on Inbox.work in general? HTH, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgp1fUJvlUMHd.pgp Description: PGP signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] question about date-tree
Dear Experts, I really like the date-tree feature of org-remember and use it to plan my daily agenda. Often I want to plan things in the future and fill out an entry for a couple of weeks hence. It's slightly annoying to try to remember the day of week and date so that it will match the date-tree format. Is there a function/utility/suggestion for prepopulating a month's worth of date-tree daily nodes? Thanks, -Emin ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [PATCH] org-capture with LISP function template
Hi Carsten, I think the original problem is in the defcustom specification: org-capture.el L292 (choice :tag Template (string) (list :tag File (const :format file) (file :tag Template file)) (list :tag Function (const :format function) (file :tag Template function))) The last line should read 'sexp' instead of 'file'. This is why the function is being held as a string. Saludos, .j. On Mon, Jul 19, 2010 at 09:05:06AM +0200, Carsten Dominik wrote: the function must be a symbol in this setup, not a string. I am rejecting this patch. On Jul 19, 2010, at 3:45 AM, Juan Pechiar wrote: Below is a patch for org-capture when the template is given by a LISP function. Problem was that the function is inside a string (not a LISP form), so the string has to be evaluated explicitly. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode release 7.01
Carsten Dominik carsten.domi...@gmail.com writes: This is a major release, and we have worked months on getting it together. Most important is of cause the complete integration of Org Babel into Org mode. Many thanks to Eric Schulte and Dan Davison who have worked tirelessly to make this happen. Thomas S. Dye gets credit here as well because he did a lot of work on documentation and function/variable docstrings. Thanks, Carsten, for another brilliant release! And a special thanks to Eric Schulte for taking into account my concerns about security and org-babel and for finding a very graceful solution. Best, Matt ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: [PATCH] org-capture with LISP function template
On Jul 19, 2010, at 2:26 PM, Juan wrote: Hi Carsten, I think the original problem is in the defcustom specification: org-capture.el L292 (choice :tag Template (string) (list :tag File (const :format file) (file :tag Template file)) (list :tag Function (const :format function) (file :tag Template function))) The last line should read 'sexp' instead of 'file'. This is why the function is being held as a string. Indeed, thanks. - Carsten Saludos, .j. On Mon, Jul 19, 2010 at 09:05:06AM +0200, Carsten Dominik wrote: the function must be a symbol in this setup, not a string. I am rejecting this patch. On Jul 19, 2010, at 3:45 AM, Juan Pechiar wrote: Below is a patch for org-capture when the template is given by a LISP function. Problem was that the function is inside a string (not a LISP form), so the string has to be evaluated explicitly. - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [babel] show R commands in html export
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 19/07/2010 13:51, Vikas Rawal wrote: Is it possible that org-babel shows not just the output of R commands but also R commands themselves in the html output? Yes. Look at the header argument exports: : as stated in the manual: 14.8.2.5 :exports The :exports header argument specifies what should be included in HTML or LaTeX exports of the Org-mode file. ? code The default. The body of code is included into the exported file. E.g., :exports code. ? results The result of evaluating the code is included in the exported file. E.g., :exports results. ? both Both the code and results are included in the exported file. E.g., :exports both. ? none Nothing is included in the exported file. E.g., :exports none. That should solve your problem. Cheers, Rainer I could perhaps write the commands twice, once outside the code block (to make the commands appear as they are), and once inside the codeblock to display output of those commands. But is there a better solution? If using them twice is the only way, what would be the best way to set the code (when typed outside the codeblock) so that it is formatted properly in the html output? Vikas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - -- Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany) Centre of Excellence for Invasion Biology Natural Sciences Building Office Suite 2039 Stellenbosch University Main Campus, Merriman Avenue Stellenbosch South Africa Tel:+33 - (0)9 53 10 27 44 Cell: +27 - (0)8 39 47 90 42 Fax (SA): +27 - (0)8 65 16 27 82 Fax (D) : +49 - (0)3 21 21 25 22 44 Fax (FR): +33 - (0)9 58 10 27 44 email: rai...@krugs.de Skype: RMkrug -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxERzoACgkQoYgNqgF2egrzZwCfblz8+7ULmso9nn1E+3tjUcEP VZ4An1P5Tyfi53kKXAGZNGoNKZz4IK0K =aI5o -END PGP SIGNATURE- ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Org-Mode button
Advocating Org-Mode is always a noble cause. In order to do so, I've put together a created with Org-Mode button which is displayed on my website. Although I'm far from being a designer type of guy, you may want to have a look at http://ulf.zeitform.de/images/org-mode.png. Of course you are very welcome to use that button yourself or come up with an improved version. Ulf ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [babel] show R commands in html export
E.g., :exports both. Works beautifully. Thanks very much, Vikas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
Hi all, Just a quick note that the documentation for org-babel does not appear to be in place yet. That is, when I click on the Source Code link from http://orgmode.org/manual/ I get a 404 Not Found error. Looking forward to trying out the new version, thanks to everyone involved! Org-mode has completely changed the way I use emacs. It is simply amazing. Best, Ista On Mon, Jul 19, 2010 at 6:43 AM, Carsten Dominik carsten.domi...@gmail.com wrote: Hi everyone, I have just released version 7.01 of Org mode. This is a major release, and we have worked months on getting it together. Most important is of cause the complete integration of Org Babel into Org mode. Many thanks to Eric Schulte and Dan Davison who have worked tirelessly to make this happen. Thomas S. Dye gets credit here as well because he did a lot of work on documentation and function/variable docstrings. Also, I need to shout out my gratitude to the increasing number of volunteers in the project. John Wiegley's patchwork server has done wonders for streamlining the process of reviewing and applying patches. I have applied dozens of patches though this process, just in the last week. The issue tracker by David Maus has finally brought some structure into the stream of ideas and reports on this mailing list, at a moment when I was about to falter under the amount of work maintaining this project means for me. Frankly, right now I don't know how I would do things without David's competent and efficient help - he has effectively and silently become co-maintainer of this project. Below these tips above the waterline, there is an iceberg of contributions large and small by so many people. We have 54 people with FSF papers now, and more contributors of tiny patches. Also there are the volunteers that manage the mailing list, Worg, and the FAQ. I am truly humbled and made proud at the same time by each and every contribution that the Org mode projects receives. These contributions made Org mode the phenomenon it now is. Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. P.P.S. The feature freeze is over now. Changes in Version 7.01 === Incompatible Changes ~ Emacs 21 support has been dropped == Do not use Org mode 7.xx with Emacs 21, use [version 6.36c] instead. [version 6.36c]: http://orgmode.org/org-6.36c.zip XEmacs support requires the XEmacs development version === To use Org mode 7.xx with XEmacs, you need to run the developer version of XEmacs. I was about to drop XEmacs support entirely, but Michael Sperber stepped in and made changes to XEmacs that made it easier to keep the support. Thanks to Michael for this last-minute save. I had hoped to be able to remove xemacs/noutline.el from release 7 by moving it into XEmacs, but this is not yet done. Org-babel configuration changes Babel took the integration into Org-mode as an opportunity to do some much needed house cleaning. Most importantly we have simplified the enabling of language support, and cleared out unnecessary configuration variables -- which is great unless you already have a working configuration under the old model. The most important changes regard the /location/ and /enabling/ of Babel (both core functionality and language specific support). Babel: Babel is now part of the core of Org-mode, so it is now loaded along with the rest of Org-mode. That means that there is /no configuration/ required to enable the main Babel functionality. For current users, this means that statements like (require 'org-babel) or (require 'org-babel-init) that may by lying around in your configuration must now be removed. load path: Babel (including all language specific files -- aside from those which are located in the =contrib/= directory for reasons of licencing) now lives in the base of the Org-mode lisp directory, so /no additional directories/ need to be added to your load path to use babel. For Babel users this means that statements adding babel-specific directories to your load-path should now be removed from your config. language support: It is no longer necessary to require language specific support on a language-by-language basis. Specific language support should now be managed through the `org-babel-load-languages' variable. This variable can be customized using the Emacs customization
Re: [Orgmode] Org-mode release 7.01
On Mon, Jul 19, 2010 at 6:43 AM, Carsten Dominik carsten.domi...@gmail.com wrote: Hi everyone, I have just released version 7.01 of Org mode. This is a major release, and we have worked months on getting it together. Sincere thanks and congratulations on the release to all contributors. There is more happening in Org than I can try out and integrate in my workflow at a sane pace.. the backlog has been growing for a while now. One Carsten was difficult to keep pace with and now we have others too. Sheesh. :) Can't thank you all enough for your hard work. Best regards -- Manish ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
On 07/19/2010 10:55 AM, Manish wrote: There is more happening in Org than I can try out and integrate in my workflow at a sane pace.. the backlog has been growing for a while now. One Carsten was difficult to keep pace with and now we have others too. Sheesh. :) Can't thank you all enough for your hard work. I have to agree. Org-mode has many features that I don't use but would like to use. Someday, I'll get completely organized with org-mode, but I'll have to settle for partly organized for now. It took forever before I upgraded to 6.36c, and now we have wonderful 7.01. Well, at least there is a new toy to think about getting. Org-mode is the best mode. Scott Randby ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] inline image display not working when org-indent-mode active
On Jul 18, 2010, at 9:42 PM, David Maus wrote: Erik Iverson wrote: Hello! Just pulled the latest org-mode from git. I've upgraded to Emacs 23.2 so that org-indent-mode works properly. However, when org-indent-mode is active, it seems that inline images (C-c C-x C-v) do not work properly. They show up for a brief time ( 1 second) and then promptly return to showing just the file link. Turning off org-indent-mode and re-toggling image display shows the image properly. If it matters, these files were created in org-babel source blocks. Can anyone reproduce this? Yes, I can reproduce this with Org-mode version 6.36trans I also see this bug, but I am clueles as to what might cause this issue. Image display uses overlays, org-indent-mode uses text properties, but it seems that adding these properties somehow removes the overlays from the buffer - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
On Jul 19, 2010, at 3:47 PM, Ista Zahn wrote: Hi all, Just a quick note that the documentation for org-babel does not appear to be in place yet. That is, when I click on the Source Code link from http://orgmode.org/manual/ I get a 404 Not Found error. The documentation is in place, but there is a broken link. The correct link is here: http://orgmode.org/manual/Working-With-Source-Code.html#Working-With-Source-Code I will soon upload a minor fix 7.01a which will also fix the link. - Carsten Looking forward to trying out the new version, thanks to everyone involved! Org-mode has completely changed the way I use emacs. It is simply amazing. Best, Ista On Mon, Jul 19, 2010 at 6:43 AM, Carsten Dominik carsten.domi...@gmail.com wrote: Hi everyone, I have just released version 7.01 of Org mode. This is a major release, and we have worked months on getting it together. Most important is of cause the complete integration of Org Babel into Org mode. Many thanks to Eric Schulte and Dan Davison who have worked tirelessly to make this happen. Thomas S. Dye gets credit here as well because he did a lot of work on documentation and function/variable docstrings. Also, I need to shout out my gratitude to the increasing number of volunteers in the project. John Wiegley's patchwork server has done wonders for streamlining the process of reviewing and applying patches. I have applied dozens of patches though this process, just in the last week. The issue tracker by David Maus has finally brought some structure into the stream of ideas and reports on this mailing list, at a moment when I was about to falter under the amount of work maintaining this project means for me. Frankly, right now I don't know how I would do things without David's competent and efficient help - he has effectively and silently become co-maintainer of this project. Below these tips above the waterline, there is an iceberg of contributions large and small by so many people. We have 54 people with FSF papers now, and more contributors of tiny patches. Also there are the volunteers that manage the mailing list, Worg, and the FAQ. I am truly humbled and made proud at the same time by each and every contribution that the Org mode projects receives. These contributions made Org mode the phenomenon it now is. Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. P.P.S. The feature freeze is over now. Changes in Version 7.01 === Incompatible Changes ~ Emacs 21 support has been dropped == Do not use Org mode 7.xx with Emacs 21, use [version 6.36c] instead. [version 6.36c]: http://orgmode.org/org-6.36c.zip XEmacs support requires the XEmacs development version === To use Org mode 7.xx with XEmacs, you need to run the developer version of XEmacs. I was about to drop XEmacs support entirely, but Michael Sperber stepped in and made changes to XEmacs that made it easier to keep the support. Thanks to Michael for this last-minute save. I had hoped to be able to remove xemacs/noutline.el from release 7 by moving it into XEmacs, but this is not yet done. Org-babel configuration changes Babel took the integration into Org-mode as an opportunity to do some much needed house cleaning. Most importantly we have simplified the enabling of language support, and cleared out unnecessary configuration variables -- which is great unless you already have a working configuration under the old model. The most important changes regard the /location/ and /enabling/ of Babel (both core functionality and language specific support). Babel: Babel is now part of the core of Org-mode, so it is now loaded along with the rest of Org-mode. That means that there is /no configuration/ required to enable the main Babel functionality. For current users, this means that statements like (require 'org-babel) or (require 'org-babel-init) that may by lying around in your configuration must now be removed. load path: Babel (including all language specific files -- aside from those which are located in the =contrib/= directory for reasons of licencing) now lives in the base of the Org-mode lisp directory, so /no additional directories/ need to be added to your load path to use babel. For Babel users this means that statements adding babel-specific directories to your load-path should now be removed from your config. language support: It is no longer necessary to require language
Re: [Orgmode] Org-mode release 7.01
On Jul 19, 2010, at 5:31 PM, Scott Randby wrote: On 07/19/2010 10:55 AM, Manish wrote: There is more happening in Org than I can try out and integrate in my workflow at a sane pace.. the backlog has been growing for a while now. One Carsten was difficult to keep pace with and now we have others too. Sheesh. :) Can't thank you all enough for your hard work. I have to agree. Org-mode has many features that I don't use but would like to use. Someday, I'll get completely organized with org-mode, but I'll have to settle for partly organized for now. That is OK, and Org is even meant to be used in this way :) It took forever before I upgraded to 6.36c, and now we have wonderful 7.01. Well, at least there is a new toy to think about getting. Org-mode is the best mode. Scott Randby ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] footer for latex export
Thanks.
On Mon, Jul 12, 2010 at 1:57 PM, Nick Dokos nicholas.do...@hp.com wrote:
Buck Brody buckbr...@gmail.com wrote:
I am just getting started with LaTeX. I can't seem to figure out how
to add a footer to my document.
I don't think that orgmode provides built-in support for this, but it
does provide mechanisms so that you can do it by hand. The most flexible
header/footer package that I know of is fancyhdr by Piet van Oostrum:
http://www.tex.ac.uk/tex-archive/macros/latex/contrib/fancyhdr/
which provides for 3-part headers and footers with a lot of flexibility.
The PDF doc in the above directory describes it all in clear detail.
Here is a (fairly rudimentary) attempt to do that in an org-mode file:
--8---cut here---start-8---
#+LATEX_HEADER: \usepackage{fancyhdr}
#+LATEX_HEADER: \pagestyle{fancy} \renewcommand{\headrulewidth}{0pt} \lhead{}
\chead{} \rhead{} \lfoot{} \cfoot{Centered footer} \rfoot{}
#+LaTeX: \thispagestyle{fancy}
* Foo
bar
* Foo2
bar2
#+LaTeX: \newpage
* Foo3
bar3
--8---cut here---end---8---
whose only effect is to replace the default centered page number
by the string Centered footer.
HTH,
Nick
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode release 7.01
Carsten Dominik carsten.domi...@gmail.com writes: [snip] Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. This might be a bit OT, I apoligize, but how exactly do I get the new release with git? I'm new to git, and I've tried the following: 1. Change the branch to maint 2. git pull git://repo.or.cz/org-mode.git maint All I get is a list of Merge conflicts from the Auto-merging as shown below. I must be doing something wrong, it'd be great if one of the git wizards could help me out :-) Thanks and cheers, and tons of thanks to Carsten and all contributors!! Markus The merge conflicts I get: From git://repo.or.cz/org-mode * branchmaint - FETCH_HEAD Auto-merging ORGWEBPAGE/index.org Auto-merging README_DIST CONFLICT (content): Merge conflict in README_DIST Auto-merging doc/org.texi CONFLICT (content): Merge conflict in doc/org.texi Auto-merging doc/orgcard.tex CONFLICT (content): Merge conflict in doc/orgcard.tex Auto-merging lisp/ob-C.el CONFLICT (content): Merge conflict in lisp/ob-C.el Auto-merging lisp/ob-R.el CONFLICT (content): Merge conflict in lisp/ob-R.el Auto-merging lisp/ob-asymptote.el CONFLICT (content): Merge conflict in lisp/ob-asymptote.el Auto-merging lisp/ob-clojure.el CONFLICT (content): Merge conflict in lisp/ob-clojure.el Auto-merging lisp/ob-comint.el CONFLICT (content): Merge conflict in lisp/ob-comint.el Auto-merging lisp/ob-css.el CONFLICT (content): Merge conflict in lisp/ob-css.el Auto-merging lisp/ob-ditaa.el CONFLICT (content): Merge conflict in lisp/ob-ditaa.el Auto-merging lisp/ob-dot.el CONFLICT (content): Merge conflict in lisp/ob-dot.el Auto-merging lisp/ob-emacs-lisp.el CONFLICT (content): Merge conflict in lisp/ob-emacs-lisp.el Auto-merging lisp/ob-eval.el CONFLICT (content): Merge conflict in lisp/ob-eval.el Auto-merging lisp/ob-exp.el CONFLICT (content): Merge conflict in lisp/ob-exp.el Auto-merging lisp/ob-gnuplot.el CONFLICT (content): Merge conflict in lisp/ob-gnuplot.el Auto-merging lisp/ob-haskell.el CONFLICT (content): Merge conflict in lisp/ob-haskell.el Auto-merging lisp/ob-keys.el CONFLICT (content): Merge conflict in lisp/ob-keys.el Auto-merging lisp/ob-latex.el CONFLICT (content): Merge conflict in lisp/ob-latex.el Auto-merging lisp/ob-lob.el CONFLICT (content): Merge conflict in lisp/ob-lob.el Auto-merging lisp/ob-matlab.el CONFLICT (content): Merge conflict in lisp/ob-matlab.el Auto-merging lisp/ob-mscgen.el CONFLICT (content): Merge conflict in lisp/ob-mscgen.el Auto-merging lisp/ob-ocaml.el CONFLICT (content): Merge conflict in lisp/ob-ocaml.el Auto-merging lisp/ob-octave.el CONFLICT (content): Merge conflict in lisp/ob-octave.el Auto-merging lisp/ob-perl.el CONFLICT (content): Merge conflict in lisp/ob-perl.el Auto-merging lisp/ob-python.el CONFLICT (content): Merge conflict in lisp/ob-python.el Auto-merging lisp/ob-ref.el CONFLICT (content): Merge conflict in lisp/ob-ref.el Auto-merging lisp/ob-ruby.el CONFLICT (content): Merge conflict in lisp/ob-ruby.el Auto-merging lisp/ob-sass.el CONFLICT (content): Merge conflict in lisp/ob-sass.el Auto-merging lisp/ob-screen.el CONFLICT (content): Merge conflict in lisp/ob-screen.el Auto-merging lisp/ob-sh.el CONFLICT (content): Merge conflict in lisp/ob-sh.el Auto-merging lisp/ob-sql.el CONFLICT (content): Merge conflict in lisp/ob-sql.el Auto-merging lisp/ob-sqlite.el CONFLICT (content): Merge conflict in lisp/ob-sqlite.el Auto-merging lisp/ob-table.el CONFLICT (content): Merge conflict in lisp/ob-table.el Auto-merging lisp/ob-tangle.el CONFLICT (content): Merge conflict in lisp/ob-tangle.el Auto-merging lisp/ob.el CONFLICT (content): Merge conflict in lisp/ob.el Auto-merging lisp/org-agenda.el CONFLICT (content): Merge conflict in lisp/org-agenda.el Auto-merging lisp/org-archive.el CONFLICT (content): Merge conflict in lisp/org-archive.el Auto-merging lisp/org-ascii.el CONFLICT (content): Merge conflict in lisp/org-ascii.el Auto-merging lisp/org-attach.el CONFLICT (content): Merge conflict in lisp/org-attach.el Auto-merging lisp/org-bbdb.el CONFLICT (content): Merge conflict in lisp/org-bbdb.el Auto-merging lisp/org-beamer.el CONFLICT (content): Merge conflict in lisp/org-beamer.el Auto-merging lisp/org-bibtex.el CONFLICT (content): Merge conflict in lisp/org-bibtex.el Auto-merging lisp/org-capture.el CONFLICT (content): Merge conflict in lisp/org-capture.el Auto-merging lisp/org-clock.el CONFLICT (content): Merge conflict in lisp/org-clock.el Auto-merging lisp/org-colview-xemacs.el CONFLICT (content): Merge conflict in lisp/org-colview-xemacs.el Auto-merging lisp/org-colview.el CONFLICT (content): Merge conflict in lisp/org-colview.el Auto-merging lisp/org-compat.el
[Orgmode] Re: Org-mode release 7.01
Markus Heller helle...@gmail.com writes: Carsten Dominik carsten.domi...@gmail.com writes: [snip] Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. This might be a bit OT, I apoligize, but how exactly do I get the new release with git? I'm new to git, and I've tried the following: 1. Change the branch to maint 2. git pull git://repo.or.cz/org-mode.git maint That command tries to merge maint with the branch you're currently on - most likely main. If you do not have manual changes in your working tree you can run git reset --hard to undo that merge. I think what you want is: git pull git checkout -t origin/maint Andreas All I get is a list of Merge conflicts from the Auto-merging as shown below. I must be doing something wrong, it'd be great if one of the git wizards could help me out :-) Thanks and cheers, and tons of thanks to Carsten and all contributors!! Markus The merge conflicts I get: From git://repo.or.cz/org-mode * branchmaint - FETCH_HEAD Auto-merging ORGWEBPAGE/index.org Auto-merging README_DIST CONFLICT (content): Merge conflict in README_DIST Auto-merging doc/org.texi CONFLICT (content): Merge conflict in doc/org.texi Auto-merging doc/orgcard.tex CONFLICT (content): Merge conflict in doc/orgcard.tex Auto-merging lisp/ob-C.el CONFLICT (content): Merge conflict in lisp/ob-C.el Auto-merging lisp/ob-R.el CONFLICT (content): Merge conflict in lisp/ob-R.el Auto-merging lisp/ob-asymptote.el CONFLICT (content): Merge conflict in lisp/ob-asymptote.el Auto-merging lisp/ob-clojure.el CONFLICT (content): Merge conflict in lisp/ob-clojure.el Auto-merging lisp/ob-comint.el CONFLICT (content): Merge conflict in lisp/ob-comint.el Auto-merging lisp/ob-css.el CONFLICT (content): Merge conflict in lisp/ob-css.el Auto-merging lisp/ob-ditaa.el CONFLICT (content): Merge conflict in lisp/ob-ditaa.el Auto-merging lisp/ob-dot.el CONFLICT (content): Merge conflict in lisp/ob-dot.el Auto-merging lisp/ob-emacs-lisp.el CONFLICT (content): Merge conflict in lisp/ob-emacs-lisp.el Auto-merging lisp/ob-eval.el CONFLICT (content): Merge conflict in lisp/ob-eval.el Auto-merging lisp/ob-exp.el CONFLICT (content): Merge conflict in lisp/ob-exp.el Auto-merging lisp/ob-gnuplot.el CONFLICT (content): Merge conflict in lisp/ob-gnuplot.el Auto-merging lisp/ob-haskell.el CONFLICT (content): Merge conflict in lisp/ob-haskell.el Auto-merging lisp/ob-keys.el CONFLICT (content): Merge conflict in lisp/ob-keys.el Auto-merging lisp/ob-latex.el CONFLICT (content): Merge conflict in lisp/ob-latex.el Auto-merging lisp/ob-lob.el CONFLICT (content): Merge conflict in lisp/ob-lob.el Auto-merging lisp/ob-matlab.el CONFLICT (content): Merge conflict in lisp/ob-matlab.el Auto-merging lisp/ob-mscgen.el CONFLICT (content): Merge conflict in lisp/ob-mscgen.el Auto-merging lisp/ob-ocaml.el CONFLICT (content): Merge conflict in lisp/ob-ocaml.el Auto-merging lisp/ob-octave.el CONFLICT (content): Merge conflict in lisp/ob-octave.el Auto-merging lisp/ob-perl.el CONFLICT (content): Merge conflict in lisp/ob-perl.el Auto-merging lisp/ob-python.el CONFLICT (content): Merge conflict in lisp/ob-python.el Auto-merging lisp/ob-ref.el CONFLICT (content): Merge conflict in lisp/ob-ref.el Auto-merging lisp/ob-ruby.el CONFLICT (content): Merge conflict in lisp/ob-ruby.el Auto-merging lisp/ob-sass.el CONFLICT (content): Merge conflict in lisp/ob-sass.el Auto-merging lisp/ob-screen.el CONFLICT (content): Merge conflict in lisp/ob-screen.el Auto-merging lisp/ob-sh.el CONFLICT (content): Merge conflict in lisp/ob-sh.el Auto-merging lisp/ob-sql.el CONFLICT (content): Merge conflict in lisp/ob-sql.el Auto-merging lisp/ob-sqlite.el CONFLICT (content): Merge conflict in lisp/ob-sqlite.el Auto-merging lisp/ob-table.el CONFLICT (content): Merge conflict in lisp/ob-table.el Auto-merging lisp/ob-tangle.el CONFLICT (content): Merge conflict in lisp/ob-tangle.el Auto-merging lisp/ob.el CONFLICT (content): Merge conflict in lisp/ob.el Auto-merging lisp/org-agenda.el CONFLICT (content): Merge conflict in lisp/org-agenda.el Auto-merging lisp/org-archive.el CONFLICT (content): Merge conflict in lisp/org-archive.el Auto-merging lisp/org-ascii.el CONFLICT (content): Merge conflict in lisp/org-ascii.el Auto-merging lisp/org-attach.el CONFLICT (content): Merge conflict in lisp/org-attach.el Auto-merging lisp/org-bbdb.el CONFLICT (content): Merge conflict in lisp/org-bbdb.el Auto-merging lisp/org-beamer.el CONFLICT (content): Merge conflict in lisp/org-beamer.el Auto-merging lisp/org-bibtex.el CONFLICT (content): Merge conflict in
[Orgmode] Re: Org-mode release 7.01
Andreas Burtzlaff and...@gmx.net writes: Markus Heller helle...@gmail.com writes: Carsten Dominik carsten.domi...@gmail.com writes: [snip] Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. This might be a bit OT, I apoligize, but how exactly do I get the new release with git? I'm new to git, and I've tried the following: 1. Change the branch to maint 2. git pull git://repo.or.cz/org-mode.git maint That command tries to merge maint with the branch you're currently on - most likely main. If you do not have manual changes in your working tree you can run git reset --hard to undo that merge. I think what you want is: git pull git checkout -t origin/maint Andreas, thanks for the reply, worked as advertised. Cheers Markus ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
Hi Eric, Its great to hear that you're hoping to contribute new language support. I've just written some instructions for adding new languages to Babel, they should propagate to Worg [1] within the next hour or so. The most important part of these new instructions is an updated ob-template.el which is available in the Worg repo [2]. Let me know if/how this new documentation should be improved, or if you run into any issues along the way. Looking forward to seeing what you come up with! -- Eric Eric S Fraga ucec...@ucl.ac.uk writes: Carsten, as always, thanks for an incredible job! The announcement of this new release has motivated me to back up to speed with org-babel and the changes that have been done to simplify it. I had previously written interfaces for jython, ledger and maxima. These have not worked since the simplification work on org-babel started and I haven't had the time to do anything about it. I would now like to get these working again and hopefully contribute them to org. However, there does not appear to be any documentation on writing support for new languages. Before I delve into existing codes (which is what I did last time), I just want to confirm that this is indeed the case? Thanks again, eric Footnotes: [1] http://orgmode.org/worg/org-contrib/babel/language.php [2] http://repo.or.cz/w/Worg.git/blob/HEAD:/org-contrib/babel/ob-template.el ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode release 7.01
Markus Heller helle...@gmail.com writes: Andreas Burtzlaff and...@gmx.net writes: Markus Heller helle...@gmail.com writes: Carsten Dominik carsten.domi...@gmail.com writes: [snip] Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. This might be a bit OT, I apoligize, but how exactly do I get the new release with git? I'm new to git, and I've tried the following: 1. Change the branch to maint 2. git pull git://repo.or.cz/org-mode.git maint That command tries to merge maint with the branch you're currently on - most likely main. If you do not have manual changes in your working tree you can run git reset --hard to undo that merge. I think what you want is: git pull git checkout -t origin/maint Andreas, thanks for the reply, worked as advertised. Cheers Markus Great, but thinking about it again, it is not necessary to switch to the maint branch unless you want to stick to releases and not follow the bleeding edge of development. Andreas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode Andreas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode release 7.01
Andreas Burtzlaff and...@gmx.net writes: Markus Heller helle...@gmail.com writes: Andreas Burtzlaff and...@gmx.net writes: Markus Heller helle...@gmail.com writes: Carsten Dominik carsten.domi...@gmail.com writes: [snip] Thanks, thanks, thanks! Enjoy! - Carsten P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. This might be a bit OT, I apoligize, but how exactly do I get the new release with git? I'm new to git, and I've tried the following: 1. Change the branch to maint 2. git pull git://repo.or.cz/org-mode.git maint That command tries to merge maint with the branch you're currently on - most likely main. If you do not have manual changes in your working tree you can run git reset --hard to undo that merge. I think what you want is: git pull git checkout -t origin/maint Andreas, thanks for the reply, worked as advertised. Cheers Markus Great, but thinking about it again, it is not necessary to switch to the maint branch unless you want to stick to releases and not follow the bleeding edge of development. I assumed I had to switch to the maint branch in order to get the 7.01 release. How could I have done this while staying on the master branch? Thanks Markus ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Org-mode release 7.01
I assumed I had to switch to the maint branch in order to get the 7.01 release. How could I have done this while staying on the master branch? Basically, as long as you're on master, you'll always have the latest and greatest, which may or may not be what you want. At certain times, including in the past few days, 'master' is deemed release-worthy, and a stable release is produced. However, development goes on in the master branch. The maint branch was created so that small bugs in the latest release could be fixed and updated, without having to include whatever major developments might have happened on master in the mean time. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Org-mode release 7.01
On Jul 19, 2010, at 8:38 PM, Erik Iverson wrote: I assumed I had to switch to the maint branch in order to get the 7.01 release. How could I have done this while staying on the master branch? Basically, as long as you're on master, you'll always have the latest and greatest, which may or may not be what you want. At certain times, including in the past few days, 'master' is deemed release-worthy, and a stable release is produced. However, development goes on in the master branch. The maint branch was created so that small bugs in the latest release could be fixed and updated, without having to include whatever major developments might have happened on master in the mean time. The main reason for making releases at all are - to produce a fall-back if the current master does not work for you because it is buggy. This happen only rarely here and only for short times. - To give alternative distributions like the Debian package a point of reference, a signal that this state of Org is reasonably well tested and stable. Kind regards - Carsten ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Org-mode release 7.01
Erik Iverson er...@ccbr.umn.edu writes: I assumed I had to switch to the maint branch in order to get the 7.01 release. How could I have done this while staying on the master branch? Basically, as long as you're on master, you'll always have the latest and greatest, which may or may not be what you want. I am confused now. Carsten said is his announcement that master did NOT contain the 7.01 release: quote P.S. If you are trying to find the 7.01 release on the master branch in the repository, you will not. The releases are now on a new branch, called maint, which will contain only commits that are also releases. This will make it easier to make minor fixes to a release while development continues on the master branch. /quote At certain times, including in the past few days, 'master' is deemed release-worthy, and a stable release is produced. However, development goes on in the master branch. The maint branch was created so that small bugs in the latest release could be fixed and updated, without having to include whatever major developments might have happened on master in the mean time. Would this explanation be correct then: Right now, 7.01 is in the maint branch, for a few days/weeks or so, until the small nags have been resolved; the master branch is the last 6.36 release. Once the little bugs/issues have been resolved, 7.01 will be merged with the master branch, and everything will be back to (my) normal? Is this correct? Thanks Markus ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Re: Org-mode release 7.01
Markus Heller wrote: Erik Iverson er...@ccbr.umn.edu writes: I assumed I had to switch to the maint branch in order to get the 7.01 release. How could I have done this while staying on the master branch? Basically, as long as you're on master, you'll always have the latest and greatest, which may or may not be what you want. I am confused now. Carsten said is his announcement that master did NOT contain the 7.01 release: Okay, maybe these pictures will clarify: Org mode is developed in a branch called master. All new changes are done here so with A, B, C etc. representing changes to Org mode's source code the development looks like this: , | +---++---++---++---++---++---++---+ | [master] | A |---| B |---| C |---| D |---| E |---| F |---| G |--- | +---++---++---++---++---++---++---+ ` Now let's say at the source code being at patch B the stable version 7.01 is released. In this case we create a new branch called maint that starts at patch B: , | +---++---++---++---++---++---++---+ | [master] | A |---| B |---| C |---| D |---| E |---| F |---| G |--- ... | +---++---++---++---++---++---++---+ | : | : | +---+ | [maint] | B | | +---+ ` Currently release is on maint means that the branch [maint] represents the state of Org mode's sources at the time when the release 7.01 was made. Example: Org 7.01 was released after commit (change) a760c250a5585656567275c743cced6c4e652573. The branch [maint] currently contains the source code as it was right after this change.[1] The branch [master] was at this point in time in the same state but has already proceeded with fresh new patches. So, 7.01 is indeed /not/ on master, because master is where all new things go in and has already proceeded (patch C, D etc. in the picture). And [maint] will never be merged to [master], because all changes will be done in [master]. It's the other way round: If a bug is fixed in [master] that is known to be present in [maint], the fix will be first made in [master] and than in [maint]. So if E is a fix for a bug that is present before B (read: in [master] and [maint]), we apply the fix in [maint], too. , | +---++---++---++---++---++---++---+ | | A |---| B |---| C |---| D |---| E |---| F |---| G |--- ... | +---++---++---++---++---++---++---+ |: : |: v | +---+ +---+ | | B |--| E'|--- | +---+ +---+ ` If people use a stable version (e.g. Release 7.01) we can provide fixes for bugs in this version. More details on this topic especially for Git can be found in: The Git Community Book http://book.git-scm.com/ -or- Loeliger, Jon: Version Control with Git. O'Reilly 2009. (my favorite) HTH, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpLIbM58wIHQ.pgp Description: PGP signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: ms-exchange invitation -- org-mode appointment
Here is something similar for gnus http://ozymandias.dk/emacs/org-import-calendar.el It looks for text/calendar parts. It copies a small org formatted text snippet to the kill-ring. I then use org-remember for these mails and just do a yank after the org-remember call. -- Vagn Johansen ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Re: Behavior of Gnus when called from an hyperlink
Hi David, Tassilo and Nick, David Maus wrote: Tassilo Horn wrote: Please check, if that function is that slow for all message-ids or if that's only for some. The function has a FIXME: Should this try to use CHARSET? -- fx, and maybe this answer has to be answered with Yes! I think this is not very likely: With the CHARSET argument a client can inform the server that the search string is in a charset different than the default 7bit ASCII (Cf. rfc3501, 6.4.4). You could rule out the server being the culprit by performing the search manually: gnutls-cli --crlf --port 993 your.mail.host.here 0x1 LOGIN user password 0x2 SELECT Inbox.work 0x3 SEARCH HEADER Message-ID message id w/o angle brackets 0x4 LOGOUT Great idea to test that. I began with it (before going to edebug more functions): --8---cut here---start-8--- [...@mundaneum] /nc -vv mail imap Connection to mail 143 port [tcp/imap2] succeeded! * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE ACL ACL2=UNION STARTTLS XMAGICTRASH] Courier-IMAP ready. Copyright 1998-2004 Double Precision, Inc. See COPYING for distribution information. 0x1 LOGIN sva not-shown 0x1 OK LOGIN Ok. 0x2 SELECT INBOX.mc * FLAGS ($MDNSent Junk gnus-save gnus-forward NonJunk $Forwarded \Draft \Answered \Flagged \Deleted \Seen \Recent) * OK [PERMANENTFLAGS ($MDNSent Junk gnus-save gnus-forward NonJunk $Forwarded \* \Draft \Answered \Flagged \Deleted \Seen)] Limited * 27072 EXISTS * 0 RECENT * OK [UIDVALIDITY 1097250695] Ok * OK [MYRIGHTS acdilrsw] ACL 0x2 OK [READ-WRITE] Ok 0x3 SEARCH HEADER Message-ID 871vbrxzo6@mundaneum.com * SEARCH 26856 0x3 OK SEARCH done. 0x3 SEARCH HEADER Message-ID 871vbrxzo6@mundaneum.com * SEARCH 26856 0x3 OK SEARCH done. 0x4 LOGOUT * BYE Courier-IMAP server shutting down 0x4 OK LOGOUT completed [...@mundaneum] / --8---cut here---end---8--- Did twice the same request. Did take twice 5 mins... My main account uses Courier on Debian, too and search for a particular message id within ~7000 messages is quite fast. In my case, the culprit seems well to be our mail server, then. Couldn't find this information in the tread: Is it slow for a particular message or slow on Inbox.work in general? I answered this in the early beginning of the thread: time taken for opening the link seems to be (linearly?) dependant on the size of the mail groups. In INBOX.mc (the group for all work-related emails, containing ~27,000 emails), it takes ~5 mins to open a link from Org. In other normally-sized groups (a couple of 100's of emails), it took a couple of seconds ( 10 s). Maybe a problem is that I keep all of my emails (but the spams...) since the beginning: now, over 140,000 emails entered my INBOX -- only the spams left it. What would be your pieces of advice in such a case? Do I need to test something extra? Get a local imap server? Others (like asking for fixing the search on our Courier mail server)? Best regards, Seb -- Sébastien Vauban ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [PATCH] fix infinite loop in csv table import
Hi, I've just noticed that I get an infinite loop when importing csv tables into Org-mode tables. For example calling (org-table-convert-region (point-min) (point-max) '(4)) from inside of a simple text file containing the following --8---cut here---start-8--- 1,2,3 1 2 3 5 --8---cut here---end---8--- results in an infinite loop. The attached patch fixes this issue [1], however it seems weird that this would just surface now, given that the code in question has been in the repo since last fall , | commit 59c9c4cdd4ae974dfb92ab441462b3fee48ab5af | Author: Carsten Dominik carsten.domi...@gmail.com | Date: Mon Oct 26 12:31:16 2009 +0100 | | Correctly interpret CVS tables with quoted fields | | The csv parser was very primitive, ignoring quoted fields. This is | now fixed. ` Has anyone else noticed this problem? Should I go ahead and apply this patch? Best -- Eric Footnotes: [1] From 3c3f4ca9a34dca23051ca2f4e4518b416338d4f4 Mon Sep 17 00:00:00 2001 From: Eric Schulte schulte.e...@gmail.com Date: Mon, 19 Jul 2010 13:45:25 -0700 Subject: [PATCH] org-table: fix infinite loop in table importation * lisp/org-table.el (org-table-convert-region): don't continue csv importation which the point catches the end, this fixes an infinite loop which was caused by the (point) never catching up with the end marker --- lisp/org-table.el |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lisp/org-table.el b/lisp/org-table.el index a0311d9..6172e1c 100644 --- a/lisp/org-table.el +++ b/lisp/org-table.el @@ -453,7 +453,7 @@ nil When nil, the command tries to be smart and figure out the (t 1 (goto-char beg) (if (equal separator '(4)) - (while (= (point) end) + (while ( (point) end) ;; parse the csv stuff (cond ((looking-at ^) (insert | )) -- 1.7.0.4 ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [mobile-org] Recovering notes
Hey guys, I have a small situation with mobileorg. I removed the files from the WebDav repo by accident, but I had lots of notes taken into mobileorg (iPod touch). I tried to sync by accident and the notes are gone. This is not a life-or-death situation, but it would be nice if I could recover my notes somehow -- does mobileorg keep them in a cache somewhere (maybe I could access via ssh / jailbroken iPod). If it's not possible, maybe this could serve as a new feature suggestion, to at least keep backups of captured items (or all the items on the iPhone OS, for that matter). Thanks, Marcelo. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] question about date-tree
On Mon, 19 Jul 2010 08:10:49 -0400, Emin.shopper Martinian.shopper emin.shop...@gmail.com wrote: Dear Experts, I really like the date-tree feature of org-remember and use it to plan my daily agenda. Often I want to plan things in the future and fill out an entry for a couple of weeks hence. It's slightly annoying to try to remember the day of week and date so that it will match the date-tree format. Is there a function/utility/suggestion for prepopulating a month's worth of date-tree daily nodes? Thanks, -Emin ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode I know this doesn't actually answer your question but what I do is simply bring up the agenda view and then insert an entry in the right day using i d. This will create a date-tree entry if you've set the right variable, specifically org-agenda-diary-file to point to the date-tree file. However, I also would like org-capture to handle this situation... for instance, I would sometimes like todo entries that I define with org-capture to be placed in a date tree structure for either of the scheduled or deadline dates that todo entry is initially defined with. -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-Mode button
On Mon, 19 Jul 2010 14:57:33 +0200, Ulf Stegemann ulf-n...@zeitform.de wrote: Advocating Org-Mode is always a noble cause. In order to do so, I've put together a created with Org-Mode button which is displayed on my website. Although I'm far from being a designer type of guy, you may want to have a look at http://ulf.zeitform.de/images/org-mode.png. Of course you are very welcome to use that button yourself or come up with an improved version. Excellent! I like it and would like to use it for my web pages. Can we get it placed somewhere static, like maybe on Worg? -- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] bug: images always inlined when exporting to HTML
Having seen the recent message by Ulf regarding an org-mode button, I thought I would do a little bit of work on my web site. Unfortunately, this has caused me a problem! It would appear that the handling of images in HTML export has changed sometime recently and does not match the documentation (12.5.5 Images in HTML export). Specifically, whether a link to an image file has a description or not is ignored and all my images are being inlined. Attached are a simple org file that illustrates the problem and the resulting HTML. I think I'm up to date with org, although the version number I get is a bit strange: : Org-mode version 7.01trans (release_6.36.718.g78ef) : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) : of 2010-05-16 on raven, modified by Debian Any help greatly appreciated! Thanks, eric # -*- coding: utf-8; -*- #+TITLE: examplebug.org #+AUTHOR:Eric S Fraga #+EMAIL: e.fr...@ucl.ac.uk #+DATE: 2010.07.19 23:16:44 #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * problem with html export of links to images I often have links to images that should be inline: #+caption: An example image to be displayed on the page [[file:mip.png]] and images which are [[file:mip.png][linked to]] but not displayed. #+begin_src emacs-lisp :results output (format %s\n%s (org-version) (emacs-version)) #+end_src #+results: : Org-mode version 7.01trans (release_6.36.718.g78ef) : GNU Emacs 23.2.1 (i486-pc-linux-gnu, GTK+ Version 2.20.0) : of 2010-05-16 on raven, modified by Debian Title: examplebug.org examplebug.org Table of Contents 1 problem with html export of links to images 1 problem with html export of links to images I often have links to images that should be inline: An example image to be displayed on the page and images which are but not displayed. (format "%s\n%s" (org-version) (emacs-version)) Author: Eric S Fraga Date: 2010.07.19 23:16:44 HTML generated by org-mode 7.01trans in emacs 23 inline: mip.png-- Eric S Fraga GnuPG: 8F5C 279D 3907 E14A 5C29 570D C891 93D8 FFFC F67D ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [mobile-org] Recovering notes
Hi Marcelo, If you happened to plug in your device somewhat recently and a backup was made through iTunes, you may be able to dig through the backup and find the sqlite database MobileOrg uses. You might also be able to find a temp Org-file the app uses. Feel free to email me off-list and I can help you try to track that down if you choose to go that route. Hope this helps. I'll see if I can recreate this problem and issue a warning instead of losing notes. -Richard On Mon, Jul 19, 2010 at 5:04 PM, Marcelo de Moraes Serpa celose...@gmail.com wrote: Hey guys, I have a small situation with mobileorg. I removed the files from the WebDav repo by accident, but I had lots of notes taken into mobileorg (iPod touch). I tried to sync by accident and the notes are gone. This is not a life-or-death situation, but it would be nice if I could recover my notes somehow -- does mobileorg keep them in a cache somewhere (maybe I could access via ssh / jailbroken iPod). If it's not possible, maybe this could serve as a new feature suggestion, to at least keep backups of captured items (or all the items on the iPhone OS, for that matter). Thanks, Marcelo. ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Org-mode release 7.01
Carsten Dominik carsten.domi...@gmail.com writes: Hi everyone, I have just released version 7.01 of Org mode. This is a major release, and we have worked months on getting it together. Most important is of cause the complete integration of Org Babel into Org mode. Many thanks to Eric Schulte and Dan Davison who have worked tirelessly to make this happen. Thomas S. Dye gets credit here as well because he did a lot of work on documentation and function/variable docstrings. Wowwiieeeh! Great work Carsten! Thanks a lot everyone! Sebastian ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Development setup (was: Org-mode release 7.01)
Hi Carsten and John, Also, I need to shout out my gratitude to the increasing number of volunteers in the project. John Wiegley's patchwork server has done wonders for streamlining the process of reviewing and applying patches. I have applied dozens of patches though this process, just in the last week. The issue tracker by David Maus has finally brought some structure into the stream of ideas and reports on this mailing list, at a moment when I was about to falter under the amount of work maintaining this project means for me. Frankly, right now I don't know how I would do things without David's competent and efficient help - he has effectively and silently become co-maintainer of this project. The new technique drives me crazy. To me, it feels frustrating compared to the direct means of the good old times. Now, that the release is done, it's time to speak about the next decade of Org mode developing ;) A minute ago I got 5 mails like this one here: Subject: Patchwork: Patch 150 Accepted Body: Patch 145 (http://patchwork.newartisans.com/patch/145/) is now Accepted. This relates to the following submission: http://mid.gmane.org/%3C1279347713-29950-1-git-send-email-dmaus%40ictsoc.de%3E This current mechanism might help the maintainers as it's automated, but for me it's hard to follow. I often delete mails suggesting patches I don't apprehend. I then get those dangling Patchwork: ... messages. I simply don't want to gather all those mails from this high traffic list, just to now to which issue the accepted patches belong. I don't want to click the link(s) in those mails and wait for my browser to load either. Suggestions: 1.) Could the original mail (the one including the actual patch, even if modified) be attached to the autogenerated email, please? This should be at the very bottom of the mail, because of length and priority. 2.) And how about the subject? The OP's subject is what I read on the patchwork server. Why can't that be (part of) the subject of the Accepted message? E.g.: [Orgmode] [ACCEPTED] org-capture with LISP function template Maybe something that works on gmane et al, too. 3.) If there are annotations to the patch, would it be possible to include that comment in that automated message? I don't now how the patch is switched to accepted on the patchwork server. But a simple textarea field and appropriate POST variable would do, wouldn't it? This is all information available on the patchwork server. So I hope it's just changing a few lines of code? I sometimes receive mails from bugzilla servers, concerning bug reports I wrote years ago. I never had that problem to understand what those mails were trying to tell me. Thanks for considering this. Best wishes Sebastian ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] org capture: use org-default-notes-file
Using the latest and greatest 7.01... Is it possible to use the variable org-default-notes-file in the org capture settings? I have a lot of org capture templates and I would rather set the file in one location then have to set it for each template. I would think it is possible with the org-default-notes-file, but no matter how I try to use it in the template it doesn't work. I get errors such as expecting stringp. See below. I would like to do something similar to the todo entry and not the note entry where I need to explicitly specify the file. Thanks for any help. Stephen ;;; Org Capture (setq org-default-notes-file (concat org-directory /refile.org)) (define-key global-map (kbd C-c c) 'org-capture) (setq org-capture-templates '((t todo entry (file+headline org-default-notes-file ToDo) * TODO %?\n %U\n ) (n note entry (file+headline /Users/stephen/Dropbox/org/refile.org Notes) * %?\n %U\n ) )) ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] [babel] html export of R data frame
I have an R script which outputs a small table in the form of a dataframe. In org-babel, this dataframe is not displayed as an org table but simply as text laid out as it would be in an R session. When I export the output to html, I do not get an html table but only text. How do I make org-babel show a table instead of plain text? For example, take a simple code block like: #+BEGIN_SRC R :results output :exports both :session y x-c(1:5) y-x^2 data.frame(x,y) #+END_SRC Vikas ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Development setup (was: Org-mode release 7.01)
Suggestions: 1.) Could the original mail (the one including the actual patch, even if modified) be attached to the autogenerated email, please? This should be at the very bottom of the mail, because of length and priority. 2.) And how about the subject? The OP's subject is what I read on the patchwork server. Why can't that be (part of) the subject of the Accepted message? E.g.: [Orgmode] [ACCEPTED] org-capture with LISP function template Maybe something that works on gmane et al, too. 3.) If there are annotations to the patch, would it be possible to include that comment in that automated message? I don't now how the patch is switched to accepted on the patchwork server. But a simple textarea field and appropriate POST variable would do, wouldn't it? 4) If traffic warrants it and as more users join this list generating more posts... perhaps a new list called emacs-orgmode-dev for development related work? ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [babel] html export of R data frame
On Jul 19, 2010, at 4:27 PM, Vikas Rawal wrote: I have an R script which outputs a small table in the form of a dataframe. In org-babel, this dataframe is not displayed as an org table but simply as text laid out as it would be in an R session. When I export the output to html, I do not get an html table but only text. How do I make org-babel show a table instead of plain text? For example, take a simple code block like: #+BEGIN_SRC R :results output :exports both :session y x-c(1:5) y-x^2 data.frame(x,y) #+END_SRC Vikas Aloha Vikas, Is this what you want? #+BEGIN_SRC R :results value :exports both x-c(1:5) y-x^2 data.frame(x,y) #+END_SRC #+results: | 1 | 1 | | 2 | 4 | | 3 | 9 | | 4 | 16 | | 5 | 25 | hth, Tom Thomas S. Dye, Ph.D. T. S. Dye Colleagues, Archaeologists, Inc. Phone: (808) 529-0866 Fax: (808) 529-0884 http://www.tsdye.com ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] [PATCH] fix infinite loop in csv table import
Eric Schulte wrote: Hi, I've just noticed that I get an infinite loop when importing csv tables into Org-mode tables. For example calling (org-table-convert-region (point-min) (point-max) '(4)) from inside of a simple text file containing the following --8---cut here---start-8--- 1,2,3 1 2 3 5 --8---cut here---end---8--- results in an infinite loop. The attached patch fixes this issue [1], however it seems weird that this would just surface now, given that the code in question has been in the repo since last fall This patch looks good to me: If the end of the region happens to be end-of-buffer point will never be greater than end and the loop loops forever. Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de pgpWGvKwCRbru.pgp Description: PGP signature ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
