Re: [O] Bug: Org-mode suppress newlines between headlines when sorting footnotes with folded buffer view [7.8.03]
Hello, oitofe...@gmail.com (Bruno Félix Rezende Ribeiro) writes: Consider the following org code: -- * Headline 1 This is only a text.[fn:1] [fn:1] This is a footnote. * Headline 2 This is another text.[fn:2] [fn:2] This is another footnote. -- Now consider the folded buffer view of that code: -- * Headline 1... * Headline 2... -- If you type 'C-u C-c C-x f s', to sort footnotes, buffer become like this: -- * Headline 1...Headline 2... -- If you save and revert the buffer or type S-TAB to get OVERVIEW cycling state all is okay again. If you don't fold headlines before sorting, everything goes fine too. Nevertheless, it's still very annoying. This should be fixed on master branch. Note: I haven't made it a hotfix since I am not certain it will not have any side effect. Thanks for your report. Regards, -- Nicolas Goaziou
[O] [PATCH] Fix broken links in worg (org-contrib/index.org)
Hello worgers,
I've noticed that all links to raw files (.el) on
http://orgmode.org/worg/org-contrib/index.html are broken. They used
to be pointers to repo.or.cz. The attached patch reactivates these
links with pointers to the new orgmode.org git repository.
This is my first patch (not to worg, but ever), and I'm still learning
how to use git and so on, so please tell me how I could make better
patches in the future.
BTW, org-contrib/index.org needs an update on a few additional
points:
- A few new contributions in contrib/lisp are not listed here.
- A few contributions passed into the core of org. This should be
commented, together with link to the relevant sections in the
documentation (org.texi), etc.
- A lost last version of org-refer-by-numbers.el
- A decision to take with links to raw-files that were removed from
the org-mode git repository: either link them to legacy raw file
from org-mode git, or remove these links
- and a few other tiny things...
I would happily take care of that, or help anyone in doing it. I
welcome any advice on that.
Thanks for all your job in org and worg,
A happy Org user,
François.
From 8979cc24cefea89d227d13a27f4dfbf7e8f42dec Mon Sep 17 00:00:00 2001
From: François Allisson franc...@allisson.co
Date: Sun, 8 Apr 2012 11:56:29 +0200
Subject: [PATCH] Fix broken links on worg/org-contrib/index.org
* worg/org-contrib/index.org: Added a repofile link definition with
pointer to the orgmode.org git repository, because most links to raw
(.el) files depended on that missing definition.
* worg/org-contrib/index.org: Fixed two additional links.
---
org-contrib/index.org |5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/org-contrib/index.org b/org-contrib/index.org
index e8e5467..35aa013 100644
--- a/org-contrib/index.org
+++ b/org-contrib/index.org
@@ -7,6 +7,7 @@
#+EMAIL: bzg AT altern DOT org
#+LANGUAGE: en
#+CATEGORY: worg
+#+LINK: repofile http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=%s;hb=HEAD
[[file:../index.org][{Back to Worg's index}]]
@@ -166,7 +167,7 @@ hopefully have some documentation.
Written by /Reimar Finken/.
[[repofile:contrib/lisp/org-git-link.el][Link to raw file]].
-- [[http://julien.danjou.info/google-weather-el.html][org-google-weather.el -- weather forecast in the agenda buffer]] ::
+- [[http://julien.danjou.info/software/google-weather.el][org-google-weather.el -- weather forecast in the agenda buffer]] ::
Allow %%(org-google-weather New York) sexps for displaying weather
forecast in the agenda buffer.
Written by /Julien Danjou/.
@@ -215,7 +216,7 @@ hopefully have some documentation.
This approximates a WYSiWYG HTML mail editor from within Emacs, and
can be useful for sending tables, fontified source code, and inline
images in email. Written by /Eric Schulte/.
- [[repofile:lisp/org-mime.el][Link to raw file]].
+ [[repofile:contrib/lisp/org-mime.el][Link to raw file]].
- /org-mtags.el/ -- support for some Muse-like tags in Org-mode ::
This package allows you to write =example= and =src= and other
--
1.7.5.4
[O] Usage of disqus instead of mailinglist considered harmful (was: Disqus commenting system tested on Worg)
* John Hendy jw.he...@gmail.com wrote: On Apr 7, 2012 4:28 AM, Bastien b...@gnu.org wrote: The question now is: on what Worg pages should we have this comment system? True. And how to balance the mailing list vs disqus... While thw mailing list is great, sometimes for the life of me I can't find a discussion I know exists. If it were attached to a Worg page it would just be there instead of having to remember the specific syntax to google. Oh I'd like to warn here: disqus is a private commercial company that wants to make money. Their strategy can (and will) change from one day to the other. They can not guarantee that the API, focus of service, long-time-data-preservation, ... does not change. Mailinglists - though currently handled by gmane which is also a company - are a standard that is independent from any company. You can extract the complete archive if you want and host it somewhere else. No fuzz here. Disqus offers export to XML (AFAIR) but where could you import it as an alternative hosting service? I consider services as *disqus better than no discussion at all* but it is *nonpermanent* information. It can disappear from one day to the other[1]. I do like to see disqus comments on Worg-pages to give non-Worgers the possibility to interact with the Worg-community. But remember: any information (only) posted to disqus is lost in the long run. I'd like to bet on that. BTDT. :-) Therefore: Any *important* information contained in disqus comments have to be written to the Worg-pages (or the Mailinglist) as well. I beg you not to shift discussions from ML to disqus and to continue posting to the mailinglist. Since ML is a well structured and well backup-able communication channel that is way better future-proof than the neat features of disqus. Imagine there would not be any Org-mode ML-archive[2] at all ... Besides that: I personally prefer using mailinglists with my news reader than with my email client. With gmane I do have the choice. With disqus, I do have to use a web frontend I do not like. Things like following threads, scoring for people or topics, filtering, composing (in Emacs or vim), is *much* better outside of Web forums or services like disqus. Or should disqus comments be more like wiki discussions? Only for commenting on the page itself. Definitely neat; as you said, we'll have to see how it evolves! 1. Who can obviate shutdown and/or bankruptcy of disqus.com? 2. http://news.gmane.org/gmane.emacs.orgmode -- Karl Voit
Re: [O] Usage of disqus instead of mailinglist considered harmful
Am 08.04.2012 13:43, schrieb Karl Voit: Mailinglists - though currently handled by gmane which is also a company - are a standard that is independent from any company. You can extract the complete archive if you want and host it somewhere else. No fuzz here. Gmane is not a company: http://gmane.org/about.php Besides, the mailing list isn't run in any way by Gmane. -- Achim. (on the road :-)
[O] [PATCH] org.texi: Fix missing links and formatting in 'Exporting' section
From 40344d3dd27af520ba09516b72e6cbb06a37e780 Mon Sep 17 00:00:00 2001
From: Julian Gehring julian.gehr...@googlemail.com
Date: Sun, 8 Apr 2012 15:24:47 +0200
Subject: [PATCH] org.texi: Fix missing links and formatting in 'Exporting'
section
---
doc/org.texi | 25 -
1 file changed, 12 insertions(+), 13 deletions(-)
diff --git a/doc/org.texi b/doc/org.texi
index b16adf8..5e51843 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -9565,12 +9565,12 @@ the web, while the XOXO format provides a solid base for exchange with a
broad range of other applications. @LaTeX{} export lets you use Org mode and
its structured editing functions to easily create @LaTeX{} files. DocBook
export makes it possible to convert Org files to many other formats using
-DocBook tools. OpenDocument Text(ODT) export allows seamless
+DocBook tools. OpenDocument Text (ODT) export allows seamless
collaboration across organizational boundaries. For project management you
can create gantt and resource charts by using TaskJuggler export. To
incorporate entries with associated times like deadlines or appointments into
a desktop calendar program like iCal, Org mode can also produce extracts in
-the iCalendar format. Currently Org mode only supports export, not import of
+the iCalendar format. Currently, Org mode only supports export, not import of
these different formats.
Org supports export of selected regions when @code{transient-mark-mode} is
@@ -10906,10 +10906,10 @@ one format (say @samp{csv}) to another format (say @samp{ods} or @samp{xls}).
If you have a working installation of LibreOffice, a document converter is
pre-configured for you and you can use it right away. If you would like to
use @file{unoconv} as your preferred converter, customize the variable
-@code{org-export-odt-convert-process} to point to @code{unoconv}. If you
-would like to use a converter of your own choosing or tweak the default
-settings of the default @file{LibreOffice} and @samp{unoconv} converters
-@xref{Configuring a document converter}.
+@code{org-export-odt-convert-process} to point to @code{unoconv}. You can also
+use a converter of your own choice or tweak the default settings of the default
+@file{LibreOffice} and @samp{unoconv} converters
+(@xref{Configuring a document converter}).
@subsubsection Automatically exporting to other formats
@anchor{x-export-to-other-formats}
@@ -11243,7 +11243,7 @@ that the @file{dvipng} program be available on your system.
For various reasons, you may find embedding @LaTeX{} math snippets in an
ODT document less than reliable. In that case, you can embed a
-math equation by linking to its MathML(@file{.mml}) source or its
+math equation by linking to its MathML (@file{.mml}) source or its
OpenDocument formula (@file{.odf}) file as shown below:
@example
@@ -11306,7 +11306,7 @@ Illustration 2: Bell curve
Export of literal examples (@pxref{Literal examples}) with full fontification
is supported. Internally, the exporter relies on @file{htmlfontify.el} to
generate all style definitions needed for a fancy listing.@footnote{Your
-@file{htmlfontify.el} library must atleast be at Emacs 24.1 levels for
+@file{htmlfontify.el} library must at least be at Emacs 24.1 levels for
fontification to be turned on.} The auto-generated styles have @samp{OrgSrc}
as prefix and inherit their color from the faces used by Emacs
@code{font-lock} library for the source language.
@@ -11355,10 +11355,9 @@ the variable @code{org-export-odt-convert-processes}. Also specify how the
converter can be invoked via command-line to effect the conversion.
@item Configure its capabilities
-@vindex org-export-odt-convert-capabilities
+@vindex org-export-odt-convert-capabilities
@anchor{x-odt-converter-capabilities}
-
Specify the set of formats the converter can handle by customizing the
variable @code{org-export-odt-convert-capabilities}. Use the default value
for this variable as a guide for configuring your converter. As suggested by
@@ -11497,7 +11496,7 @@ regular text.
@end example
@strong{Hint:} To see the above example in action, edit your
-@file{styles.xml}(@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
+@file{styles.xml} (@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
custom @samp{Highlight} style as shown below.
@example
@@ -11516,7 +11515,7 @@ directive. For example, to force a page break do the following:
@end example
@strong{Hint:} To see the above example in action, edit your
-@file{styles.xml}(@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
+@file{styles.xml} (@pxref{x-orgodtstyles-xml,,Factory styles}) and add a
custom @samp{PageBreak} style as shown below.
@example
@@ -11588,7 +11587,7 @@ two table styles with the names @samp{TableWithHeaderRowAndColumn} and
@samp{TableWithFirstRowandLastRow}. (@strong{Important:} The OpenDocument
styles needed for producing the above template have been pre-defined for you.
These styles
Re: [O] TODO agenda filtering on priority?
At Sat, 7 Apr 2012 21:22:59 +0200, Michael Brand wrote: On Sat, Apr 7, 2012 at 17:59, James Harkins jamshar...@gmail.com wrote: How to make a TODO agenda search that will show only #A priority items? (Or #B or #C?) I see in the manual how to search on tags or properties, but not priorities. The manual has an example for matching PRIORITY, linked from several other manual pages about searches, here: http://orgmode.org/manual/Matching-tags-and-properties.html And my solution, for now: just a separate block for priority A. Priority B and C, I guess, don't really need to be in separate blocks. '(org-agenda-custom-commands (quote ( (0 Block TODO ( (tags-todo PRIORITY=\A\ ( (org-agenda-overriding-header TOP PRIORITY) (org-agenda-sorting-strategy (quote (user-defined-up))) )) (tags-todo -PRIORITY=\A\ ( (org-agenda-overriding-header Others) (org-agenda-sorting-strategy (quote (priority-down user-defined-up))) )) ) nil nil) ) )) Thanks for the tips! James -- James Harkins /// dewdrop world jamshar...@dewdrop-world.net http://www.dewdrop-world.net Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal. -- Whitman blog: http://www.dewdrop-world.net/words audio clips: http://www.dewdrop-world.net/audio more audio: http://soundcloud.com/dewdrop_world/tracks
Re: [O] [PATCH] org.texi: Fix missing links and formatting in 'Exporting' section
Julian Gehring julian.gehr...@googlemail.com writes:
From 40344d3dd27af520ba09516b72e6cbb06a37e780 Mon Sep 17 00:00:00 2001
From: Julian Gehring julian.gehr...@googlemail.com
Date: Sun, 8 Apr 2012 15:24:47 +0200
Subject: [PATCH] org.texi: Fix missing links and formatting in 'Exporting'
section
Hi Julian,
Why is the last hunk in this patch useful? Doesn't it just add a
trailing blank?
@@ -11588,7 +11587,7 @@ two table styles with the names
@samp{TableWithHeaderRowAndColumn} and
@samp{TableWithFirstRowandLastRow}. (@strong{Important:} The OpenDocument
styles needed for producing the above template have been pre-defined for you.
These styles are available under the section marked @samp{Custom Table
-Template} in @file{OrgOdtContentTemplate.xml}
+Template} in @file{OrgOdtContentTemplate.xml}
(@pxref{x-orgodtcontenttemplate-xml,,Factory styles}). If you need
additional templates you have to define these styles yourselves.
I think this hunk should probably be dropped.
Bernt
Re: [O] [PATCH] Fix broken links in worg (org-contrib/index.org)
François Allisson franc...@allisson.co writes: Hello worgers, I've noticed that all links to raw files (.el) on http://orgmode.org/worg/org-contrib/index.html are broken. They used to be pointers to repo.or.cz. The attached patch reactivates these links with pointers to the new orgmode.org git repository. This is my first patch (not to worg, but ever), and I'm still learning how to use git and so on, so please tell me how I could make better patches in the future. Hi François, This patch looks great to me (although I didn't test it). For worg patches you can request commit access directly and just apply the patch yourself. I don't think we need changelog entries for worg patches (only for org-mode source). Please correct me if that's wrong. Regards, Bernt
Re: [O] ledger file in org mode hangs during code block eval
On 08/04/12 05:06, Alexandros Bantis wrote: Hello all, Hoping someone might be help me diagnose this problem. I recently changed my linux distro from ubuntu to arch linux. I had an org-file that was running very well (over a year) up until the switch over. I have monthly entries separated into separate src ledger code blocks. When I do C-c C-c on a code block, it updates the results just fine. But when I try to update a report, it hangs for about 15 seconds and I get the following message: executing Ledger code block... executing Ledger source code block ledger -f /tmp/babel-13899vK/ledger-1389JnV -c -d Tl=3 bal Error: Please specify ledger file using -f or LEDGER_FILE environment variable. Code block evaluation complete. The code block that is being evaluated is only 127 lines in length. emacs version: GNU Emacs 23.4.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.9) of 2012-02-01 on shirley.hoetzel.inf org-version: Org-mode version 7.8.08 $ ledger -version Ledger 2.6.3, the command-line accounting tool The file that I'm using is an org-mode file encrypted with ccrypt, but when I create a duplicate unencrypted file, I get the same exact results. Thus, the problem doesn't seem to be related to ccrypt. When I paste the code block to a separate text file and run the command that was output from the *Messages* buffer. Thus, the problem doesn't seem to be related to ledger. Here's the relevant output from my installation log (pacman.log): [2012-04-06 18:38] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.6kK/emacs-org-mode-7.8.08-1-any.pkg.tar.xz' [2012-04-06 18:38] To enable this version of org-mode instead of the one shipped with emacs, [2012-04-06 18:38] add the line: [2012-04-06 18:38] (require 'org-install) [2012-04-06 18:38] to your .emacs file. [2012-04-06 18:38] [2012-04-06 18:38] NOTE: info documentation for emacs-org-mode goes now as 'orgmode' in /usr/share/info, [2012-04-06 18:38] It does NOT replace the 'org' info files shipped with emacs: [2012-04-06 18:38] $ info orgmode ## this version [2012-04-06 18:38] $ info org ## emacs' org version (currently 6.21) [2012-04-06 18:38] installed emacs-org-mode (7.8.08-1) $ whereis emacs emacs: /usr/bin/emacs /usr/lib/emacs /usr/share/emacs /usr/share/man/man1/emacs.1.gz relevant part from my .emacs file: ;; with a new installation (setq load-path (cons /usr/share/emacs/site-lisp load-path)) (require 'org-install) Have you got: (org-babel-do-load-languages 'org-babel-load-languages '((R . t) (ditaa . t) (dot . t) (emacs-lisp . t) (gnuplot . t) (haskell . nil) (latex . t) (ledger . t) (ocaml . nil) (octave . t) (python . t) (ruby . t) (screen . nil) (sh . t) (sql . nil) (sqlite . t))) somewhere in your .emacs. FWIW Ledger and Babel work fine on Arch here. Ian.
Re: [O] Usage of disqus instead of mailinglist considered harmful (was: Disqus commenting system tested on Worg)
On 8 Apr 2012 13:44, Karl Voit snip Oh I'd like to warn here: disqus is a private commercial company that wants to make money. Their strategy can (and will) change from one day to the other. An enthusiastic +1 from this largely lurking list member. Best, Brian vdB
Re: [O] ledger file in org mode hangs during code block eval
Have you got: (org-babel-do-load-languages 'org-babel-load-languages '((R . t) (ditaa . t) (dot . t) (emacs-lisp . t) (gnuplot . t) (haskell . nil) (latex . t) (ledger . t) (ocaml . nil) (octave . t) (python . t) (ruby . t) (screen . nil) (sh . t) (sql . nil) (sqlite . t))) somewhere in your .emacs. FWIW Ledger and Babel work fine on Arch here. Ian. Yes. This morning I reverted to version 7.7 and the problem went away.
Re: [O] layout org-babel menu WAS: About org-babel menu
Eric Schulte eric.schu...@gmx.com writes: Torsten Wagner torsten.wag...@gmail.com writes: Hi, for me the biggest trouble with babel is to remember the possible keywords in the header for different languages. There were a lot of ongoing syntax change which did not make it easier for me to remember all this. Thus a menu which is organised by languages offering all possible settings for each language would be very helpful. | Python || | export - code - result - both - none || | tangle - no - yes- filename | | | result - value - output | | | ... | ... Not sure how effectual this would be in a main menu. It would be definitely awesome in a context menu That would be (copied from worg) [*] indicates cursor position #+NAME: factorial #+BEGIN_SRC haskell [*] :results silent :exports code :var n=0 a context menu would appear presenting all possible header arguments for haskell #+NAME: factorial #+BEGIN_SRC haskell :results [*] :exports code :var n=0 a context menu presenting all possible values for the header argument :results in haskell I guess that together with the possibility to call this menu by keyboard strokes or alternatively show the same infos in the minibuffer would be a great win for babel and it would make many questions here on the list unnecessary. Furthermore, any change or extension in the syntax for a certain language would be directly reflected to the end-user. E.g., If I suddenly see the menu entry :exports 3dprint, I would be curious and check it out on worg and the manual ;) Totti Hi, I've put together a first pass at such support for interactive header argument look up. Please evaluate this elisp code [1] in your *scratch* buffer, then in an Org-mode buffer insert a code block like the following with the point at [*], and press tab. #+begin_src R :[*] :foo #+end_src You should see an auto-completion list showing which header arguments are available and (for those with known arguments) which arguments may be specified. This includes language specific header arguments, i.e., the R code block above suggests about twice as many possible header arguments as an elisp block. Note this expand on tab after : behavior is active on #+headers: lines as well. This makes use of the `org-babel-common-header-args-w-values' variable which holds header argument names and completions, as well as the org-babel-header-arg-names:lang variables. Does this seem like a good interface? Is it missing any important functionality? Best, Footnotes: [1] ;; Add support for completing-read insertion of header arguments after : (defun org-babel-header-arg-expand () Call `org-babel-enter-header-arg-w-completion' in appropriate contexts. (when (and (= (char-before) ?\:) (org-babel-where-is-src-block-head)) (org-babel-enter-header-arg-w-completion (match-string 2 (defun org-babel-enter-header-arg-w-completion (optional lang) Insert header argument appropriate for LANG with completion. (let* ((lang-headers-var (intern (concat org-babel-header-arg-names: lang))) (lang-headers (when (boundp lang-headers-var) (mapcar #'symbol-name (eval lang-headers-var (headers (append (mapcar #'symbol-name org-babel-header-arg-names) lang-headers)) (header (org-completing-read Header Arg: headers)) (args (cdr (assoc (intern header) org-babel-common-header-args-w-values))) (arg (when (and args (listp args)) (org-completing-read (format %s: header) (mapcar #'symbol-name (car args)) (insert (concat header (or arg ))) (cons header arg))) (add-hook 'org-tab-first-hook 'org-babel-header-arg-expand) Hi Eric, This is potentially much nicer than a function template. I tried filling out an R source code block's header arguments, but I couldn't find a way to get :results output graphics, which I use frequently for ggplot2 graphics. With TAB I could see type arguments, but not collection or handling arguments. Is there some way to cycle through the various completion lists? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Usage of disqus instead of mailinglist considered harmful
Hi all, there is no plan for changing the role and usage of the mailing list. This role and usage are in *our* hands. The idea behind a lightweight commenting system is not to split discussion areas, but to gather non-permanent feedback, to help spot small typos, etc. If worgers think comments should not be an a page, let's simply unplug disqus on that page. If some Worger wants comments on his page, I think it's better for him to use a centralized system. If zero useful comment comes out during the next few months, let's just remove this. Best, -- Bastien
Re: [O] Usage of disqus instead of mailinglist considered harmful
Achim Gratz strom...@nexgo.de writes: Am 08.04.2012 13:43, schrieb Karl Voit: Mailinglists - though currently handled by gmane which is also a company - are a standard that is independent from any company. You can extract the complete archive if you want and host it somewhere else. No fuzz here. Gmane is not a company: http://gmane.org/about.php Besides, the mailing list isn't run in any way by Gmane. Exactly. The mailing list is run by the GNU project and hosted on the GNU servers. We owe a lot to GNU. And we owe a lot to Lars for services like Gmane and Gwene. -- Bastien
Re: [O] idea, bug report template
Hi Bhastien, ;) thanks for the pointer. Indeed this does much of the idea I had already. A few points which might be add * If called with a region marked, this region could be put into the mail. That is mark the defect region and call `org-submit-bug-report' and you are almost done with your report. * As for the privacy concern. The org-mode settings could be saved to an extra file and attached as a zipped attachment. It would be still rather easy for devs to see it but it would not be exposed on the mailing list archives for any kind of data crawler. E.g. some might have email-addresses saved and hence they might receive a lot of spam if this addresses are exposed on the web. * The text could include a first responder guide to help people to send in clean and good bug-reports. It could include to ask people to start emacs without personal config-files, to make sure the bug is not actually a misconfiguration. A bunch of questions to fill in. E.g., * Abstract of the bug report (3-5 sentence) * Please select from the keywords below the ones which fits your problems best * Description ** What did you try yo do? ** What did you expect to happen? ** What happen? * Did the problem appear for the first time resp. did it work previously? * Is the problem still reproducible after starting emacs with emacs -q (do not load init files)? * Please copy here a minimal example which demonstrate the problem. Try to reduce it to the real problem. * Please attach here any error log you might received * Writing down this list makes me wonder if the bug-report buffer shouldn't be a org-buffer itself so people could test there minimal example within that buffer and the bug report could be split into two parts org-create-bug-report and org-submit-bug-report (create a mail with the bug report org-buffer as content). The last could call the first hook if no bug-report buffer is present. Torsten On 6 April 2012 20:40, Bastien b...@gnu.org wrote: Hi Thorsten, check `org-submit-bug-report'. We can certainly improve this and make it more structured/interactive. Thanks, -- Bastien
