[O] TexInfo conversion of Org syntax (Success!)
TexInfo conversion of Org syntax (Success!) The info file looks good. But, I feel some stylistic aspects can be improved. Eval this form (info /home/kjambunathan/src/worg/dev/org-syntax.info nil) Or try C-u M-x info RET org-syntax.info RET
Re: [O] [PATCH] * lisp/ob-core.el (org-babel-execute-src-block): insert hash for silent results
Eric Schulte writes: A hash marks a *result* with an indication of what was used to generate it (code block parameters). The point of a hash is to allow the result to be returned without having to re-execute. For this reason, I think that the hash should live with the result. Here Babel is assuming a very specific execution model, namely a functional one (a function with the same parameters always delivers the same results, so if you see the same function invoked with the same parameters you can just substitute the result from an earlier invocation). Babel isn't a functional language however, so it is both possible and done in practice to use it for side-effects or even side-effects only. But back to my earlier remark about the hash value actually being a signature of the source block and not the result. If I use noweb references, the reference text is cached, not its expansion. See the example below where after the first invocation I change the source block referenced to deliver a different result. That invalidates the cache for direct invocation of that block, but fails to do so for the indirect invocation. If you look at the two result blocks, you see that the same hash is added to two different blocks. --8---cut here---start-8--- #+name: list #+header: :exports none :results yes :eval query :cache yes #+begin_src emacs-lisp '(a b c d) #+end_src #+RESULTS[6bd0507c2cc972cc7647a9c2c169a1095bab5941]: list | a | b | c | d | #+RESULTS[d8dad02c5c6fd93a991a4bb23471f273cc0b3415]: list-1 | a | b | c | #+name: indirect #+header: :noweb yes #+header: :exports none :results yes :eval query :cache yes #+begin_src emacs-lisp list #+end_src #+RESULTS[0b6ada101242e80d4d50f4909f33d8819a88ea4e]: indirect | a | b | c | d | #+RESULTS[0b6ada101242e80d4d50f4909f33d8819a88ea4e]: indirect-1 | a | b | c | --8---cut here---end---8--- I'm not saying this needs fixing (expanding references could easily be the most costly step in a re-evaluation), but the description in the manual talks about caching in terms of results which is not what is actually implemented, as demonstrated above. In general a hash without a result doesn't make sense (because then what is cached?). If the question was meant as did this code block already run? and the invocation was for side-effects only, then it does make sense to me. If one did want to move hashes to code blocks it would be a major refactoring which would (in my opinion) require significant justification. I'm not disputing that it requires significant effort. The benefits would be that we might have a chance to clear up some confusion over the code execution model of Babel and better support different ones. As I understand this particular case, the OP is using a hash not to mark a result as up to date, but rather to mark a side effect (loading data into R) as having taken place. I think this is a misuse of a cache. Or you might call it a clever hack. But I think the general problem of needing one-time invocations of source blocks is one that comes up often when programming with side-effects that are not directly observable. This again comes in different shades, I'd often want to run some blocks only when the document is first opened, but then only again if something changes. This would require that the hash value was a property of the buffer text, not actual buffer text, I'd think. Sure, you can use hooks to nuke the caches on load, but that only works when you are using your own Emacs configuration. What if the R process restarts? The hash would still be valid, but the side effects have been lost. I think a better approach would be to implement the logic in R required to check if data is present and conditionally load it if not. Then simply re-run this conditional reloading code in full every time. Oh yes, there's a whole set of _other_ problems that are waiting to be solved. :-) Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for KORG EX-800 and Poly-800MkII V0.9: http://Synth.Stromeko.net/Downloads.html#KorgSDada
Re: [O] two-way sync org agenda/ical
* Marvin Doyley marvin...@gmail.com wrote: Hi there, Hi! Does anybody know how to export deadline or schedule items from org to ical ? I think you want to read following pages: http://orgmode.org/manual/iCalendar-export.html http://orgmode.org/worg/org-tutorials/org-google-sync.html -- Karl Voit
Re: [O] S-M-right problem in orgstruct-mode
Christopher Schmidt writes: Alan Schmitt alan.schm...@polytechnique.org writes: Looking at it there seems to be occurrences of '++' that are a bit strange. Was it garbled when attached? Ooops, I forgot to finalise my merge. It's looking good, thanks. One small nitpick: when a key is disabled, the message is orgstruct-error: This key has no function outside structure elements even though the cursor is on a structure element. Maybe a more information this function is disabled would work (if it's possible). But as I said, it's a nitpick. Thanks again, Alan
Re: [O] Editing folded headlines and ellipses
Hi Suvayu, Suvayu Ali fatkasuvayu+li...@gmail.com writes: I remember someone (maybe Bastien) putting in a safeguard quite sometime back that would unfold a headline with a warning when you tried to edit near the ellipses. This was to protect against accidental edits. I see this not there anymore, can we have it back? You mean `org-catch-invisible-edits'? It's still here... HTH, -- Bastien
Re: [O] [new exporter] [html] Tables of Contents
Hi Samuel, Samuel Wales samolog...@gmail.com writes: How do we make it a reality NOW? No, I stated my reasons here: http://article.gmane.org/gmane.emacs.orgmode/67829 -- Bastien
Re: [O] Fixing footnote HTML
Jambunathan K kjambunat...@gmail.com writes: I asked him to remove ox-html.el and he indicated how he wanted to proceed ahead. He wants ox-html.el in the tree and not GNU ELPA. Just to prevent confusion: I never said anything like this. ox-html.el is in the master branch of Org's repository, it will be in GNU ELPA (and Emacs) when we release 8.0. -- Bastien
Re: [O] S-M-right problem in orgstruct-mode
Hi Alan and Christopher, Alan Schmitt alan.schm...@polytechnique.org writes: even though the cursor is on a structure element. Maybe a more information this function is disabled would work (if it's possible). But as I said, it's a nitpick. I agree with Alan, let's update the user-error to something more informative -- Christopher, thanks a lot for the patch! Feel free to commit and push when you want. Best, -- Bastien
Re: [O] Editing folded headlines and ellipses
Hi Bastien, On Sun, Mar 10, 2013 at 10:34:26AM +0100, Bastien wrote: Suvayu Ali fatkasuvayu+li...@gmail.com writes: I remember someone (maybe Bastien) putting in a safeguard quite sometime back that would unfold a headline with a warning when you tried to edit near the ellipses. This was to protect against accidental edits. I see this not there anymore, can we have it back? You mean `org-catch-invisible-edits'? It's still here... Ah, I missed it since I did not have that variable set. Thanks and sorry for the noise. Cheers, -- Suvayu Open source is the future. It sets us free.
Re: [O] Fixing footnote HTML
Jambunathan K kjambunat...@gmail.com writes: Samuel Wales samolog...@gmail.com writes: On 3/9/13, Jambunathan K kjambunat...@gmail.com wrote: I am sure Samuel will remind us infinitely if we forget about it. Unless you say why it is confusing, I would count the above statement as just mis-information and not a fact that other parties could agree with. You promised to leave: On 2/12/13, Jambunathan K kjambunat...@gmail.com wrote: I let go of my commit access sometime ago. Now, I am leaving this forum. Bastien asked you to ban yourself. Samuel, I asked him to remove ox-html.el and he indicated how he wanted to proceed ahead. He wants ox-html.el in the tree and not GNU ELPA. The code in ox-html belongs to the Org community and to everyone who wants to use Org mode. Your request to Bastien implies a right of property, which doesn't exist. Because you have no property claim, Bastien's wishes don't involve you, they involve the Org community and its potential use of ox-html.el. As one who re-wrote ox-html.el I have every moral authority to accept or reject proposals or handle it the way I see fit. Bastien has the keys. Hehas commit rights, which I don't have. What is the foundation of your moral authority, except some non-existent property right? You have no property right to this code. On the other hand, we have the right not to be excluded from its use and enjoyment. The FSF papers are clear about this. This is how we function as a community. Please understand that we've placed our trust in Bastien and are confident that he will do right by us. He is clearly looking after our best interests by keeping ox-html in the tree. Sorry. The list has to learn to deal with me, even if that amounts to throwing the wares I have written out the window. We are not fools and won't throw out your code until it suits us. It works well and we intend to use and enjoy it for as long as it is useful and enjoyable. I hope you know that I admire your work and think you are a valuable member of our community. But, like the rest of us, you have to deal with the Org community, because it is the Org mode community, ever changing, that will shepherd the code you, many others, and (to a much lesser extent) I wrote. If we work well together on this magnificent idea, Org mode might outlive us all. Peace, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] GFDL
Carsten Dominik carsten.domi...@gmail.com writes:
On 9.3.2013, at 16:25, Achim Gratz strom...@nexgo.de wrote:
Carsten Dominik writes:
I still think it is crazy to add these 8 pages to each time someone prints
it
It fits on exactly two pages (or front and back of one page) if wrapped in
\begin{multicols}{2}
\scriptsize
…
and it is still a lot more readable (even if printed out on A5 instead
of A4) than the fineprint you get with commercial software.
Cool. We should do this
Agreed.
Feel free to make the change in org.texi if you know how to achieve
this in a simple way. I checked the Texinfo manual and the control
over columns and font size is rudimentary. My tests using @iftex
didn't go anywhere :/
--
Bastien
Re: [O] [RFC] Org syntax (draft)
Hi Nicolas, the manual would enjoy a subsection in Hacking on how to create a new exporter, either from scratch or as a derived exporter. (Such a subsection can be short enough, thanks to derived backend.) From this section, we can throw links to the exporter reference document and the Org syntax document published on Worgs. We may also add footnotes referring to the Org syntax relevant sections, when needed. But both reference documents don't fit into the manual IMO. They are great resources for developers, not for users. The footnotes are enough for advanced users who want to go beyond the manual. Thanks! -- Bastien
Re: [O] Fixing footnote HTML
Bastien b...@altern.org writes: Jambunathan K kjambunat...@gmail.com writes: I asked him to remove ox-html.el and he indicated how he wanted to proceed ahead. He wants ox-html.el in the tree and not GNU ELPA. Just to prevent confusion: I never said anything like this. ox-html.el is in the master branch of Org's repository, it will be in GNU ELPA (and Emacs) when we release 8.0. I was typing faster. So I consider what I typed grammatically malformed. Sorry. People who want improvements to ox-html.el should be willing to work with me or act on my comments or argue with me or openly call me I am wrong. To others, if you cannot handle how I come across, there are things that you can do to deal with me - One famous Orger added me to his kill file for example. (I am telling you how to deal with me!) I will comment on what goes in to ox-html.el and offer my opinions on it. I don't have or want commit access. So I am very constrained on what I could do, unlike what my tone implies. --
Re: [O] [RFC] Org syntax (draft)
Bastien b...@altern.org writes: But both reference documents don't fit into the manual IMO. They are great resources for developers, not for users. The footnotes are enough for advanced users who want to go beyond the manual. That said, we can also bundle both documents into Org's distribution, as .org files in the doc/ directory. And have a make rule to convert them to .pdf and info docs. -- Bastien
Re: [O] Fixing footnote HTML
Jambunathan K kjambunat...@gmail.com writes: I was typing faster. So I consider what I typed grammatically malformed. Sorry. No problem. People who want improvements to ox-html.el should be willing to work with me or act on my comments or argue with me or openly call me I am wrong. People who want to work on ox-html.el are welcome to work on anyone subscribed in this list. Since you don't know HTML, maybe you are not in the best position to comment on the HTML output. For the problem at stake, I agree putting footnotes in a HTML table is confusing, I will fix this. I will comment on what goes in to ox-html.el and offer my opinions on it. I don't have or want commit access. So I am very constrained on what I could do, unlike what my tone implies. You're opinion is welcome when it's stated in a civilian tone, like any opinion on this list. -- Bastien
Re: [O] Fixing footnote HTML
Thomas I will reply to you in private. I am talking to Samuels and Ricks who think that I have no right to offer my opinions on what gets in to that file. Jambunathan K.
Re: [O] Fixing footnote HTML
Bastien b...@altern.org writes: Jambunathan K kjambunat...@gmail.com writes: I was typing faster. So I consider what I typed grammatically malformed. Sorry. No problem. People who want improvements to ox-html.el should be willing to work with me or act on my comments or argue with me or openly call me I am wrong. People who want to work on ox-html.el are welcome to work on anyone subscribed in this list. Since you don't know HTML, maybe you are not in the best position to comment on the HTML output. For the problem at stake, I agree putting footnotes in a HTML table is confusing, I will fix this. I wrote the code, I know where it will bite. I will not say it, because you seem so confident. Yes, go ahead and fix it. I will comment on what goes in to ox-html.el and offer my opinions on it. I don't have or want commit access. So I am very constrained on what I could do, unlike what my tone implies. You're opinion is welcome when it's stated in a civilian tone, like any opinion on this list. Not all civilians are civil.
Re: [O] Fixing footnote HTML
Jambunathan K kjambunat...@gmail.com writes: I wrote the code, I know where it will bite. I will not say it, because you seem so confident. Yes, go ahead and fix it. Done, thanks. -- Bastien
[O] Syntax of Org Babel results
Hello, Before Org 8 is out, I'm willing to put light on some last syntax which I find counter-intuitive and not along the lines of the rest: it concerns the `results' parameter. Let's sum up first the list of all parameters: 1. Collection - :results value - :results output 2. Type of results (when :results is set to `value'): - Result types + :results vector + :results scalar + :results list + :results file - Result wrappers + :results raw + :results drawer + :results org (removed, right?) + :results html + :results code + :results latex + :results pp 3. Handling - :results replace - :results silent - :results none - :results append - :results prepend As you see (by the shown structure), the different values answer different questions: - How the results should be collected from the source code block? - How they will be inserted into the Org mode buffer? - How to interpret/wrap the results? - How the results should be handled? And answering many of these questions at the same time means giving a *multi-value* to the parameter, such as: :results list append Wouldn't it make more sense (and be more easily parsed by the machine and be cleaner and less error-prone for us, poor humans) if `results' would be split in different parameters for the different questions they answer, each of those parameters getting at most one value? Something along the lines of: :results_type file :results_insertion append (those names may be ugly, it just for the purpose of explaining my idea). I know that it's the ultimate moment to discuss such a change, would there be consensus, before Org 8 is out. Best regards, Seb -- Sebastien Vauban
Re: [O] [RFC] Org version of the Org manual
Thomas S. Dye writes:
That works nicely. I found the error and orgmanual.pdf is now produced
without errors.
Progress! :-)
With the current version from git I cannot export to texinfo
successfully, though, I get this error near the end of the export:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match(\\`[ \n.]+ nil) (if (string-match \\`[ \n.]+ s)
(setq s (replace-match t t s))) org-trim(nil) (concat \n@item
(if tag desc) \n (org-trim contents) \n) (let* ((tag
(org-element-property :tag item)) (desc (org-export-data tag info)))
(concat \n@item (if tag desc) \n (org-trim contents) \n))
org-texinfo-item((item (:bullet - :begin 41929 :end 42016
:contents-begin 42016 :contents-end 42016 :checkbox nil :counter nil
:hiddenp outline :structure ((40825 2 - nil nil @@info:@kbd{@@C-c
/@@info:}@@, ~org-sparse-tree~ 41031) (41031 2 - nil nil
@@info:@kbd{@@C-c / r@@info:}@@, ~org-occur~ 41929) (41929 2 -
nil nil @@info:@kbd{@@M-g n@@info:}@@ or @@info:@kbd{@@M-g
M-n@@info:}@@, ~next-error~ 42016))…
This may actually a bug in the texinfo exporter.
Is the html version of the Org manual generated from the .texi source?
If so, could you show me how to augment Makefile so the html
document is generated by `make orgmanual'? I want to check if the html
document looks reasonable.
I've extended the Makefile to approximate the one in doc/, HTML is
produced both via makeinfo and as an export via ox-html. To proceed in
an orderly manner and prepare for an eventual integration into Org, can
you please do the following in your Org clone:
git checkout master
git checkout -b orgmanual master
git submodule add https://github.com/tsdye/orgmanual.git
git commit -am 'make orgmanual/ a submodule'
cd orgmanual
git checkout -b orgmanual master
git am orgmanual.patch
From 5511736802ced4e08bd432ebdb12dfeebe282a22 Mon Sep 17 00:00:00 2001
From: Achim Gratz strom...@stromeko.de
Date: Sun, 10 Mar 2013 12:07:19 +0100
Subject: [PATCH] add Makefile, org-version.inc (symbolic link), modify
.gitignore
ignore make products
---
.gitignore | 7 ---
Makefile| 49 +
org-version.inc | 1 +
3 files changed, 54 insertions(+), 3 deletions(-)
create mode 100644 Makefile
create mode 12 org-version.inc
diff --git a/.gitignore b/.gitignore
index 1f940d9..fde636e 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,10 +1,8 @@
*.*~
*.texi
*.info
-Makefile
init.el
export-test.org
-org-version.inc
*.aux
*.cp
*.fn
@@ -17,4 +15,7 @@ org-version.inc
*.vr
*.cps
*.pgs
-.DS_Store
\ No newline at end of file
+.DS_Store
+/orgmanual.html
+/orgmanual.t2d/
+/orgmanual/
diff --git a/Makefile b/Makefile
new file mode 100644
index 000..7c45664
--- /dev/null
+++ b/Makefile
@@ -0,0 +1,49 @@
+TEXI2PDF+=--tidy
+BEXP=$(BATCH) \
+ --eval '(add-to-list '''load-path ../lisp)' \
+ --eval '(setq org-footnote-auto-adjust nil)'
+EXTEXI= -l ox-texinfo \
+ --eval '(add-to-list '''org-export-snippet-translation-alist '''(info . texinfo))'
+EXHTML= -l ox-html \
+ $(BTEST_POST) \
+ --eval '(add-to-list '''org-export-snippet-translation-alist '''(info . texinfo))'
+ORG2TEXI=-f org-texinfo-export-to-texinfo
+ORG2HTML=-f org-html-export-to-html
+ORG2INFO=--eval (org-texinfo-compile \./$\)
+
+.SUFFIXES: # we don't need default suffix rules
+ifeq ($(MAKELEVEL), 0)
+ $(error This make needs to be started as a sub-make from the toplevel directory.)
+endif
+.PHONY: all info html pdf
+
+all: $(ORG_MAKE_DOC)
+
+info: orgmanual.info
+
+html: orgmanual orgmanual.html
+
+pdf: orgmanual.pdf
+
+orgmanual.texi: orgmanual.org
+ $(BEXP) $(EXTEXI) $ $(ORG2TEXI)
+orgmanual.info: orgmanual.texi
+ $(MAKEINFO) --no-split $ -o $@
+orgmanual.pdf: LC_ALL=C# work around a bug in texi2dvi
+orgmanual.pdf: LANG=C # work around a bug in texi2dvi
+orgmanual.pdf: orgmanual.texi
+ $(TEXI2PDF) $
+orgmanual: orgmanual.texi
+ $(TEXI2HTML) $
+orgmanual.html: orgmanual.org
+ $(BEXP) $(EXHTML) $ $(ORG2HTML)
+
+clean:
+ $(RM) org *.pdf *.html \
+ *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs \
+ *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps
+cleanall: clean
+ $(RMR) orgmanual.t2d orgmanual
+
+
+
diff --git a/org-version.inc b/org-version.inc
new file mode 12
index 000..fd0c05b
--- /dev/null
+++ b/org-version.inc
@@ -0,0 +1 @@
+../doc/org-version.inc
\ No newline at end of file
--
1.8.1.4
cd ..
git commit -am 'update submodule orgmanual'
git am org.patch
From 488e1aa75d9420a238851217c39f52ecf317e8a0 Mon Sep 17 00:00:00 2001
From: Achim Gratz strom...@stromeko.de
Date: Sun, 10 Mar 2013 12:11:29 +0100
Subject: [PATCH] add $(EXTRADIRS) to targets.mk for build system integration
of orgmanual/
---
mk/targets.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mk/targets.mk b/mk/targets.mk
index aef11eb..b7fe9cc 100644
--- a/mk/targets.mk
+++ b/mk/targets.mk
@@ -6,7 +6,7 @@ DISTFILES_extra= Makefile
Re: [O] GFDL
Bastien writes: Feel free to make the change in org.texi if you know how to achieve this in a simple way. I checked the Texinfo manual and the control over columns and font size is rudimentary. My tests using @iftex didn't go anywhere :/ Obviously, multicols is a LaTeX package and that code snippet was from one of my own documents that was written directly in LaTeX. So, sadly, I do not have any working example of how to do it in TeX, let alone TeXinfo. So we will have to ask elsewhere to get that kind of expertise. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] org-agenda-write taking very long (probably because of babel)
Karl Voit writes: Since my Org-mode update from today (from 5d467d6f8affc0afe34922e885ac6e2492ddd091 Fri Feb 15 15:28:35 2013 +0100) it takes very long to export the ics file. I guess this relates to ... org-babel-exp processing... [25 times] ... which also pops up some babel result graphics which did not happen before. Was there a change in the default settings or is this a bug? I have worked with Karl to try and find what caused this change in behaviour and it wasn't anything to do with my patch or even recently, but the switch from the old to the new exporter framework for producing the iCalendar files. The patch in question is buried in commit 0a01e52aa1: --8---cut here---start-8--- -- lisp/org-agenda.el -- index 809287b..e9a9efc 100644 @@ -2361,11 +2361,11 @@ (defun org-agenda-mode () [Phases of the Moon org-agenda-phases-of-moon (org-agenda-check-type nil 'agenda 'timeline)] [Sunrise/Sunset org-agenda-sunrise-sunset (org-agenda-check-type nil 'agenda 'timeline)] [Holidays org-agenda-holidays (org-agenda-check-type nil 'agenda 'timeline)] [Convert org-agenda-convert-date (org-agenda-check-type nil 'agenda 'timeline)] -- - [Create iCalendar File org-export-icalendar-combine-agenda-files t]) + [Create iCalendar File org-icalendar-combine-agenda-files t]) -- [Undo Remote Editing org-agenda-undo org-agenda-undo-list] -- (MobileOrg [Push Files and Views org-mobile-push t] @@ -3347,18 +3347,12 @@ (defun org-agenda-write (file optional open nosettings agenda-bufname) (concat (file-name-sans-extension file) .ps)) (expand-file-name file)) (delete-file (concat (file-name-sans-extension file) .ps)) (message PDF written to %s file)) ((string-match \\.ics\\' file) - (require 'org-icalendar) - (let ((org-agenda-marker-table - (org-create-marker-find-array - (org-agenda-collect-markers))) -(org-icalendar-verify-function 'org-check-agenda-marker-table) -(org-combined-agenda-icalendar-file file)) -(apply 'org-export-icalendar 'combine - (org-agenda-files nil 'ifmode + (require 'ox-icalendar) + (org-icalendar-export-current-agenda (expand-file-name file))) (t (let ((bs (buffer-string))) (find-file file) (erase-buffer) (insert bs) --8---cut here---end---8--- So, it seems that the old code did something to prevent source block execution, while the new one does not handle this situation specially. I know next to nothing about agendas or iCalendar export, so I would appreciate if someone more knowledgeable could have a look. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Q+, Q and microQ: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] [RFC] Org syntax (draft)
Bastien writes: That said, we can also bundle both documents into Org's distribution, as .org files in the doc/ directory. And have a make rule to convert them to .pdf and info docs. I don't want to be the party pooper, but if these documents should go into the distribution, then we must insist that all modifications be FSF copyrighted, otherwise we'd have to remove and/or rewrite the ones that aren't when they are incorporated into the distribution. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] TexInfo conversion of Org syntax (Success!)
Jambunathan K writes: Or try C-u M-x info RET org-syntax.info RET Bye, bye webbrowser! Finally a (relatively) painless way to get info documentation, great. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] [new exporter] ignoring a headline on export to PDF?via?latex
Hi Charles, On Wed, Mar 06, 2013 at 07:11:48AM +, Charles Berry wrote: I added to org-hacks.org at the bottom of ** Exporting org files. I tried to push to worg but got a permission error - its been years since I last pushed anything, so something on my end probably needs to be updated. You probably your keys were not moved to the new machine that hosts Worg. An email to Bastien and/or Jason should fix that. I've posted the file at: https://raw.github.com/chasberry/orgmode-accessories/master/filter-markup.org If you would like to put it in org-hacks, I'd appreciate it. I had missed your email, I put your writeup with some minor formatting changes under the new exporters directory on Worg. Please have a look and let me know if they are in order. http://orgmode.org/worg/exporters/ http://orgmode.org/worg/exporters/filter-markup.html Here are the commits: http://orgmode.org/cgit.cgi/worg.git/commit/?id=0ae0f97db6ac6c3ca7cc94001a442e54c2d1d3d9 http://orgmode.org/cgit.cgi/worg.git/commit/?id=ce62735fd8298c8924f76098d768db42b53f155b Thanks a lot for your contribution. :) -- Suvayu Open source is the future. It sets us free.
Re: [O] S-M-right problem in orgstruct-mode
Bastien b...@altern.org writes:
Hi there,
Alan Schmitt alan.schm...@polytechnique.org writes:
even though the cursor is on a structure element. Maybe a more
information this function is disabled would work (if it's possible).
But as I said, it's a nitpick.
thank you very much for testing the patch.
I agree with Alan, let's update the user-error to something more
informative -- Christopher, thanks a lot for the patch! Feel free
to commit and push when you want.
Disabled commands are no-ops now. I pushed this to origin/master.
03b1edf org.el: Disable {pro,de}motion commands in orgstruct-mode if
orgstruct-heading-prefix-regexp is non-nil
Christopher
Re: [O] [RFC] Org syntax (draft)
Achim Gratz strom...@nexgo.de writes: Bastien writes: That said, we can also bundle both documents into Org's distribution, as .org files in the doc/ directory. And have a make rule to convert them to .pdf and info docs. I don't want to be the party pooper, but if these documents should go into the distribution, then we must insist that all modifications be FSF copyrighted, otherwise we'd have to remove and/or rewrite the ones that aren't when they are incorporated into the distribution. No, the documents can go into the distribution with contributions from anyone, because they won't be in Emacs. FSF assignment is needed only for things that go into Emacs. Best, -- Bastien
Re: [O] GFDL
Achim Gratz strom...@nexgo.de writes: Obviously, multicols is a LaTeX package and that code snippet was from one of my own documents that was written directly in LaTeX. So, sadly, I do not have any working example of how to do it in TeX, let alone TeXinfo. So we will have to ask elsewhere to get that kind of expertise. :( I'll keep this issue on my radar and see if something can be done in the .texi file. -- Bastien
[O] emacs export org-mode to wiki: especially for the org-mode tables
hi all I badly need the feature of exporting org-mode to wiki(like mediawiki). After google for a while, I found some links but they don't work for me. Do you guys have any suggestion for this? If no option, I may use lisp to implement them by myself. http://lists.gnu.org/archive/html/emacs-orgmode/2011-07/msg00862.html http://lists.gnu.org/archive/html/emacs-orgmode/2011-07/msg00896.html http://lists.gnu.org/archive/html/emacs-orgmode/2011-03/msg01834.html http://orgmode.org/worg/org-blog-wiki.html http://orgmode.org/ -- Thanks Regards Denny Zhang
[O] ox-odt.el/ox-freemind.el: Please remove it from Org core
ox-odt.el/ox-freemind.el: Please remove it from Org core and don't distribute these files with Org. I don't want to discuss property rights. I am the sole author of ox-odt.el and I don't want it as part of Org distribution. As for ox-html.el etc, interested people can watch emacs-devel for either for amusement or information. Bastien, please oblige. Jambunathan K. --
[O] ox-html.el removal
I would like to remove ox-html.el from Org distribution. My relationship with ox-html.el is a bit complicated and I am not sure how far I can go forward on this front. I am willing to go as far is humanly possible for me to have my displeasure registered. --
Re: [O] asynchronous exporter and babel confirmation
Nicolas Goaziou writes: Hello, Achim Gratz strom...@nexgo.de writes: Done in commit 4f7d514f13. The double hyphens have been omitted based on a discussion with Eric Schulte. Applied to ox.el in commit 69c617c. Thanks a lot! Alan
Re: [O] [RFC] Org syntax (draft)
Bastien But both reference documents don't fit into the manual IMO. You are a jerk, a BIG JERK. Jambunathan K. --
Re: [O] Support Freemind/Freeplane export
On 03/03/2013 08:33 PM, François Pinard wrote: Jambunathan K kjambunat...@gmail.com writes: How many people are going to read HTML code? [...] In short, the concern you have raised is more cosmetic than functional. Replying to the org-mode mailing list. I did not closely followed the discussion, so maybe I'm missing the point. A lot of people are not going to read HTML, but it does not mean that nobody does. Many people still read HTML code, for a variety of reasons. I find HTML code should stay as legible as possible. I agree. I read the HTML code that org generates and there other are people who read the same code and don't use org. Legibility of the code generated by org is a necessity for me. Scott Randby
Re: [O] [RFC] Org syntax (draft)
Bastien writes: No, the documents can go into the distribution with contributions from anyone, because they won't be in Emacs. FSF assignment is needed only for things that go into Emacs. I understood that these or substantial parts of it will end up in the Org manual, which is in Emacs. If that's not the case, then disregard my comment. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptation for Waldorf rackAttack V1.04R1: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [RFC] Org syntax (draft)
Achim Gratz strom...@nexgo.de writes: Bastien writes: No, the documents can go into the distribution with contributions from anyone, because they won't be in Emacs. FSF assignment is needed only for things that go into Emacs. I understood that these or substantial parts of it will end up in the Org manual, which is in Emacs. If that's not the case, then disregard my comment. Emacs lisp has a manual of it's own. I don't see how Org export reference *cannot* end in Emacs. Bastien is doing what(ever) suits his whims and you are approving of it. I disapprove of what you are doing, Achim. Export syntax deserves to be part of Org/Emacs. Let the maintainer go to hell. He is talking irreverently/hand-wavingly about some work which has stretched to good part of around 3 years. The Orgmode maintainership is in the hands of the wrong person, he calls shots based on his owh whims and I regret it. Jambunathan K. Regards, Achim. --
[O] Org Community
Last September, I attended a talk given by the lead developers of a prominent free software project. One of the developers spoke about the importance of maintaining a friendly community that does not drive people away. In particular, the developer emphasized that the community is more important than the code. The org community has been wonderful since I've started using org. My questions on even the most basic matters have been answered with respect and clarity. Even though I'm a mere user of org, I've never hesitated to participate in a discussion on the mailing list. However, I am concerned about the future of org. There is one individual who is poisoning the atmosphere by engaging in unfair and unfounded name calling that simply should not be included in messages to this list. Now this person wants to take some of their contributions out of org. The developer of the talk I attended called this tactic hostage taking and said that it is better for the community to let hostage takers go their own way. The project and community are more important than the code. The code can be written by others, or the community can decide to go in a different direction. Giving in to hostage takers leads to more hostage taking and the decline of the project. Many of the users of org find it to be irreplaceable. We don't want to see org fall apart because of dissension in the community. I'm not saying that we shouldn't have dissent and disagreement. No, those are essential for a vigorous and healthy project. It is hateful and untruthful personal attacks that we should not accept no matter how significant the code contributions of those making the attacks. Scott Randby
Re: [O] [RFC] Org syntax (draft)
Jambunathan K writes: Emacs lisp has a manual of it's own. I don't see how Org export reference *cannot* end in Emacs. I said that I'm expecting these references to become part of the manual(s). I still expect that and will try to help it along, but it doesn't necessarily need to take the exact sequence of events that I envisioned. Bastien is doing what(ever) suits his whims and you are approving of it. I haven't approved or disapproved anything. I have only stated the plain fact that if my understanding of the future course of events is incorrect, then my comment does not apply (and conversely, if it does, then the issue I've stated needs to be dealt with). I disapprove of what you are doing, Achim. You're welcome. (Sun Tzu, III/2) Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] Fixing footnote HTML
Aloha Jambunathan, Jambunathan K kjambunat...@gmail.com writes: Thomas I will reply to you in private. I am talking to Samuels and Ricks who think that I have no right to offer my opinions on what gets in to that file. If this is indeed what is being discussed, then there is no reason to discuss it on the Org mode mailing list. Like every other person, you are free to alter the contents of that file as it pleases you. If you think your changes might benefit other users, and you are still willing to accept the structure of rights in the FSF papers, then you can send patches. The Org community, through its maintainer, Bastien, will do with your patches as it pleases. Alternatively, as Bastien pointed out a while back, you are free to fork Org mode and form your own FSF community of like-minded coders and users. This way, the ideas and opinions of our community members need not concern you at all. Peace, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Macros expanded in Org buffer
t...@tsdye.com (Thomas S. Dye) writes: Aloha all, I'm not sure how this happened, but chapter 2 of orgmanual now has all the macros replaced by their expansions. You can see this here: https://github.com/tsdye/orgmanual/blob/master/orgmanual.org Apologies for the brief post earlier. I discovered this an hour before guests arrived for a dinner I was supposed to be cooking ... Here is what I was doing prior to discovering that all the macros in chapter 2 had been replaced by their expansions. I had been working on description lists throughout the document and had inadvertently left two blank lines in the middle of a list. The error this raises is something along the lines of incorrect argument stringp, nil and I haven't found an easy way to discover from this where the error occurs in the Org buffer. The method I've been using is a variant of one Nick Dokos suggested some years ago in the context of a different problem, and which he called bisecting. What I do, is export one subtree at a time until I find a subtree that doesn't export, then I do this on subtrees of that subtree until I have isolated a reasonably-sized search space. In this instance, once I discovered that chapter 2 had the error, I used toggle-debug-on-error, turned asynchronous export off, and exported chapter 2 to see the debug information. This pointed me in the right direction and I was able to find the problem and fix it. I don't know where in this sequence of events the macros were replaced by their expansion, but I feel certain that it happened during this work because the problem is confined only to chapter 2. I hope this helps. Let me know if you have questions. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] Publish setup in file
Hi, Is there a way to specify publishing options (e.g. the location) at the level of the file to be published, instead doing this globally in the =.emacs= file? I have many projects in orgmode which consist of a single file. I have been looking at #+SETUPFILE (which seems to deal only with org files) and publishing templates (which seem not to be able to change all project options, as the target location). Does anyone of you have an idea on how to do this? Best wishes Julian
Re: [O] ox-html.el removal
I am willing to go as far is humanly possible for me to have my displeasure registered. Dear Jambunathan, your displeasure is very well registered by the hundreds or even thousands of readers of this list. It is very sad to see an obviously very gifted and energetic programmer going in lonely fighter mode without obvious reasons. But: The papers the FSF asked you to sign were constructed for exactly this case I assume. No developer may ever have the rights to destroy afterwards what nice piece of work he once gave to the community! I must admit the FSF is to praise. It always seemed a bit restrictive to me to demand that time consuming process of sending the paperworks all over the world. Now I understand. You authored valuable parts of orgmode, yes. And you promised and decided, through signing the FSF papers, to never take it away again. Now you changed your mind. Humans, even programmers, change their mind. Nevertheless there is your promise on paper, signed by you. It is impossible for you to take anything away now and, morally, that's the right thing, too. Otherwise some contributors could easily destroy communities and their spirit at will whenever their mind would change. So, thanks for your great contributions! No kidding here. Find some peace of mind. Best regards Detlef --
Re: [O] [RFC] Org version of the Org manual
Hello Achim,
On 10 March 2013 08:24, Achim Gratz strom...@nexgo.de wrote:
Thomas S. Dye writes:
That works nicely. I found the error and orgmanual.pdf is now produced
without errors.
Progress! :-)
With the current version from git I cannot export to texinfo
successfully, though, I get this error near the end of the export:
Debugger entered--Lisp error: (wrong-type-argument stringp nil)
string-match(\\`[ \n.]+ nil) (if (string-match \\`[ \n.]+ s)
(setq s (replace-match t t s))) org-trim(nil) (concat \n@item
(if tag desc) \n (org-trim contents) \n) (let* ((tag
(org-element-property :tag item)) (desc (org-export-data tag info)))
(concat \n@item (if tag desc) \n (org-trim contents) \n))
org-texinfo-item((item (:bullet - :begin 41929 :end 42016
:contents-begin 42016 :contents-end 42016 :checkbox nil :counter nil
:hiddenp outline :structure ((40825 2 - nil nil @@info:@kbd{@@C-c
/@@info:}@@, ~org-sparse-tree~ 41031) (41031 2 - nil nil
@@info:@kbd{@@C-c / r@@info:}@@, ~org-occur~ 41929) (41929 2 -
nil nil @@info:@kbd{@@M-g n@@info:}@@ or @@info:@kbd{@@M-g
M-n@@info:}@@, ~next-error~ 42016))…
This may actually a bug in the texinfo exporter.
The error is actually on line 6069 of the manual. The {{{vindex[...]}}}
line and
subsequent paragraph. As far as the list is concerned there is no
associated
content for that list entry. Indenting them appropriately to be recognized
as part
of the list allows for successful export.
This may also be partly a bug, should the exporter allow for a list item
without any contents?
Regards,
Jon
Is the html version of the Org manual generated from the .texi source?
If so, could you show me how to augment Makefile so the html
document is generated by `make orgmanual'? I want to check if the html
document looks reasonable.
I've extended the Makefile to approximate the one in doc/, HTML is
produced both via makeinfo and as an export via ox-html. To proceed in
an orderly manner and prepare for an eventual integration into Org, can
you please do the following in your Org clone:
git checkout master
git checkout -b orgmanual master
git submodule add https://github.com/tsdye/orgmanual.git
git commit -am 'make orgmanual/ a submodule'
cd orgmanual
git checkout -b orgmanual master
git am orgmanual.patch
cd ..
git commit -am 'update submodule orgmanual'
git am org.patch
If you are unsure about any of this, please ask. You can now edit/add
these lines
--8---cut here---start-8---
.PHONY: orgmanual
EXTRADIRS=orgmanual
orgmanual:
$(MAKE) -C $@
--8---cut here---end---8---
to the top of your local.mk and should now be able to do a make
orgmanual. Which types of documentation are produced can be controlled
with ORG_MAKE_DOC (default is info pdf html), just like for the
official manuals. Also, make cleanall will now clean up in orgmanual
also. BTEST_POST should be configured to have a load-path pointing to a
sufficiently advanced htmlize version for the HTML export.
My next step will be to bring orgmanual up-to-date with the changes
that have been made to org.texi since I started the translation several
months ago.
I'm not envious…
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] ox-html.el removal
Am 10.03.2013 19:55, schrieb Detlef Steuer: I am willing to go as far is humanly possible for me to have my displeasure registered. Dear Jambunathan, your displeasure is very well registered by the hundreds or even thousands of readers of this list. It is very sad to see an obviously very gifted and energetic programmer going in lonely fighter mode without obvious reasons. But: The papers the FSF asked you to sign were constructed for exactly this case I assume. No developer may ever have the rights to destroy afterwards what nice piece of work he once gave to the community! I must admit the FSF is to praise. It always seemed a bit restrictive to me to demand that time consuming process of sending the paperworks all over the world. Now I understand. You authored valuable parts of orgmode, yes. And you promised and decided, through signing the FSF papers, to never take it away again. Now you changed your mind. Humans, even programmers, change their mind. Nevertheless there is your promise on paper, signed by you. It is impossible for you to take anything away now and, morally, that's the right thing, too. Otherwise some contributors could easily destroy communities and their spirit at will whenever their mind would change. So, thanks for your great contributions! No kidding here. Find some peace of mind. Best regards Detlef Hi Detlef, thanks for your kind words. Just a remark to copyright assignment though, as I always thought it being wrong: it doesn't interfere here. Once code is published under GPL, don't see a way to revoke the license. GPL'ed code is all what's needed for distribution. Best, Andreas
Re: [O] [RFC] Org version of the Org manual
Jonathan Leech-Pepin writes:
The error is actually on line 6069 of the manual. The {{{vindex
[...]}}} line and subsequent paragraph. As far as the list is
concerned there is no associated content for that list
entry. Indenting them appropriately to be recognized as part of the
list allows for successful export.
Thanks for tracking that down.
This may also be partly a bug, should the exporter allow for a list
item without any contents?
Well it should maybe not allow for it, but I think it should either
expect to get a nil in that situation or otherwsie not let the error
propagate. Anyway, it's great to have such a large and complex document
available to train the exporter on.
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Waldorf MIDI Implementation additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] ox-html.el removal
Detlef Steuer detlef.ste...@gmx.de writes: But: The papers the FSF asked you to sign were constructed for exactly this case I assume. That's not right. https://www.gnu.org/licenses/why-assign.html I am not a copyright lawyer. So is everyone else subscribed to this list. The FSF's copyright clerk should assist on this issue. #+BEGIN my2cents If Jambunathan does not want code he wrote to be part of Org any more, I'd respect his wish. At first sight this is a loss for Org. This does not need to be the end, though. GSoC is coming up, rewriting specific exporter look like great projects. Jambunathan did not mention what is going to happen to his code. Jambu, are you going to maintain the code you wrote separately. If so, is code free, libre and upwards compatible to future Org releases? #+END A long yet somewhat relevant read: https://lwn.net/Articles/529522/ http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/6465 Christopher
Re: [O] [RFC] Org version of the Org manual
On 10 March 2013 15:25, Achim Gratz strom...@nexgo.de wrote:
Jonathan Leech-Pepin writes:
The error is actually on line 6069 of the manual. The {{{vindex
[...]}}} line and subsequent paragraph. As far as the list is
concerned there is no associated content for that list
entry. Indenting them appropriately to be recognized as part of the
list allows for successful export.
Thanks for tracking that down.
This may also be partly a bug, should the exporter allow for a list
item without any contents?
Well it should maybe not allow for it, but I think it should either
expect to get a nil in that situation or otherwsie not let the error
propagate. Anyway, it's great to have such a large and complex document
available to train the exporter on.
The error is not actually within ox-texinfo in this case however I suspect.
The exact same code (at the location of the error in ox-texinfo) appears
within
ox-latex and ox-ascii.
`(org-trim contents)', which removes whitespace at start and end of string,
in this case with the string being the contents of the list item. When
there is
no contents there is no string to clean up.
Regards,
Jon
Regards,
Achim.
--
+[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+
Waldorf MIDI Implementation additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
Re: [O] src blocks in texinfo export
Hello Dario,
On 12 February 2013 17:09, Dario Hamidi dario.ham...@gmail.com wrote:
Hello Jonathan,
Using your patch as is would wrap the source blocks in both example and
verbatim blocks. If going with verbatim it would be better to remove all
references to @example/@end example.
I don't understand where the problem lies with having a `@verbatim'
within a `@example'. Could you maybe explain to me why this is
problematic?
Using both environments seems to achieve the goal of having an idented
source block in the resulting info file without having to further
process the source block before export.
Consider exporting
#+BEGIN_SRC sh
function fails
{
echo this causes an error with makeinfo
}
#+END_SRC
with only the verbatim environment:
File: test.info, Node: Top, Up: (dir)
Manual
**
function fails
{
echo this causes an error with makeinfo
}
and with verbatim in example:
File: test.info, Node: Top, Up: (dir)
Manual
**
function fails
{
echo this causes an error with makeinfo
}
It should be possible to escape any braces or @ before inserting them
into
the
example block to ensure there is no expansion.
While it certainly is possible, it would also mean to properly escape
*all* characters with a special meaning to TeX. I suppose that making
text containing such characters visible in a document without having to
escape them is what the verbatim environment is for.
The only differences in using @verbatim over escaping any characters in
@example are the following:
- Tabs are treated as tabs and not as single spaces
- The code block is not indented.
Preserving whitespace seems like a good idea when displaying python
source code or makefiles.
Dario
I've implemented a fix for this that should resolve the issue. `@ { }` are
now
properly escaped before export within source blocks. I didn't wrap the one
block in the other since the issue also existed within lisp blocks (where
inserting a verbatim block within a lisp block would have likely caused
issues
had someone wanted to extract any @lisp code from the info file.
Regards,
Jon
Re: [O] [PATCH] * lisp/ob-core.el (org-babel-execute-src-block): insert hash for silent results
Achim, Eric, Achim Gratz wrote: Eric Schulte writes: A hash marks a *result* with an indication of what was used to generate it (code block parameters). The point of a hash is to allow the result to be returned without having to re-execute. For this reason, I think that the hash should live with the result. Here Babel is assuming a very specific execution model, namely a functional one (a function with the same parameters always delivers the same results, so if you see the same function invoked with the same parameters you can just substitute the result from an earlier invocation). Babel isn't a functional language however, so it is both possible and done in practice to use it for side-effects or even side-effects only. But back to my earlier remark about the hash value actually being a signature of the source block and not the result. If I use noweb references, the reference text is cached, not its expansion. Well seen... I wouldn't have thought of that... A more general question: shouldn't cache be unusable (generate an error) when there is a session? In the presence of a session, I've the impression that caching results is always wrong. Who knows its contents before executing the code, in the next Emacs session? Best regards, Seb -- Sebastien Vauban
Re: [O] [RFC] Org version of the Org manual
Hello, Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes: The error is not actually within ox-texinfo in this case however I suspect. The exact same code (at the location of the error in ox-texinfo) appears within ox-latex and ox-ascii. `(org-trim contents)', which removes whitespace at start and end of string, in this case with the string being the contents of the list item. When there is no contents there is no string to clean up. I'm unsure about the part of the code you're referring to: in ox-latex.el, there is (and contents (org-trim contents)), which shouldn't generate an error. Would you mind providing an ECM for the problem you're describing? Thank you. Regards, -- Nicolas Goaziou
Re: [O] ox-html.el removal
Aloha Christopher, Christopher Schmidt christop...@ch.ristopher.com writes: #+BEGIN my2cents If Jambunathan does not want code he wrote to be part of Org any more, I'd respect his wish. At first sight this is a loss for Org. This does not need to be the end, though. GSoC is coming up, rewriting specific exporter look like great projects. I don't think it is in the community's best interest to respect Jambunathan's wish. I agree with you that losing code he contributed would be a loss for the Org community. Why should our community sustain such a loss? On the other hand, I think your GSoC idea is a good one. Working with Nicolas' export framework would be a terrific experience for students. If the GSoC coders come up with a functional replacement for ox-html, then we can choose to use the replacement, instead. I guess this would be Nicolas call as potential mentor? I think the Org community might want to decide whether or not to accept patches from Jambunathan K in the future. I don't think we are under any obligation to accept his contributions. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] [RFC] Org version of the Org manual
Hello, On 10 March 2013 16:23, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes: The error is not actually within ox-texinfo in this case however I suspect. The exact same code (at the location of the error in ox-texinfo) appears within ox-latex and ox-ascii. `(org-trim contents)', which removes whitespace at start and end of string, in this case with the string being the contents of the list item. When there is no contents there is no string to clean up. I'm unsure about the part of the code you're referring to: in ox-latex.el, there is (and contents (org-trim contents)), which shouldn't generate an error. Oops. I'd forgotten to include the (and contents ...) around the (org-trim contents). Sorry for the noise. Regards, Jon Would you mind providing an ECM for the problem you're describing? Thank you. Regards, -- Nicolas Goaziou
Re: [O] [PATCH] * lisp/ob-core.el (org-babel-execute-src-block): insert hash for silent results
Sebastien Vauban writes: A more general question: shouldn't cache be unusable (generate an error) when there is a session? In the presence of a session, I've the impression that caching results is always wrong. Who knows its contents before executing the code, in the next Emacs session? That depends on what execution model you have in mind. Generally caching results from a session has questionable utility as you mention, since you still have to arrange certain things by hand. Now, if Babel would provide a way to check a session ID and have the hash depend on it also, then suddenly this becomes an extremely useful tool. One application would be to ensure that certain initialization have taken place (but only once) in that session even though the code calling into the session hasn't set it up. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Factory and User Sound Singles for Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
Re: [O] Help with babel results
Michael Gauland mikely...@no8wireless.co.nz writes:
I'm working with an sqlite database of songs, and I've run into trouble
with titles that start with a '(' (for example,
(I Can't Get No) Satisfaction). 'Verbatim' results work:
#+BEGIN_SRC sqlite :db test-db :results verbatim
.mode csv
.separator |
drop table playlist;
create table playlist (title varchar, artist varchar);
insert into playlist values((I Can't Get No) Satisfaction,
Rolling Stones);
select * from playlist;
#+END_SRC
#+RESULTS:
: (I Can't Get No) Satisfaction|Rolling Stones
But :results table' reports:
eval: Symbol's function definition is void: I
It looks to me like org is trying to interpret (I Can't Get No) as emacs
lisp, but I haven't been able to figure out how to prevent that.
Advice would be greatly appreciated.
Kind Regards,
Mike
Hi Mike,
Thanks for reporting this problem. Your diagnosis is correct, the table
contents were being interpreted as lisp. I've fixed this issue with the
attached patch. I'm unable to ping orgmode.org right now, so I can't
commit this fix, but I will commit it as soon as I'm able.
Thanks,
From 2196096cdecde82c9af8695422ae3f6c5fa42ff1 Mon Sep 17 00:00:00 2001
From: Eric Schulte schulte.e...@gmail.com
Date: Sun, 10 Mar 2013 15:34:56 -0600
Subject: [PATCH] don't read sqlite output as lisp
Thanks to Michael Gauland for pointing out this bug.
* lisp/ob-sqlite.el (org-babel-sqlite-table-or-scalar): Don't read
sqlite output as lisp.
---
lisp/ob-sqlite.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/ob-sqlite.el b/lisp/ob-sqlite.el
index 30bfc73..84d4688 100644
--- a/lisp/ob-sqlite.el
+++ b/lisp/ob-sqlite.el
@@ -143,7 +143,7 @@ This function is called by `org-babel-execute-src-block'.
(mapcar (lambda (row)
(if (equal 'hline row)
'hline
- (mapcar #'org-babel-read row))) result)))
+ (mapcar #'org-babel-string-read row))) result)))
(defun org-babel-sqlite-offset-colnames (table headers-p)
If HEADERS-P is non-nil then offset the first row as column names.
--
1.8.1.5
--
Eric Schulte
http://cs.unm.edu/~eschulte
Re: [O] [RFC] Org syntax (draft)
Hello On 10 March 2013 13:12, Achim Gratz strom...@nexgo.de wrote: Jambunathan K writes: Emacs lisp has a manual of it's own. I don't see how Org export reference *cannot* end in Emacs. I said that I'm expecting these references to become part of the manual(s). I still expect that and will try to help it along, but it doesn't necessarily need to take the exact sequence of events that I envisioned. I have to agree with Bastien that they do not really fit into the main Org manual. Providing them with Emacs (so that they are immediately available) is a good thing in my mind, however I would put them as a separate document similarly to how the Elisp manual is separate. Regards, Jon Bastien is doing what(ever) suits his whims and you are approving of it. I haven't approved or disapproved anything. I have only stated the plain fact that if my understanding of the future course of events is incorrect, then my comment does not apply (and conversely, if it does, then the issue I've stated needs to be dealt with). I disapprove of what you are doing, Achim. You're welcome. (Sun Tzu, III/2) Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
Re: [O] [PATCH] Make `org-contacts-message-complete-function' work with byte compilation
Frank Terbeck f...@bewatermyfriend.org writes: Hi Frank, Thank you for the report; however, I'm unsure about the right solution. There is a problem with the current (eval-when-compile ...) but there are still warnings when I compile it (with emacs -batch -f batch-byte-compile). In org-contacts-db-need-update-p: org-contacts.el:169:14:Warning: function `some' from cl package called at runtime In org-contacts-filter: org-contacts.el:211:37:Warning: function `some' from cl package called at runtime In org-contacts-test-completion-prefix: org-contacts.el:373:12:Warning: function `find-if' from cl package called at runtime In org-contacts-complete-name: org-contacts.el:445:71:Warning: function `remove-duplicates' from cl package called at runtime Those warnings disapear if I simply (require 'cl) at toplevel but it triggers this warning: org-contacts.el:40:1:Warning: cl package required at runtime @All: Can I use (require 'cl) and ignore the warning or is there better solution? -- Daimrod/Greg pgp2M1C9H7f_a.pgp Description: PGP signature
Re: [O] Help with babel results
I've now committed this patch. -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [RFC] Org version of the Org manual
Achim Gratz strom...@nexgo.de writes: Thomas S. Dye writes: That works nicely. I found the error and orgmanual.pdf is now produced without errors. Progress! :-) With the current version from git I cannot export to texinfo This is fixed now. I've extended the Makefile to approximate the one in doc/, HTML is produced both via makeinfo and as an export via ox-html. To proceed in an orderly manner and prepare for an eventual integration into Org, can you please do the following in your Org clone: git checkout master git checkout -b orgmanual master git submodule add https://github.com/tsdye/orgmanual.git git commit -am 'make orgmanual/ a submodule' cd orgmanual git checkout -b orgmanual master git am orgmanual.patch cd .. git commit -am 'update submodule orgmanual' git am org.patch This all worked fine. Thanks for the detailed instructions. If you are unsure about any of this, please ask. You can now edit/add these lines .PHONY: orgmanual EXTRADIRS=orgmanual orgmanual: $(MAKE) -C $@ to the top of your local.mk and should now be able to do a make orgmanual. Which types of documentation are produced can be controlled with ORG_MAKE_DOC (default is info pdf html), just like for the official manuals. Also, make cleanall will now clean up in orgmanual also. BTEST_POST should be configured to have a load-path pointing to a sufficiently advanced htmlize version for the HTML export. I do have a problem here. I think I have mis-configured BTEST_POST. I have this: BTEST_POST = # -L path-to/ert # needed for Emacs23, Emacs24 has ert built in # -L path-to/ess # needed for running R tests -L contrib/lisp/htmlize.el # need at least version 1.34 for source code formatting Now 'make orgmanual' returns this: local.mk:55: *** commands commence before first target. Stop. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] ox-html.el removal
On 11/03/13 06:30, Christopher Schmidt wrote: Detlef Steuer detlef.ste...@gmx.de writes: But: The papers the FSF asked you to sign were constructed for exactly this case I assume. That's not right. https://www.gnu.org/licenses/why-assign.html I am not a copyright lawyer. So is everyone else subscribed to this list. The FSF's copyright clerk should assist on this issue. That may be why the FSF *wants* copyright, but that hardly matters. The fact is (I presume) that copyright *was* assigned to the FSF and therefore the FSF is the entity that can determine the rights of copy, distribution, etc of the code. This is very common in publishing: the author is asked to assign copyright to the publisher, and it is then the publisher who has rights formerly held by the author. Cheers, Alan #+BEGIN my2cents If Jambunathan does not want code he wrote to be part of Org any more, I'd respect his wish. At first sight this is a loss for Org. This does not need to be the end, though. GSoC is coming up, rewriting specific exporter look like great projects. Jambunathan did not mention what is going to happen to his code. Jambu, are you going to maintain the code you wrote separately. If so, is code free, libre and upwards compatible to future Org releases? #+END A long yet somewhat relevant read: https://lwn.net/Articles/529522/ http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/6465 Christopher -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] Fixing footnote HTML
Hi Bastien, Thanks for removing the table tags. It looks great in w3m. Much less confusing. For some reason, I am getting no blank lines between footnotes, and no blank lines between paragraphs in multi-paragraph footnotes. Any idea why? Tested in Firefox. I can try to dig up old exporter output if that will help, as that looked good. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com The disease DOES progress. MANY people have died from it. It attacks MANY body systems. ANYBODY can get it. There is NO hope without activist action. This means YOU.
Re: [O] Org Community
Scott Randby srandby at gmail.com writes: However, I am concerned about the future of org. There is one individual who is poisoning the atmosphere by engaging in unfair and unfounded name calling that simply should not be included in messages to this list. Now this person wants to take some of their contributions out of org. The developer of the talk I attended called this tactic hostage taking and said that it is better for the community to let hostage takers go their own way. The project and community are more important than the code. The code can be written by others, or the community can decide to go in a different direction. Giving in to hostage takers leads to more hostage taking and the decline of the project. I'm inclined to agree with this. I don't feel like hesitating to name names. Jambunathan: Whatever offense was done to you, it remains true that ego-validation often (perhaps even usually) does not go along with accomplishing goals. I would like to be sympathetic to the injustice you feel. This is difficult when your approach to the problem is to hold your ego to be more important than the goal. So what is the point here? If the point is to have well-functioning HTML, ODT and freemind exporters (and, secondarily, to enjoy knowing that you made, or helped to make, that happen), I think that's a worthy goal which the org community should support. If this is your goal, surely it can't be lost on you that your actions are impeding that goal. If, on the other hand, your goal is to prove that you are an Important Person (and secondarily to contribute to org), then your actions are consistent with that goal. However, I think the org community would not be well-served by catering to your ego demands. I contribute code and documentation to SuperCollider (an audio programming language). When I check in new content, I consider it a way to thank other developers who wrote code that I'm glad I didn't have to write myself. I don't expect credit and I don't expect my contributions to be inviolable entities that nobody should touch. It's not about ownership. It's about making a software environment that works better for people. The org community functions on the same principle, and I think it's correct that this community should not cave in to a diva's temper tantrums. hjh
Re: [O] ox-html.el removal
Christopher Schmidt christop...@ch.ristopher.com writes: Detlef Steuer detlef.ste...@gmx.de writes: But: The papers the FSF asked you to sign were constructed for exactly this case I assume. That's not right. https://www.gnu.org/licenses/why-assign.html I am not a copyright lawyer. So is everyone else subscribed to this list. The FSF's copyright clerk should assist on this issue. I really am not discussing what I am going to do with people on this list. My disagreements are past discussion. My code has not landed in Emacs and Org-8.0 is not released. #+BEGIN my2cents If Jambunathan does not want code he wrote to be part of Org any more, I'd respect his wish. At first sight this is a loss for Org. This does not need to be the end, though. GSoC is coming up, rewriting specific exporter look like great projects. You can write exporters even if they are available elsewhere. That said, Writing exporters is an easy job - a low hanging fruit so to speak - and if you are a student, I recommend that you focus on more interesting projects that pose some challenge and provide opportunities to think in critical manner and frustrate you in some way. I would consider Nicolas work - Writing a parser, developing a spec, defining APIs - etc as a project that has broader scope. Writing exporters is meh!. Poor me, I have been stupid. If you are interested in project ideas concerning Org, talk to Nicolas Goaziou. I am sure he will not disappoint you. See whether you can use element infrastructure in other heavily used parts of Org core - say agenda generation. Work on projects where the project maintainer has written substantial amount of challenging code for considerable period. Also, look for project ideas that can continue for considerable period of time, work that you can revisit for the next GSOC or one that you can continue after your current course work. You want to look for work with greater scope. Actively seek projects where the requirements and what-is-to-be-done is either not clear or the time investment required to achieve the goal cannot be established apriori. Also look for features that are new and young. They tend to have challenges that are easily defined but not refined. If you are interested in Emacs, keep tracking Stefan Monnier's or Eli Zaretskii's posts. They drop hints during casual discussion on where they want things improved - Concurrency support in Emacs, Eli may have some ideas on improvement to Bi-directional support, Use of Red-Black trees and improvement to overlays code, porting over C code to Lisp etc. I can dig up the mailing lists if you are interested. I wish to more GSoC contributions in to core Emacs. Jambunathan did not mention what is going to happen to his code. I don't know. I believe it will continue to remain in repos and in people's disks. I cannot cleanup the whole internet, can I? Jambu, are you going to maintain the code you wrote separately. If so, is code free, libre and upwards compatible to future Org releases? I use Emacs (and have been using it for atleast 10 years or so). I support Free Software. Even if my combative positioning doesn't amount to anything much, I want to throw in a little friction by the way of Bastien and the current release. I am stating my purpose in no uncertain terms - yes it is to delay the release or cause confusion. I contribute to Free Software under my pleasure - it is my time and efforts and my resources - and I have freedom to exercise my discretion on what conditions and what projects I contribute to. It is possible that ox-html.el is re-written. It is unlikely that ox-odt.el is *not* re-written. So I will release ox-odt.el for inclusion in to Emacs or GNU ELPA after a 6 month or 1 year period. My code is meant for others to use and I am not bothered about a 6 month or a 1 year break. #+END A long yet somewhat relevant read: https://lwn.net/Articles/529522/ http://thread.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/6465 I have seen these threads. I have a casual interest in such stuff. May be it is time I developed a nuanced understanding of how copyright etc works in real world. When it comes to law, much depends on context and the context has to be un-equivocally established by debating parties and a judge. It is possible that my case is different, and I will see what opinions people have to offer. By people, I mean people-in-the-know. Christopher
Re: [O] ox-html.el removal
Aloha Jambunathan, Jambunathan K kjambunat...@gmail.com writes: Even if my combative positioning doesn't amount to anything much, I want to throw in a little friction by the way of Bastien and the current release. I am stating my purpose in no uncertain terms - yes it is to delay the release or cause confusion. Neither of these contributes to the goals of the Org community. I appreciate your honesty in stating them specifically, but a contributing member of the Org community would be ashamed to share these purposes. I contribute to Free Software under my pleasure - it is my time and efforts and my resources - and I have freedom to exercise my discretion on what conditions and what projects I contribute to. Yes, absolutely. And the Org community is free to reject contributions as it sees fit. So I will release ox-odt.el for inclusion in to Emacs or GNU ELPA after a 6 month or 1 year period. My code is meant for others to use and I am not bothered about a 6 month or a 1 year break. Good news. I look forward to the release of this code. It would be great if you could announce the release on our mailing list. All the best, Tom -- Thomas S. Dye http://www.tsdye.com
