Re: [O] [PATCH] session with python-mode.el complains of void py-toggle-shells
Am 24.01.2013 15:10, schrieb Bastien: Hi Andreas, Andreas Röhler andreas.roeh...@online.de writes: Okay, I'll dig into. For the moment: assume this code should not be needed, python-mode.el should act that all. But let me have a closer look, Great, thanks a lot! ob-python.el patch again better provision for XEmacs users commit 0fd2ac7ede3d7c8602a0a71fe1dc1678773baee4 Author: Andreas Roehler andreas.roeh...@online.de Date: Fri Feb 22 09:08:28 2013 +0100 Depend default python-mode from existing feature The former (if (featurep 'xemacs) 'python-mode 'python) makes a wrong assumption, as python-mode.el provides 'python-mode which does not depend from use of XEmacs python-mode.el should provide a defcustom still to choose environment TINYCHANGE diff --git a/lisp/ob-python.el b/lisp/ob-python.el index 02d762c..c9118e9 100644 --- a/lisp/ob-python.el +++ b/lisp/ob-python.el @@ -43,7 +43,7 @@ (defvar org-babel-python-command python Name of the command for executing Python code.) -(defvar org-babel-python-mode (if (featurep 'xemacs) 'python-mode 'python) +(defvar org-babel-python-mode (if (or (featurep 'python-mode)(featurep 'xemacs)) 'python-mode 'python) Preferred python mode for use in running python interactively. This will typically be either 'python or 'python-mode.)
Re: [O] [ANN] TaskJuggler ported to new export framework
Hi Nicolas, Nicolas Goaziou n.goaz...@gmail.com writes: I eventually ported TaskJuggler back-end to new export framework. great, thanks a lot for this. Christian, as the TaskJuggler expert out there, and if you have some free time in the next few weeks, please let us know if it works correctly (for TJ2 and TJ3). If the Worg page about TaskJuggler needs some update, please feel free to go ahead or ask some help on the list. Thanks! -- Bastien
Re: [O] need: custom agenda for last 7 days
Hi Subhan, Subhan Tindall subhan.tind...@rentrakmail.com writes: '(org-agenda-custom-commands (quote ((w Weekly Logs agenda ((org-agenda-span 8)) You can combine `org-agenda-span' and `org-agenda-start-day', which interprets negative values correctly: '(org-agenda-custom-commands (quote ((w Weekly Logs agenda ((org-agenda-span 8) (org-agenda-start-day -7)) And *yes*, we need more documentation and tutorials on this. Help is welcome! Best, -- Bastien
Re: [O] need: custom agenda for last 7 days
I was just trying to search for this the other day. On Feb 22, 2013, at 5:19 PM, Bastien b...@altern.org wrote: Hi Subhan, Subhan Tindall subhan.tind...@rentrakmail.com writes: '(org-agenda-custom-commands (quote ((w Weekly Logs agenda ((org-agenda-span 8)) You can combine `org-agenda-span' and `org-agenda-start-day', which interprets negative values correctly: '(org-agenda-custom-commands (quote ((w Weekly Logs agenda ((org-agenda-span 8) (org-agenda-start-day -7)) I believe you need to pass a string to =org-agenda-start-day=. (org-agenda-start-day -7) And *yes*, we need more documentation and tutorials on this. For this variable, =org-agenda-start-day=, give a link to the document of the function =org-read-date= would be great. I had to read through the source code to understand it. Help is welcome! Best, -- Bastien
[O] [Bug] Export Coding System
I've ran into this before, but I guess I wasn't able to clearly explain what the
issue was at the time... so let's try again.
I'm exporting an Org file in UTF-8 to LaTeX. Unless I switch the coding system
in Emacs from default to UTF-8 (which has the side effect that any new
buffer will have UTF-8 coding, which is usually not what I want), the LaTeX
buffer gets created with ISO8859-1/latin-1 encoding (which is dead wrong,
because several characters in the document are in fact not representable in that
encoding). Changing the option Org Export Latex Coding System to utf-8
doesn't change how the LaTeX buffer gets created, but it will then helpfully ask
when its time to save the buffer if I want to save it as UTF-8 (no, I want it
created with UTF-8, not changed to a different encoding on save). That salvages
a few characters, but the larger damage of \usepackage[latin1]{inputenc} doesn't
get changed of course.
The coding system of any export buffers should by default follow the Org buffer
they are created from and any changes to the coding system stipulated by export
configuration must be applied before the buffer coding system gets used to make
any decisions on how to export things.
Regards,
Achim.
[O] [Worg][Bug] extra ...-source.html files in Worg
Something seems to run amok when Worg gets published, if you look in the sitemap under org-tools you'll find entries for index.html, index-source.html, index-source-source.html and so on. The documents actually exist (not showing the source of course). This seems to happen in a few other places as well. I don't know since when this might have been going on. Regards, Achim.
Re: [O] comments after paragraph remove newline
Samuel Wales samolog...@gmail.com writes: On 2/10/13, Nicolas Goaziou n.goaz...@gmail.com wrote: Blank lines below an element belong to that element, by definition. So, obviously, just add a blank line between comments and # test and it will not be removed. You are saying that the comments get removed with the blank line because the blank line is considered part of the comments? Is silence following music still music? ;) Blank lines belong to the comments element, but are not commented themselves. In my case, the proposed solution changes the meaning of the comment. For example: === a b c d # e # f new paragraph === If you make e and f a new paragraph, it is intended to be a new paragraph and no longer refers to the previous paragraph. I don't know the code, but is it possible that, instead of attaching blank lines to elements, blank lines can be an element on their own? It's not a matter of where to store it, but what to do with it. Would that allow the needed flexibility and also add orthogonality for other purposes? I don't think we need it. I have pushed a patch for that. Note that now, blank lines before the comment and after it will accumulate. Regards, -- Nicolas Goaziou
[O] org-element
The Org fragment
\[
r = a
+ b
- c
\]
gets interpreted as something strange with a list inbetween. Thus it gets
exported as:
$\backslash$[
r = a
\begin{itemize}
\item b
\item c
\end{itemize}
$\backslash$]
How is one supposed to write (longer) equations out on multiple lines (leaving
the operators behind on the previous line obviously works, but is ugly)?
Regards,
Achim.
Re: [O] FIXME lines in ox-html.el
Hi Terry, tftor...@tftorrey.com (T.F. Torrey) writes: There are about 25 lines of what looks like function or filter names under the heading of FIXME in ox-html.el. I fixed some FIXME in ox-html.el and removed some of the final FIXME lines that were already fixed. Does anyone know if these are features handled by the old exporter but not yet by the new one, goals for new functionality, or something else? I think this is it: features that were handled by the old exporter and still need to be implemented. Do these need to be resolved before the new exporter can reliably replace the old one? The more we fix the better. Help is welcome here. Thanks, -- Bastien
[O] thank you !!
Hello org world, I have silently used org-mode for quite a while, but now comes the time when I need some help. I must say it feels a bit like the smallest shareholder taking the mic in front of a big meeting, so I figured it would be nice to first say the obvious: THANK YOU !!! I use org in part thanks to the immense flexibility of the tool, and in part thanks to the wonderfull sharing habit in the community. Org is such a flexible beast that it can be daunting for a newcomer to start using it. But thanks to that sharing habit, getting things done with org has just been a matter of finding the wizzards who work mostly like I do and have shared their configuration. I just then had to tweak the small bits to make it fell like home. So a big thanks to all of you: developpers, community, wizzards,... it is a real pleasure to be (even a small) part of this whole thing. Thanks for reading, now I can ask my questions in the next message :-) -- Rémi
Re: [O] ob-doc-R-extended.org
Greetings, On Fri, Feb 22, 2013 at 3:55 AM, Andreas Röhler andreas.roeh...@easy-emacs.de wrote: Coming upon this tutorial, which seems excellent for beginners http://orgmode.org/worg/sources/FIXME/ob-doc-R-extended.org maybe move from FIXME into common place? Andreas Yes, I agree, that's an excellent one, and a person can find another version of it here: https://github.com/erikriverson/org-mode-R-tutorial Coincidentally, just last week I was working on this (fixing broken links, etc) mostly with an eye to update with recent developments and make compatible with the new exporter. I contacted the original author a couple days ago to see if he would like to incorporate those updates, but I haven't heard back from him. Unfortunately my updated draft is on my computer at home so I would have to wait until later this evening before I could share the updates. (If there's interest, of course.) Regards, Jay
Re: [O] [Feature Request] Cross headings in tables
On 17 feb. 2013, at 09:35, Nicolas Goaziou n.goaz...@gmail.com wrote: Hello, Achim Gratz strom...@nexgo.de writes: I've just looked at how to implement this using org-element and the new exporter. Much to my dismay I found that table headers are not a separate row or row group type and the new exporter is still using this everything before the first separator is a heading kludge. I wouldn't call that a kludge. That's where most of the mere mortals expect the heading to be anyway. Also, it's somewhat back-end specific. It's easy enough to introduce a second type of separator in org-element (BTW, I don't think that 'rule is a particularly good symbol name for this) by adding another type of table rows, but then these lines get ignored by the new exporter. While the logic used there is amendable (not as easily), it would be more hackish than I hoped. You only need to modify org-element if Org syntax has been changed. Also, it appears that each element can have only one property or did I miss something? It seems that having a way to get the (main) property and then asking if there are sub-properties on that element would allow simpler code in this particular instance and likely elsewhere. Maybe I missed how to do it, though. I don't understand that part. For example: --8---cut here---start-8--- * TODO Headline :tag: --8---cut here---end---8--- In the following buffer, you can have: (org-element-property :priority (org-element-at-point)) (org-element-property :tag (org-element-at-point)) (org-element-property :todo-keyword (org-element-at-point)) (org-element-property :todo-type (org-element-at-point)) (org-element-property :level: (org-element-at-point)) ... So there is more than one property. See: http://orgmode.org/worg/dev/org-export-reference.html for a list of all properties associated to a given element or object type. The cleanest way to implement this would be if being a header would be a property of the row group (maybe returnable as the sign of the row group number). There'd be two types of separators, |- and |~. If the line past the end of a row group is |~, then it is a header group, otherwise it is a normal group. This is incompatible with tradition, but it would allow to use row groups in formulas without introducing unwanted headers. Thoughts? I think the cleanest way to implement this would be to _not_ modify Org syntax, because it is export back-end very specific. Something like: #+attr_html: :header-groups (1 3) | This | will | | be| a header | |---+---| | This | won't | |---+---| | This will | be too| |---+---| | This | won't too | I really like this approach, to mark the header groups in an attribute - maybe an backend-independent attribute? The reason why I prefer this approach is that I am weary of new syntax in Org-mode that will take up new characters of character chains. For the case of tables, if I could go back, I would even remove some of the syntax I introduced, for example for defining the values of constants - that should have been an attribute-link thing as well. Probably even row and column naming, could have been done in this way. - Carsten
[O] org-sync and redmine
Hello again org world, org is real nice and all for my personnal organization, but I now have to communicate with others for some projects. Org-sync to the rescue, and as I dislike using hosted services like github or bitbucket, the natural choice is redmine. So I installed redmine, tested it, and all is well under the sun. Except that org-sync (at least the redmine backend) seems to be lacking quite a bit. Correct me if I'm wrong, but I think that the most current org-sync comes from here: https://github.com/daimrod/org-sync With that, the first errors that I got came from org-element, so I installed org-element from git HEAD (as instructed in the doc). Then I have no lisp errors, but the result is not very useable. Issues import ok, but they are all closed in org, and the descriptions are missing the last character. If I sync what I imported, I get conflicts about the descriptions: local has descriptions minus one char, and remote has an additionnal «^M» at the end. I am offered to resolve the conflicts, but somehow this gets me duplicate issues at the next sync :-( Ok my non existent lisp knowledge would slow me to a crawl, but I can probably solve that problem. However the issues being interpreted as closed seems a bit further out of my reach. And this is after a quick small test, so I have no idea what lurks further down that road. If the whole org-sync is out of date and needs some rough love, there is no way I can tackle that with my level of lisp knowledge. So I get to ask if anyone that I'm not aware of is still currently working on org-sync, and if yes if they are interrested in fixing the redmine backend ? I can provide a test account and project on a recent redmine if that helps, and I can try to help a bit on the org-sync side, although my lisp knowledge is near zero and overall programming just a bit over that :-) But I'm willing to help and learn if some more competent soul is in it. Thanks, -- Rémi
Re: [O] Sending BibTeX entries from Zotero to Org-mode via Fireforg
Hi Marko, ma...@dimjasevic.net (Marko Dimjašević) writes: I can change it to 18.0.1, and even though it installs, it reads Error in the add-on/status bar. I just guess it's due to the Org-mode version (7.6) and hopefully it works in newer versions. Crossing fingers, then. org-protocol.el is part of Org's core. Do you maybe know since what version? 2009-03-31: http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=167a7b HTH, -- Bastien
Re: [O] need: custom agenda for last 7 days
Hi Xiao-Yong, Xiao-Yong Jin jinxiaoy...@gmail.com writes: I believe you need to pass a string to =org-agenda-start-day=. (org-agenda-start-day -7) Indeed, sorry for the mistake. For this variable, =org-agenda-start-day=, give a link to the document of the function =org-read-date= would be great. I had to read through the source code to understand it. Done, thanks! -- Bastien
Re: [O] org-element
On Fri, Feb 22, 2013 at 11:38:16AM +, Achim Gratz wrote:
How is one supposed to write (longer) equations out on multiple lines (leaving
the operators behind on the previous line obviously works, but is ugly)?
I use LaTeX blocks. So your example would translate to:
#+begin_latex
\begin{equation}
r = a
+ b
- c
\end{equation}
#+begin_latex
With easy templates, entering blocks is trivial (l for LaTeX blocks).
Hope this helps,
--
Suvayu
Open source is the future. It sets us free.
Re: [O] org-sync and redmine
Hi Rémi, hob...@poukram.net (Rémi Letot) writes: So I get to ask if anyone that I'm not aware of is still currently working on org-sync, and if yes if they are interrested in fixing the redmine backend ? Daimrod is working on it and I think he is interested in the Redmine sync too. Daimrod, let me know if you want write access to org-sync.git repo on orgmode.org, you could then merge your changes directly. Aurélien, do you want to maintain org-sync or would you be okay to let Daimrod take over maintainership if Daimrod asks for it? -- Bastien
Re: [O] thank you !!
hob...@poukram.net (Rémi Letot) writes: So a big thanks to all of you: developpers, community, wizzards,... it is a real pleasure to be (even a small) part of this whole thing. Welcome! -- Bastien
Re: [O] org-element
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
I use LaTeX blocks. So your example would translate to:
#+begin_latex
\begin{equation}
r = a
+ b
- c
\end{equation}
#+begin_latex
With easy templates, entering blocks is trivial (l for LaTeX
blocks).
Of course, the next question is whether we want to force \[ .. \]
equations to be inlined (with no newline inside) or not. But I let
Nicolas ask and answer this question :)
--
Bastien
Re: [O] org-element
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Fri, Feb 22, 2013 at 11:38:16AM +, Achim Gratz wrote:
How is one supposed to write (longer) equations out on multiple lines
(leaving
the operators behind on the previous line obviously works, but is ugly)?
I use LaTeX blocks. So your example would translate to:
#+begin_latex
\begin{equation}
r = a
+ b
- c
\end{equation}
#+begin_latex
This is a bit different from what the OP is asking for. A LaTeX block
will only be exported by a latex (or derived) back-end. On the other
hand, \[1+1\] may be exported by any back-end (for example using mathjax
in html).
Anyway, the equivalent would be a LaTeX environment:
\begin{equation*}
r = a
+ b
- c
\end{equation*}
Regards,
--
Nicolas Goaziou
Re: [O] [Worg][Bug] extra ...-source.html files in Worg
Achim Gratz strom...@nexgo.de writes: Something seems to run amok when Worg gets published, if you look in the sitemap under org-tools you'll find entries for index.html, index-source.html, index-source-source.html and so on. The documents actually exist (not showing the source of course). This seems to happen in a few other places as well. I don't know since when this might have been going on. Thanks for reporting this. I removed *-source.\(orgx?|html\) files from ~/git/org-mode/ and orgmode.org/worg/. On the maint branch, you can use :htmlized-source to ask `org-publish-org-to-org' to write a index.org.html htmlized file. I think the previous implementation was to write index-source.html and my guess is that there has been a recursion problem with files written to index-source.org, then index-source-source.org, etc. I'm not entirely sure, but the problem should be gone. Also, the new exporter doesn't allow :htmlized-source anymore in publishing project, but we should fix this. -- Bastien
Re: [O] ob-doc-R-extended.org
Hi Andreas, Andreas Röhler andreas.roeh...@easy-emacs.de writes: Coming upon this tutorial, which seems excellent for beginners http://orgmode.org/worg/sources/FIXME/ob-doc-R-extended.org maybe move from FIXME into common place? It was moved to FIXME because Org could not export it correctly. Can you test whether the current maint branch is able to export it now? If so, it's safe to move it back to its original place. Thanks, -- Bastien
Re: [O] ob-doc-R-extended.org
Hi Jay, Jay Kerns gjkerns...@gmail.com writes: Unfortunately my updated draft is on my computer at home so I would have to wait until later this evening before I could share the updates. (If there's interest, of course.) There is an interest, no doubt! Please see my message to Andreas: we first need to make sure that the maint branch of Org can export it correctly. Then any update on the file is welcome -- Worg is open, just send me your public key and I'll give you write access to Worg. Thanks! -- Bastien
[O] [PATCH] Fix typo in org.texi that broke compilation
Attached
--
Suvayu
Open source is the future. It sets us free.
From 3dc825a44e37dd2b8e9ca51428b309ee26326746 Mon Sep 17 00:00:00 2001
From: Suvayu Ali fatkasuvayu+li...@gmail.com
Date: Fri, 22 Feb 2013 14:29:24 +0100
Subject: [PATCH] Fix typo in org.texi that broke compilation
---
doc/org.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/org.texi b/doc/org.texi
index 268cf67..50bb211 100644
--- a/doc/org.texi
+++ b/doc/org.texi
@@ -6562,7 +6562,7 @@ used a special setup for @file{remember.el}, then
replaced it with
@file{org-remember.el}. As of version 8.0, @file{org-remember.el} has
been completely replaced by @file{org-capture.el}.
-If your configuration depends on @fite{org-remember.el}, you need to update
+If your configuration depends on @file{org-remember.el}, you need to update
it and use the setup described below. To convert your
@code{org-remember-templates}, run the command
@example
--
1.8.1.2
Re: [O] org-element
On Fri, Feb 22, 2013 at 02:25:13PM +0100, Nicolas Goaziou wrote:
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
On Fri, Feb 22, 2013 at 11:38:16AM +, Achim Gratz wrote:
How is one supposed to write (longer) equations out on multiple lines
(leaving
the operators behind on the previous line obviously works, but is ugly)?
I use LaTeX blocks. So your example would translate to:
#+begin_latex
\begin{equation}
r = a
+ b
- c
\end{equation}
#+begin_latex
This is a bit different from what the OP is asking for. A LaTeX block
will only be exported by a latex (or derived) back-end. On the other
hand, \[1+1\] may be exported by any back-end (for example using mathjax
in html).
Ah! I did not realise that \[..\] was also interpreted by mathjax.
Thanks for pointing it out.
Anyway, the equivalent would be a LaTeX environment:
\begin{equation*}
r = a
+ b
- c
\end{equation*}
Typo on my part. :-p
Cheers,
--
Suvayu
Open source is the future. It sets us free.
[O] bug-tracker
Hi folks, when checking http://orgmode.org/worg/org-issues.html for bugs I'm hanting, couldn't find it. And really, looks very homebrewn WRT org-mode itself. What about using some of the tools around? Mirroring the stuff at github would provide a tracker just by the way... Cheers, Andreas
Re: [O] Correct / best way of loading packages in contrib when using org compiled from git?
Hi Rainer, Rainer M Krug r.m.k...@gmail.com writes: #ORG_ADD_CONTRIB = org-e-* org-md org-export # e.g. the new exporter The comment above was outdated since org-e-* files don't exist anymore. I updated it. So I would have to add ORG_ADD_CONTRIB = org-notmuch to the local.mk file This is correct and will tell Org to compile and install org-notmuch.el. But you will still have to require it in your configuration. Nevertheless, I would like to stick with a configutration which uses the normal compiled version and all configurations are in one file (emacs.org), so I would prefer the require... approach. Compiling, installing and requiring are three different things. The makefile rules take care of the first two, while your config file needs to take care of the third one in any case. If you set the load-path to include the contrib/lisp/ directory, then you don't need to install org-notmuch, and (require 'org-notmuch) will find it. If you don't want to bother setting the load-path for contrib/lisp/ then you want to install Org. In this case, org-notmuch will not be installed unless you add the ORG_ADD_CONTRIB = org-notmuch rule. But I would like to have some clarification, what the differences are between the two approaches and if (and if yes, why) it would be advisable to use the second approach. I hope the above clarifies things. I don't install Org files, I use them from the git repo and configure the require accordingly. PS: I update my git almost daily via the following script: This should be enough # #!/bin/sh cd ~/.emacs.d/org-mode-git/org-mode make update # HTH, -- Bastien
Re: [O] [PATCH] Fix typo in org.texi that broke compilation
Suvayu Ali fatkasuvayu+li...@gmail.com writes: Attached Applied, thanks, and sorry for the typo! -- Bastien
Re: [O] orgstruct-mode with custom headline prefix
Hi Stephen, Dr Stephen J Eglen sj...@cam.ac.uk writes: I just wanted to check though whether we need to set outline-regexp; No, it is not. I think this part of `org-cycle' requires outline-regexp to be set, but I just wanted to check whether this was a pre-requisite, as it then seems that we are setting two similar regexps. The outline-regexp is useful in outline-mode. In org-mode, which is derived from outline-mode, you don't want to change outline-regexp directly, but org-outline-regexp instead. orgstruct-mode is different: it relies both on the value of `orgstruct-heading-prefix-regexp' (which you need to set) and on the value of `org-outline-regexp' (which you don't need to set). HTH, -- Bastien
Re: [O] org-capture, datetree, and tags
Hi Tim, Tim Burt tcb...@rochester.rr.com writes: : (defun org-datetree-find-year-create (year) :(let ((re ^\\*+[ \t]+\\([12][0-9][0-9][0-9]\\)[ \t]*\\(:[[:alnum:]_@]*\\)*:*[ \t]*$) : match) I've tested with the following headlines: - 2013 - both with and without trailing spaces - 2013 :abc: - 2013 :abc123: - 2013 :abc123:_underscore:@attaboy:: - 2013 :noexport: Any comments on the regular expression are welcome before I make patch. Thanks for working on fixing this. The more or less standard regexp for tags-till-end-of-line is this: :[[:alnum:]_@#%:]*[ \t]*$ ^ With * if you want to match headlines with no tag. Please have a look at this page before submitting a patch: http://orgmode.org/worg/org-contribute.html#sec-5 Thanks! -- Bastien
Re: [O] [Bug] Export Coding System
Hello,
Achim Gratz strom...@nexgo.de writes:
I'm exporting an Org file in UTF-8 to LaTeX. Unless I switch the coding
system
in Emacs from default to UTF-8 (which has the side effect that any new
buffer will have UTF-8 coding, which is usually not what I want), the LaTeX
buffer gets created with ISO8859-1/latin-1 encoding (which is dead wrong,
because several characters in the document are in fact not representable in
that
encoding). Changing the option Org Export Latex Coding System to utf-8
doesn't change how the LaTeX buffer gets created, but it will then helpfully
ask
when its time to save the buffer if I want to save it as UTF-8 (no, I want it
created with UTF-8, not changed to a different encoding on save). That
salvages
a few characters, but the larger damage of \usepackage[latin1]{inputenc}
doesn't
get changed of course.
The coding system of any export buffers should by default follow the Org
buffer
they are created from and any changes to the coding system stipulated by
export
configuration must be applied before the buffer coding system gets used to
make
any decisions on how to export things.
IIUC, there is no such thing as a coding system associated to a buffer.
A coding system only kicks in when doing some I/O operation.
Anyway, with the same context described above, what's the return value
for:
(detect-coding-string (org-export-as 'latex) t)
in the buffer you want to export?
Regards,
--
Nicolas Goaziou
[O] BUG, Re: ob-doc-R-extended.org
Am 22.02.2013 14:30, schrieb Bastien: Hi Andreas, Andreas Röhler andreas.roeh...@easy-emacs.de writes: Coming upon this tutorial, which seems excellent for beginners http://orgmode.org/worg/sources/FIXME/ob-doc-R-extended.org maybe move from FIXME into common place? It was moved to FIXME because Org could not export it correctly. Can you test whether the current maint branch is able to export it now? If so, it's safe to move it back to its original place. Thanks, Okay
Re: [O] Correct / best way of loading packages in contrib when using org compiled from git?
Rainer M Krug r.m.k...@gmail.com writes: Just for clarifications: is there any problem with adding ORG_ADD_CONTRIB = * to the local.mk file, apart from slightly longer compilation times? This should be okay, but it's not safe. If any non-emacs-lisp file gets added to contrib/lisp/ (e.g. a README file) then you will try to compile non-elisp files. *\.el is safer. -- Bastien
Re: [O] Correct / best way of loading packages in contrib when using org compiled from git?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 22/02/13 14:39, Bastien wrote: Hi Rainer, Rainer M Krug r.m.k...@gmail.com writes: #ORG_ADD_CONTRIB = org-e-* org-md org-export # e.g. the new exporter The comment above was outdated since org-e-* files don't exist anymore. I updated it. Didn't realise that... So I would have to add ORG_ADD_CONTRIB = org-notmuch to the local.mk file This is correct and will tell Org to compile and install org-notmuch.el. But you will still have to require it in your configuration. Ok - that makes sense. I just checked in my contrib/lisp and I only have .el there, so none are compiled. Nevertheless, I would like to stick with a configutration which uses the normal compiled version and all configurations are in one file (emacs.org), so I would prefer the require... approach. Compiling, installing and requiring are three different things. The makefile rules take care of the first two, while your config file needs to take care of the third one in any case. Ok. If you set the load-path to include the contrib/lisp/ directory, then you don't need to install org-notmuch, and (require 'org-notmuch) will find it. Well - I don't install org, but just specify the load-path, so I have to specify that one as well. No problem. If you don't want to bother setting the load-path for contrib/lisp/ then you want to install Org. In this case, org-notmuch will not be installed unless you add the ORG_ADD_CONTRIB = org-notmuch rule. Ok - makes sense. But I would like to have some clarification, what the differences are between the two approaches and if (and if yes, why) it would be advisable to use the second approach. I hope the above clarifies things. Absolutely - thanks. I don't install Org files, I use them from the git repo and configure the require accordingly. Yes - that is what I am doing as well. Just for clarifications: is there any problem with adding ORG_ADD_CONTRIB = * to the local.mk file, apart from slightly longer compilation times? PS: I update my git almost daily via the following script: This should be enough # #!/bin/sh cd ~/.emacs.d/org-mode-git/org-mode make update # Ok - I'll change it accordingly. Thanks a lot, Rainer HTH, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJRJ3vRAAoJENvXNx4PUvmCabcH/AzwB4P8Qcu/mNBnx9rtwVgE O2jVV7skAbrjExOI2lP1JLs2K1AAzbzYMapIMpNnzpU+2ozPvP390S6C9zs7EXMs G0VRBDhOQxJyezXpeBkgdyxMxNwnPdkldvVeltMrJFEIRApe5Y2/NC7Zw6Lm+ASr p/AxnIlZODZZTwZltvA/7wx6u1ZuWyH1jlEHbmpncqZqjqiimhLl5vXt3K8y3/GG q7HDJwbDEVunWxWQZxvH7/E+QxnJV082tcKONDs8YJNaEo+7gnLiLnMUZS4sjBGi NnkjoqCaWYltHTpZbG57YbzntFr4htn3k5KjxI4sKiMqLSgCW19ykTheOSC2dCA= =TBD/ -END PGP SIGNATURE-
Re: [O] New feature: export an agenda to an Org file
Hi Robert, Robert Eckl eck...@gmx.de writes: I've committed a feature that allows you to export your agenda buffer to an Org file. It will create a new file containing the headlines of the agenda. The headlines do not contain any children they may have. Please try the feature extensively before Org 8.0. In an agenda buffer C-x C-w test.org RET I'm not sure, is it intended? Yes it is -- exporting an agenda to an .org file will collect the original headlines (with their body but without their subtrees) and put them in a new .org file. I've updated the documentation to mention this. The idea behind this feature is to be able to create *temporary* .org files for focused work, e.g., for a clean export of the agenda or for converting headlines into a plain list to print. With this focus idea in mind, adding inherited tags seemed too much, as tags are really useful for... creating agendas. Let me know if you strongly feel inherited tags should be allowed here and why. Thanks, -- Bastien
Re: [O] bug-tracker
Andreas Röhler andreas.roeh...@easy-emacs.de writes: Hi folks, Hi, What about using some of the tools around? Mirroring the stuff at github would provide a tracker just by the way... Or you use debbugs.gnu.org, which hosts the Emacs bugtracker. Some of the org bugs will arrive there anyway, from people using M-x report-emacs-bug. advertisement And there are debbugs.el and debbugs-gnu.el, which allow access to the bugs from inside Emacs. I could imagine a debbugs-org.el as well, which translates bugs into org tasks, or whatever. /advertisement Cheers, Andreas Best regards, Michael (author of debbugs.el, coauthor of debbugs-gnu.el)
Re: [O] [Bug] Export Coding System
Nicolas Goaziou n.goaziou at gmail.com writes: IIUC, there is no such thing as a coding system associated to a buffer. A coding system only kicks in when doing some I/O operation. The coding system should be associated with the file the buffer is visiting, but a fresh buffer still shows a coding system indicator in the modeline even if it is not (yet) associated with a file. That coding system always seems to be the default coding system as provided by the language environment. Anyway, with the same context described above, what's the return value for: (detect-coding-string (org-export-as 'latex) t) Depends on what language environment is set to, but with the default setting of my Emacs (German) it becomes iso-latin-1, independently of what the coding system in the original Org buffer was. I think that the export buffer coding system should be explicitly set (via buffer-file-coding-system, which is automatically buffer-local) to copy the coding of the parent buffer (or the coding specified via export options if anything like that exists) so that the default choice of the language environment doesn't kick in. Regards, Achim.
Re: [O] org-element
Suvayu Ali fatkasuvayu+linux at gmail.com writes: I use LaTeX blocks. So your example would translate to: Sure, but then the equation would only be exported for LaTeX and I would need to copy the same thing just again for HTML export. I didn't put a [Bug] tag on the OP on purpose, since I don't really know what's officially supported or not w.r.t. LaTeX fragments. But it seems that proper support of multi-line LaTeX fragments (and count this as a yes vote) then parsing needs to take into account that there can't be any Org elements inside them. Regards, Achim.
Re: [O] [Worg][Bug] extra ...-source.html files in Worg
Bastien bzg at altern.org writes: Thanks for reporting this. I removed *-source.\(orgx?|html\) files from ~/git/org-mode/ and orgmode.org/worg/. It seems that only the subdirectories of worg/ were cleaned, but not files in worg/ itself. Or maybe I need to wait longer for the sitemap to propagate the changes... Regards, Achim.
Re: [O] Correct / best way of loading packages in contrib when using org compiled from git?
Bastien bzg at altern.org writes: Just for clarifications: is there any problem with adding ORG_ADD_CONTRIB = * to the local.mk file, apart from slightly longer compilation times? This should be okay, but it's not safe. If any non-emacs-lisp file gets added to contrib/lisp/ (e.g. a README file) then you will try to compile non-elisp files. *\.el is safer. This is a globbing pattern, not a regular expression, hence: *.el, but that would also pull in htmlize which you most likely don't want, so you might follow the lead in server.mk and make that org-* or org-*.el if you are worried that the Org maintainer forgets that only lisp files should go into the lisp directory. :-) Regards, Achim.
Re: [O] [Bug] Export Coding System
Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou n.goaziou at gmail.com writes: IIUC, there is no such thing as a coding system associated to a buffer. A coding system only kicks in when doing some I/O operation. The coding system should be associated with the file the buffer is visiting, but a fresh buffer still shows a coding system indicator in the modeline even if it is not (yet) associated with a file. That coding system always seems to be the default coding system as provided by the language environment. Anyway, with the same context described above, what's the return value for: (detect-coding-string (org-export-as 'latex) t) Depends on what language environment is set to, but with the default setting of my Emacs (German) it becomes iso-latin-1, independently of what the coding system in the original Org buffer was. In this case, it should be `utf-8', shouldn't it? I think that the export buffer coding system should be explicitly set (via buffer-file-coding-system, which is automatically buffer-local) to copy the coding of the parent buffer (or the coding specified via export options if anything like that exists) so that the default choice of the language environment doesn't kick in. Still trying to understand: is the coding system wrong when you export to a file, to a (temporary) buffer, or both? Note that `org-export-to-file' use `coding-system-for-write', which overrides `buffer-file-coding-system'. So this variable is probably irrelevant here. Regards, -- Nicolas Goaziou
[O] [bug] orgstruct has suddenly become overly opinionated about legal keystrokes
I use orgstruct mode in my message mode, so that I may easily include tables and lists when writing and responding to mail. This week, I've suddenly noticed that when I press meta-RET in message mode with orgstruct mode enabled, Org-struct returns the error orgstruct-error: This key has no function outside structure elements However, orgstruct should (and used to) just pass this key combo through to the underlying major mode. This is new behavior as of the last couple of weeks. Cheers, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [Worg][Bug] extra ...-source.html files in Worg
Achim Gratz strom...@nexgo.de writes: Or maybe I need to wait longer for the sitemap to propagate the changes... That's it, I did not update sitemap.org, it will be updated by the next push. -- Bastien
Re: [O] [bug] orgstruct has suddenly become overly opinionated about legal keystrokes
Eric Schulte schulte.e...@gmail.com writes: I use orgstruct mode in my message mode, so that I may easily include tables and lists when writing and responding to mail. orgstruct-mode does not help you with tables. That is orgtbl-mode. This week, I've suddenly noticed that when I press meta-RET in message mode with orgstruct mode enabled, Org-struct returns the error orgstruct-error: This key has no function outside structure elements However, orgstruct should (and used to) just pass this key combo through to the underlying major mode. orgstruct-mode tries to but does not find an appropriate key binding. Does this patch help? (Apply and restart Emacs.) --- a/lisp/org.el +++ b/lisp/org.el @@ -8621,7 +8621,7 @@ buffer. It will also recognize item context in multiline items. (where-is-internal f outline-mode-map))) ;; TODO use local-function-key-map (dolist (rep '((tab . TAB) - (ret . RET) + (return . RET) (esc . ESC) (del . DEL))) (setq binding (read-kbd-macro (replace-regexp-in-string This is new behavior as of the last couple of weeks. That's my fault. I am sorry. Christopher
[O] Bug: org-map-entries docstring
C-h f org-map-entries RET The remaining args are treated as settings for the skipping facilities of the scanner. The following items can be given here: archiveskip trees with the archive tag. commentskip trees with the COMMENT keyword function or Emacs Lisp form: will be used as value for `org-agenda-skip-function', so whenever the function returns t, FUNC will not be called for that entry and search will continue from the ^^^ point where the function leaves it. ^^ That is wrong. Function must return a buffer position or nil. Christopher
Re: [O] thank you !!
I gotta echo this sentiment. What a great tool! :) On 02/22/2013 04:14 AM, Rémi Letot wrote: Hello org world, I have silently used org-mode for quite a while, but now comes the time when I need some help. I must say it feels a bit like the smallest shareholder taking the mic in front of a big meeting, so I figured it would be nice to first say the obvious: THANK YOU !!! I use org in part thanks to the immense flexibility of the tool, and in part thanks to the wonderfull sharing habit in the community. Org is such a flexible beast that it can be daunting for a newcomer to start using it. But thanks to that sharing habit, getting things done with org has just been a matter of finding the wizzards who work mostly like I do and have shared their configuration. I just then had to tweak the small bits to make it fell like home. So a big thanks to all of you: developpers, community, wizzards,... it is a real pleasure to be (even a small) part of this whole thing. Thanks for reading, now I can ask my questions in the next message :-) -- Andrew M. Nuxoll Phone: 503-943-7688 Asst Professor of Computer Science Fax: 503-943-7316 University of Portland - MSC #145Email: nux...@up.edu 5000 N. Willamette Blvd Web: http://faculty.up.edu/nuxoll Portland, OR 97203-5798 Office: Shiley Hall Rm 217
[O] [new exporter] 2 questions
I'm checking out the new exporter. After some configuration and file
changes it works now, could be worse.
http://article.gmane.org/gmane.emacs.orgmode/65574 says:
The `org-special-blocks.el' library, which has been moved to “contrib/”,
is obsolete since its features are included in the new export
framework.
The features are included, does this mean special block should work
``out of the box''? If so something like this
#+begin_multicols {2}
#+end_multicols
should work in LaTeX export (as it did flawlessly with the previous
exporter); - but it fails.
How do I invoke org-info.js now? `#+INFOJS_OPT:' does not work as
expected so it must be obsolete, no?
--
henry, web: http://literaturlatenight.de
[O] Bug: :sitemap-file-entry-format export incorrectly [7.9.3e (7.9.3e-dist @ /usr/share/emacs/site-lisp/org/)]
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See http://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org-mode mailing list. When I use `org-publish-current-project` to generate a sitemap with `:sitemap-file-entry-format %d %t` option, the sitemap.org looks like this: ``` #+TITLE: Sitemap for project blog + [[file:sample.org][2013-02-22 sample.org]] ``` then it will be exported to sitemap.html, incorrectly, looks like this: ``` ul li[[file:sample.org] span class=timestamp-wrapper span class=timestamp2013-02-22 sample.org/span/span] /li /ul ``` If I set `:sitemap-file-entry-format %t %d`, it will be correct. Emacs : GNU Emacs 24.2.1 (i686-pc-linux-gnu, GTK+ Version 2.24.14) of 2013-01-22 on localhost Package: Org-mode version 7.9.3e (7.9.3e-dist @ /usr/share/emacs/site-lisp/org/)
Re: [O] [bug] orgstruct has suddenly become overly opinionated about legal keystrokes
orgstruct-mode tries to but does not find an appropriate key binding. Does this patch help? (Apply and restart Emacs.) Yes this fixes the problem. --- a/lisp/org.el +++ b/lisp/org.el @@ -8621,7 +8621,7 @@ buffer. It will also recognize item context in multiline items. (where-is-internal f outline-mode-map))) ;; TODO use local-function-key-map (dolist (rep '((tab . TAB) - (ret . RET) + (return . RET) (esc . ESC) (del . DEL))) (setq binding (read-kbd-macro (replace-regexp-in-string This is new behavior as of the last couple of weeks. That's my fault. I am sorry. No problem, thanks for the quick fix! Christopher -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] [bug] orgstruct has suddenly become overly opinionated about legal keystrokes
Eric Schulte schulte.e...@gmail.com writes: Yes this fixes the problem. Thank you. I committed this. 14df16d org.el: Use longest form when translating keys. Christopher
Re: [O] [new exporter] 2 questions
Hello,
henry atting s...@online.de writes:
The features are included, does this mean special block should work
``out of the box''? If so something like this
#+begin_multicols {2}
#+end_multicols
should work in LaTeX export (as it did flawlessly with the previous
exporter); - but it fails.
Try:
#+attr_latex: :options {2}
#+begin_multicols
...
#+end_multicols
How do I invoke org-info.js now? `#+INFOJS_OPT:' does not work as
expected so it must be obsolete, no?
Be sure to (require 'ox-infojs)
There should be some completion for #+INFOJS_OPT keyword with M-TAB.
Regards,
--
Nicolas Goaziou
Re: [O] [new exporter] 2 questions
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Try:
#+attr_latex: :options {2}
#+begin_multicols
...
#+end_multicols
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
It works here. Difficult to say what is wrong in your buffer without
more context.
Be sure to (require 'ox-infojs)
This works fine but the correct spelling is (require 'ox-jsinfo)
Actually, library ox-jsinfo.el provides both symbols.
Regards,
--
Nicolas Goaziou
Re: [O] bug-tracker
Am 22.02.2013 15:52, schrieb Michael Albinus: Andreas Röhler andreas.roeh...@easy-emacs.de writes: Hi folks, Hi, What about using some of the tools around? Mirroring the stuff at github would provide a tracker just by the way... Or you use debbugs.gnu.org, which hosts the Emacs bugtracker. Some of the org bugs will arrive there anyway, from people using M-x report-emacs-bug. advertisement And there are debbugs.el and debbugs-gnu.el, which allow access to the bugs from inside Emacs. I could imagine a debbugs-org.el as well, which translates bugs into org tasks, or whatever. /advertisement Cheers, Andreas Best regards, Michael (author of debbugs.el, coauthor of debbugs-gnu.el) Fine for me. With exception of the noise, M-x report-emacs-bugs tends to send. Herewith is a slim version, adapted to org-mode AFAIU (defun report-org-mode-bug (topic optional recent-keys) Report a bug in GNU Emacs. Prompts for bug subject. Leaves you in a mail buffer. ;; This strange form ensures that (recent-keys) is the value before ;; the bug subject string is read. (interactive (reverse (list (recent-keys) (concat org-mode; (read-string Bug Subject: ) ;; The syntax `version;' is preferred to `[version]' because the ;; latter could be mistakenly stripped by mailing software. (if (eq system-type 'ms-dos) (setq topic (concat emacs-version ; topic)) (when (string-match ^\\(\\([.0-9]+\\)*\\)\\.[0-9]+$ emacs-version) (setq topic (concat (match-string 1 emacs-version) ; topic (let ((from-buffer (current-buffer)) ;; Put these properties on semantically-void text. ;; report-emacs-bug-hook deletes these regions before sending. (prompt-properties '(field emacsbug-prompt intangible but-helpful rear-nonsticky t)) (can-insert-mail (or (report-emacs-bug-can-use-xdg-email) (report-emacs-bug-can-use-osx-open))) user-point message-end-point) (setq message-end-point (with-current-buffer (get-buffer-create *Messages*) (point-max-marker))) (compose-mail report-emacs-bug-address topic) ;; The rest of this does not execute if the user was asked to ;; confirm and said no. (when (eq major-mode 'message-mode) ;; Message-mode sorts the headers before sending. We sort now so ;; that report-emacs-bug-orig-text remains valid. (Bug#5178) (message-sort-headers) ;; Stop message-mode stealing the properties we will add. (set (make-local-variable 'message-strip-special-text-properties) nil)) (rfc822-goto-eoh) (forward-line 1) ;; Move the mail signature to the proper place. (let ((signature (buffer-substring (point) (point-max))) (inhibit-read-only t)) (delete-region (point) (point-max)) (insert signature) (backward-char (length signature))) ;; (with-help-window *help-org-mode-bug* (insert (concat Please describe exactly what actions triggered the bug, and\n ;; the precise symptoms of the bug. If you can, give a recipe\n ;; starting from `emacs -Q':\n\n ;; ;; If Emacs crashed, and you have the Emacs process in the gdb debugger,\n ;; please include the output from the following gdb commands:\n ;; `bt full' and `xbacktrace'.\n ;; ))) ;; (let ((debug-file (expand-file-name DEBUG data-directory))) ;; (if (file-readable-p debug-file) ;; (insert For information about debugging Emacs, please read the file\n ;; debug-file .\n) ;; )) (add-text-properties (save-excursion (rfc822-goto-eoh) (line-beginning-position 2)) (point) prompt-properties) (setq user-point (point)) (insert \n\n) (add-text-properties (1+ user-point) (point) prompt-properties) (insert \n\nIn (emacs-version) \n) (when (and (boundp 'emacs-bzr-version)(stringp emacs-bzr-version)) (insert Bzr revision: emacs-bzr-version \n)) (insert \n) (insert (format Major mode: %s\n (format-mode-line (buffer-local-value 'mode-name from-buffer) nil nil from-buffer))) (insert \n) ;; This is so the user has to type something in order to send easily. (use-local-map (nconc (make-sparse-keymap) (current-local-map))) (define-key (current-local-map) \C-c\C-i 'info-emacs-bug) (if can-insert-mail (define-key (current-local-map) \C-cm 'report-emacs-bug-insert-to-mailer)) (setq report-emacs-bug-send-command (get mail-user-agent 'sendfunc) report-emacs-bug-send-hook (get mail-user-agent 'hookvar)) (if report-emacs-bug-send-command (setq report-emacs-bug-send-command (symbol-name report-emacs-bug-send-command))) (unless report-emacs-bug-no-explanations (with-output-to-temp-buffer *Bug Help*
Re: [O] bug-tracker
Hello Andreas, (I like the idea of having a function to scan user setup for org) On Feb 23 2013, Andreas Röhler andreas.roeh...@easy-emacs.de wrote: Herewith is a slim version, adapted to org-mode AFAIU Tried to test, I got an error., ╭─ │or: Symbol's function definition is void: report-emacs-bug-can-use-xdg-email ╰─ Thanks., -- ఎందరో మహానుభావులు అందరికి వందనములు. YYR
Re: [O] bug-tracker
Michael Albinus writes: Andreas Röhler andreas.roeh...@easy-emacs.de writes: What about using some of the tools around? Mirroring the stuff at github would provide a tracker just by the way... Or you use debbugs.gnu.org, which hosts the Emacs bugtracker. Some of the org bugs will arrive there anyway, from people using M-x report-emacs-bug. Is it OK to report bugs for upstream/development versions through `report-emacs-bugs', though? I always thought this should only be used for stuff that's actually bundled with Emacs (what about bugs in org/contrib, for instance?). -David
Re: [O] bug-tracker
Andreas Röhler andreas.roeh...@easy-emacs.de writes: With exception of the noise, M-x report-emacs-bugs tends to send. Herewith is a slim version, adapted to org-mode AFAIU Why do you want to code all the nasty bits yourself? There is `reporter-submit-bug-report' of reporter.el, which you could customize to your needs. Compare, how Tramp uses it in `tramp-bug' (Ha! another advertisement!). Best regards, Michael.
Re: [O] [new exporter] 2 questions
henry atting s...@online.de writes:
Here is a minimal example. I use lualatex as tex engine.
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
#+LaTeX_HEADER: \usepackage{fontspec}
#+attr_latex: :options {2}
#+begin_multicols
* Lorem ipsum
[...]
You can't have a headline within a block.
Regards,
--
Nicolas Goaziou
Re: [O] bug-tracker
David Engster d...@randomsample.de writes: Is it OK to report bugs for upstream/development versions through `report-emacs-bugs', though? I always thought this should only be used for stuff that's actually bundled with Emacs (what about bugs in org/contrib, for instance?). debbugs.gnu.org is not only for Emacs. See http://debbugs.gnu.org/db/ix/packages.html which other projects are hosted there. gnus is a prominent example for a subpackage of Emacs with an own bug package using debbugs.gnu.org. An alternative approach is tagging bugs of a project with your package name. See existing user tags of project emacs at http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=usertag;user=emacs. cedet uses this mechanism already. And shame on me, Tramp doesn't use debbugs.gnu.org (yet). -David Best regards, Michael.
Re: [O] [Feature Request] Cross headings in tables
Carsten Dominik writes: I think the cleanest way to implement this would be to _not_ modify Org syntax, because it is export back-end very specific. Something like: #+attr_html: :header-groups (1 3) | This | will | | be| a header | |---+---| | This | won't | |---+---| | This will | be too| |---+---| | This | won't too | I really like this approach, to mark the header groups in an attribute - maybe an backend-independent attribute? I can see the appeal from a programmers' point of view, but from a user perspective this is extremely obscure, especially if that table spans a few pages and has many such extra header rows (hey, why not ask the user to write the table in XML to start with?). In any case, the current way of dealing with headers in org-element and the exporters doesn't admit either. The reason why I prefer this approach is that I am weary of new syntax in Org-mode that will take up new characters of character chains. For the case of tables, if I could go back, I would even remove some of the syntax I introduced, for example for defining the values of constants - that should have been an attribute-link thing as well. Probably even row and column naming, could have been done in this way. Hindsight is 20/20. :-) But going this route takes us even further from Your life in plain text. towards Your life in another programming language. because you will need a special viewer or editor to make sense of it for all but the most trivial cases. 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] [new exporter] 2 questions
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Here is a minimal example. I use lualatex as tex engine.
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
#+LaTeX_HEADER: \usepackage{fontspec}
#+attr_latex: :options {2}
#+begin_multicols
* Lorem ipsum
[...]
You can't have a headline within a block.
Regards,
Thanks.
Then the consequence is that I have to edit the .tex file manually which
I did not have to do with the previous exporter.
Or you may use:
#+latex: \begin{multicols}{2}
* Headline
#+latex: \end{multicols}
Regards,
--
Nicolas Goaziou
Re: [O] bug-tracker
Michael Albinus writes: David Engster d...@randomsample.de writes: Is it OK to report bugs for upstream/development versions through `report-emacs-bugs', though? I always thought this should only be used for stuff that's actually bundled with Emacs (what about bugs in org/contrib, for instance?). debbugs.gnu.org is not only for Emacs. See http://debbugs.gnu.org/db/ix/packages.html which other projects are hosted there. gnus is a prominent example for a subpackage of Emacs with an own bug package using debbugs.gnu.org. An alternative approach is tagging bugs of a project with your package name. See existing user tags of project emacs at http://debbugs.gnu.org/cgi/pkgindex.cgi?indexon=usertag;user=emacs. cedet uses this mechanism already. I know. I'm the guy who started using those tags for CEDET. :-) I was always under the impression that those tags are merely a way for, well, tagging bugs, so that you can search for them. Same for packages. I didn't know that this also implied that you're encouraged to report bugs against upstream packages, possibly for features which are not yet in Emacs (or may even never land there, like some stuff in org/contrib, cedet/contrib, etc.). -David
Re: [O] org-export-babel-evaluate and :exports none
Nicolas Goaziou writes: I'm just starting over because that wasn't a correct solution. I'm not even sure about what bug this patch fixed. The bug was that Babel blocks were evaluated during export when org-export-babel-evaluate was explicitly set to nil (the default value is t). Anyway, it isn't org-export-babel-evaluate's job to tell when to evaluate a source code block. The documentation says that its job is exactly that, if the context is export. --8---cut here---start-8--- Documentation: Switch controlling code evaluation during export. When set to nil no code will be evaluated as part of the export process. --8---cut here---end---8--- It may be org-babel-exp-process-buffer's. You call org-export-execute-babel-code however, which doesn't check the above variable. BTW, the function org-export-execute-babel-code is called before it is being defined. Not sure why this doesn't give a warning. Why should it? It's not a macro, after all. Ah yes. To much C++ the last month. 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] bug-tracker
On Fri, Feb 22, 2013 at 08:56:54PM +0100, Andreas Röhler wrote: With exception of the noise, M-x report-emacs-bugs tends to send. Herewith is a slim version, adapted to org-mode AFAIU [...] Org already uses one of its own: org-submit-bug-report -- Suvayu Open source is the future. It sets us free.
Re: [O] [Feature Request] Cross headings in tables
On 22.2.2013, at 21:33, Achim Gratz strom...@nexgo.de wrote: Carsten Dominik writes: I think the cleanest way to implement this would be to _not_ modify Org syntax, because it is export back-end very specific. Something like: #+attr_html: :header-groups (1 3) | This | will | | be| a header | |---+---| | This | won't | |---+---| | This will | be too| |---+---| | This | won't too | I really like this approach, to mark the header groups in an attribute - maybe an backend-independent attribute? I can see the appeal from a programmers' point of view, but from a user perspective this is extremely obscure, especially if that table spans a few pages and has many such extra header rows (hey, why not ask the user to write the table in XML to start with?). In any case, the current way of dealing with headers in org-element and the exporters doesn't admit either. The reason why I prefer this approach is that I am weary of new syntax in Org-mode that will take up new characters of character chains. For the case of tables, if I could go back, I would even remove some of the syntax I introduced, for example for defining the values of constants - that should have been an attribute-link thing as well. Probably even row and column naming, could have been done in this way. Hindsight is 20/20. :-) But going this route takes us even further from Your life in plain text. towards Your life in another programming language. because you will need a special viewer or editor to make sense of it for all but the most trivial cases. Point taken. - Carsten 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] bug-tracker
Am 22.02.2013 21:50, schrieb Suvayu Ali: On Fri, Feb 22, 2013 at 08:56:54PM +0100, Andreas Röhler wrote: With exception of the noise, M-x report-emacs-bugs tends to send. Herewith is a slim version, adapted to org-mode AFAIU [...] Org already uses one of its own: org-submit-bug-report Ah, and it collects some useful org-mode stuff. So it remains to combine that collection with posting onto the tracker. ?
[O] [texinfo] Appendix?
Aloha all, I can't find a way to have the texinfo exporter start an appendix. * Last chapter blah blah * Appendix 1 blah blah This will yield something like this: 15 Last chapter --- blah blah 16 Appendix 1 - blah blah When I would instead like: A Appendix 1 Assuming I'm not missing something, perhaps an attribute? #+attr_texinfo :appendix t All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] Correct / best way of loading packages in contrib when using org compiled from git?
Rainer M Krug writes: Ok - that makes sense. I just checked in my contrib/lisp and I only have .el there, so none are compiled. Look in lisp, not contrib/lisp. If you set the load-path to include the contrib/lisp/ directory, then you don't need to install org-notmuch, and (require 'org-notmuch) will find it. Well - I don't install org, but just specify the load-path, so I have to specify that one as well. No problem. No, you don't want that if you use ORG_ADD_CONTRIB. Yes - that is what I am doing as well. Just curious, what would change for you if you installed Org into a user directory (besides using make up2 instead of make update)? Just for clarifications: is there any problem with adding ORG_ADD_CONTRIB = * to the local.mk file, apart from slightly longer compilation times? Yes, you don't want all of contrib (htmlize.el in particular). PS: I update my git almost daily via the following script: This should be enough Actually, the git checkout master at the beginning should probably stay there as a defensive measure. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Terratec KOMPLEXER: http://Synth.Stromeko.net/Downloads.html#KomplexerWaves
Re: [O] bug-tracker
Am 22.02.2013 21:09, schrieb Michael Albinus: Andreas Röhler andreas.roeh...@easy-emacs.de writes: With exception of the noise, M-x report-emacs-bugs tends to send. Herewith is a slim version, adapted to org-mode AFAIU Why do you want to code all the nasty bits yourself? Really not eager for that, as there are a lot of interesting things to do. BTW didn't much more deleting lines... There is `reporter-submit-bug-report' of reporter.el, which you could customize to your needs. Compare, how Tramp uses it in `tramp-bug' (Ha! another advertisement!). Hmm, maybe you are fastest just to copy a version with org-mode in the slots. That may replace org-submit-bug-report, if Bastien and the others agree. Andreas Best regards, Michael.
Re: [O] [Bug] Export Coding System
Nicolas Goaziou writes: Depends on what language environment is set to, but with the default setting of my Emacs (German) it becomes iso-latin-1, independently of what the coding system in the original Org buffer was. In this case, it should be `utf-8', shouldn't it? I want it to be utf-8, but it isn't. The course of events is apparently that when a new buffer gets created it will have the default coding system. You are then apparently asking that buffer for the coding system (always the default) and set inputenc accordingly, but should have asked the parent Org buffer. Or so I think, a few details are probably still wrong. I think that the export buffer coding system should be explicitly set (via buffer-file-coding-system, which is automatically buffer-local) to copy the coding of the parent buffer (or the coding specified via export options if anything like that exists) so that the default choice of the language environment doesn't kick in. Still trying to understand: is the coding system wrong when you export to a file, to a (temporary) buffer, or both? Both. Note that `org-export-to-file' use `coding-system-for-write', which overrides `buffer-file-coding-system'. So this variable is probably irrelevant here. No it is not irrelevant, it simply gets set too late in the game: it asks for the new coding system when it is time to save the buffer, while the content of the buffer has been cobbled together while assuming a different coding system. The only way I know (from browsing the documentation) to override the coding system for a buffer that does not yet have a file association is to set that variable directly, preferrably directly after the buffer is created. 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] [new exporter] 2 questions
Hi Nicolas,
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
henry atting s...@online.de writes:
The features are included, does this mean special block should work
``out of the box''? If so something like this
#+begin_multicols {2}
#+end_multicols
should work in LaTeX export (as it did flawlessly with the previous
exporter); - but it fails.
Try:
#+attr_latex: :options {2}
#+begin_multicols
...
#+end_multicols
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
How do I invoke org-info.js now? `#+INFOJS_OPT:' does not work as
expected so it must be obsolete, no?
Be sure to (require 'ox-infojs)
This works fine but the correct spelling is (require 'ox-jsinfo)
There should be some completion for #+INFOJS_OPT keyword with M-TAB.
Regards,
Thanks,
--
henry atts, web: http://literaturlatenight.de
Re: [O] [new exporter] 2 questions
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Here is a minimal example. I use lualatex as tex engine.
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
#+LaTeX_HEADER: \usepackage{fontspec}
#+attr_latex: :options {2}
#+begin_multicols
* Lorem ipsum
[...]
You can't have a headline within a block.
Regards,
Thanks.
Then the consequence is that I have to edit the .tex file manually which
I did not have to do with the previous exporter.
--
henry atts, web: http://literaturlatenight.de
Re: [O] [new exporter] 2 questions
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
Try:
#+attr_latex: :options {2}
#+begin_multicols
...
#+end_multicols
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
It works here. Difficult to say what is wrong in your buffer without
more context.
Here is a minimal example. I use lualatex as tex engine.
--8---cut here---start-8---
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
#+LaTeX_HEADER: \usepackage{fontspec}
#+attr_latex: :options {2}
#+begin_multicols
* Lorem ipsum
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Donec a diam
lectus. Sed sit amet ipsum mauris. Maecenas congue ligula ac quam
viverra nec consectetur ante hendrerit. Donec et mollis dolor.
Praesent et diam eget libero egestas mattis sit amet vitae augue. Nam
tincidunt congue enim, ut porta lorem lacinia consectetur. Donec ut
libero sed arcu vehicula ultricies a non tortor.
begreift.
#+end_multicols
--8---cut here---end---8---
Be sure to (require 'ox-infojs)
This works fine but the correct spelling is (require 'ox-jsinfo)
Actually, library ox-jsinfo.el provides both symbols.
Regards,
Thanks,
--
henry atts, web: http://literaturlatenight.de
Re: [O] [new exporter] 2 questions
Nicolas Goaziou writes:
It creates this command in the .tex file:
\#+begin$_\mathrm{multicols}$
It works here. Difficult to say what is wrong in your buffer without
more context.
That result looks exactly like my problem with multiline \[...\],
i.e. the parser found something it considers an element inside the
multicols block and that made the block itself look like random text
that needs to be escaped.
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] ob-doc-R-extended.org
Am 22.02.2013 14:31, schrieb Bastien: Hi Jay, Jay Kerns gjkerns...@gmail.com writes: Unfortunately my updated draft is on my computer at home so I would have to wait until later this evening before I could share the updates. (If there's interest, of course.) There is an interest, no doubt! Please see my message to Andreas: we first need to make sure that the maint branch of Org can export it correctly. Then any update on the file is welcome -- Worg is open, just send me your public key and I'll give you write access to Worg. Thanks! Hi Bastien, IMHO it would be great if Jay moves it already at place. As it's a doku basically, giving a nice entry into a lot of things. If exporting is not perfect yet, it's not at the core here, we may fix it step by step. Also we might gather bug-reports that way. Agreed? Maybe I'm mistaking something... Cheers, Andreas
Re: [O] org-export-babel-evaluate and :exports none
On Fri, Feb 22, 2013 at 3:49 PM, Achim Gratz strom...@nexgo.de wrote: Nicolas Goaziou writes: I'm just starting over because that wasn't a correct solution. I'm not even sure about what bug this patch fixed. The bug was that Babel blocks were evaluated during export when org-export-babel-evaluate was explicitly set to nil (the default value is t). FWIW, I have not experienced this bug. I always set org-export-babel-evaluate to nil, and this has always had the desired effect of preventing babel evaluation on export. Best, Ista Anyway, it isn't org-export-babel-evaluate's job to tell when to evaluate a source code block. The documentation says that its job is exactly that, if the context is export. --8---cut here---start-8--- Documentation: Switch controlling code evaluation during export. When set to nil no code will be evaluated as part of the export process. --8---cut here---end---8--- It may be org-babel-exp-process-buffer's. You call org-export-execute-babel-code however, which doesn't check the above variable. BTW, the function org-export-execute-babel-code is called before it is being defined. Not sure why this doesn't give a warning. Why should it? It's not a macro, after all. Ah yes. To much C++ the last month. 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
[O] Can I refile into a journal with file+datetree?
Hello Org wizards, I use org-capture with file+datetree for keeping a journal which works fine. I also use mobile-org to take notes while I'm on the go. After syncing them back I'd like to refile them into my journal with an appropriate date attached. Mobile org doesn't record the date I took the note so I'd just have all entries collected under the date I refile. Is there a way to do that? Thanks, Martin
Re: [O] ob-doc-R-extended.org
Andreas Röhler writes: IMHO it would be great if Jay moves it already at place. As it's a doku basically, giving a nice entry into a lot of things. If exporting is not perfect yet, it's not at the core here, we may fix it step by step. Also we might gather bug-reports that way. The thing with Worg is that it is auto-published to HTML whenever a change is pushed, so if something doesn't export cleanly, it will break all of Worg. So, if the document does in fact export without error to HTML with the latest maint version of Org it could be moved, otherwise not. 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] ob-doc-R-extended.org
Am 22.02.2013 22:58, schrieb Achim Gratz: Andreas Röhler writes: IMHO it would be great if Jay moves it already at place. As it's a doku basically, giving a nice entry into a lot of things. If exporting is not perfect yet, it's not at the core here, we may fix it step by step. Also we might gather bug-reports that way. The thing with Worg is that it is auto-published to HTML whenever a change is pushed, so if something doesn't export cleanly, it will break all of Worg. So, if the document does in fact export without error to HTML with the latest maint version of Org it could be moved, otherwise not. Regards, Achim. Ahh, thanks for the explanation, Andreas
Re: [O] [texinfo] Appendix?
Hello Tom On 22 February 2013 16:15, Thomas S. Dye t...@tsdye.com wrote: Aloha all, I can't find a way to have the texinfo exporter start an appendix. * Last chapter blah blah * Appendix 1 blah blah This will yield something like this: 15 Last chapter --- blah blah 16 Appendix 1 - blah blah When I would instead like: A Appendix 1 Assuming I'm not missing something, perhaps an attribute? Appendixes should work as unnumbered headlines. I don't remember testing for that use specifically although there is a possible work-around that will allow for unnumbered headlines for sure. Indexes are always unnumbered, so using a property :INDEX: will produce an unnumbered headline. If you want it to insert one of the default indexes you set the property to the appropriate key: cp , fn , ky , pg , tp , vr Regards, Jon -- #+attr_texinfo :appendix t All the best, Tom -- T.S. Dye Colleagues, Archaeologists 735 Bishop St, Suite 315, Honolulu, HI 96813 Tel: 808-529-0866, Fax: 808-529-0884 http://www.tsdye.com
Re: [O] [Bug] Export Coding System
Achim Gratz strom...@nexgo.de writes: Nicolas Goaziou writes: Depends on what language environment is set to, but with the default setting of my Emacs (German) it becomes iso-latin-1, independently of what the coding system in the original Org buffer was. In this case, it should be `utf-8', shouldn't it? I want it to be utf-8, but it isn't. The course of events is apparently that when a new buffer gets created it will have the default coding system. You are then apparently asking that buffer for the coding system (always the default) and set inputenc accordingly, but should have asked the parent Org buffer. Or so I think, a few details are probably still wrong. I think that the export buffer coding system should be explicitly set (via buffer-file-coding-system, which is automatically buffer-local) to copy the coding of the parent buffer (or the coding specified via export options if anything like that exists) so that the default choice of the language environment doesn't kick in. Still trying to understand: is the coding system wrong when you export to a file, to a (temporary) buffer, or both? Both. Note that `org-export-to-file' use `coding-system-for-write', which overrides `buffer-file-coding-system'. So this variable is probably irrelevant here. No it is not irrelevant, it simply gets set too late in the game: it asks for the new coding system when it is time to save the buffer, while the content of the buffer has been cobbled together while assuming a different coding system. The only way I know (from browsing the documentation) to override the coding system for a buffer that does not yet have a file association is to set that variable directly, preferrably directly after the buffer is created. Does the following patch fix the problem? Regards, -- Nicolas Goaziou From ed16f38854c197e8b31607bd32622d00e47fe10c Mon Sep 17 00:00:00 2001 From: Nicolas Goaziou n.goaz...@gmail.com Date: Fri, 22 Feb 2013 23:07:04 +0100 Subject: [PATCH] ox: Fix coding system error * lisp/ox.el (org-export--generate-copy-script): Clone `buffer-file-coding-system' when creating a buffer copy. This patches makes sure the output will share the same encoding as the original buffer. --- lisp/ox.el | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/lisp/ox.el b/lisp/ox.el index efce29d..65e5acd 100644 --- a/lisp/ox.el +++ b/lisp/ox.el @@ -2729,10 +2729,13 @@ another buffer, effectively cloning the original buffer there. (val (cdr entry))) (and (not (eq var 'org-font-lock-keywords)) (or (memq var - '(major-mode default-directory - buffer-file-name outline-level - outline-regexp - buffer-invisibility-spec)) + '(major-mode + default-directory + buffer-file-name + buffer-file-coding-system + outline-level + outline-regexp + buffer-invisibility-spec)) (string-match ^\\(org-\\|orgtbl-\\) (symbol-name var))) ;; Skip unreadable values, as they cannot be -- 1.8.1.4
[O] Bug: New HTML exporter incorrect attributes
Hello, Where attributes have been assigned to an image in a paragraph, the new exporter applies those attributes to both the image and a following link. For example, this: #+BEGIN_SRC org #+ATTR_HTML: width=10 alt= [Cool thing] [[file:cool_thing.jpg]] Cool thing found here [[http://example.com/][example.com]]. #+END_SRC is exported to this: #+BEGIN_HTML p img src=cool_thing.jpg width=10 alt= [Cool thing] / Cool thing found here a href=http://example.com/; width=10 alt= [Cool thing] example.com/a. /p #+END_HTML Emacs : GNU Emacs 24.3.50.1 (i686-pc-linux-gnu, GTK+ Version 3.6.0) of 2012-12-24 on menkib, modified by Debian Package: Org-mode version 7.9.3e (7.9.3e-1173-g14df16 @ /home/tftorrey/.emacs.d/elisp/org/lisp/) Best regards, Terry -- T.F. Torrey
Re: [O] bug-tracker
Am 22.02.2013 21:10, schrieb Yagnesh Raghava Yakkala: Hello Andreas, (I like the idea of having a function to scan user setup for org) On Feb 23 2013, Andreas Röhler andreas.roeh...@easy-emacs.de wrote: Herewith is a slim version, adapted to org-mode AFAIU Tried to test, I got an error., ╭─ │or: Symbol's function definition is void: report-emacs-bug-can-use-xdg-email ╰─ Thanks., Used emacs from trunk, commenting out that section should work. Best, Andreas
Re: [O] [new exporter] 2 questions
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Nicolas Goaziou n.goaz...@gmail.com writes:
henry atting s...@online.de writes:
Here is a minimal example. I use lualatex as tex engine.
#+TITLE: lorem ipsum
#+LANGUAGE: de
#+LaTeX_CLASS: scrartcl
#+LaTeX_CLASS_OPTIONS: [DIV=8,a4paper]
#+LaTeX_HEADER: \usepackage{fontspec}
#+attr_latex: :options {2}
#+begin_multicols
* Lorem ipsum
[...]
You can't have a headline within a block.
Regards,
Thanks.
Then the consequence is that I have to edit the .tex file manually which
I did not have to do with the previous exporter.
Or you may use:
#+latex: \begin{multicols}{2}
* Headline
#+latex: \end{multicols}
Regards,
Great! Thanks again.
--
henry atts, web: http://literaturlatenight.de
[O] Footnote following a bold sentence
Hi Orgers, I need to have a footnote following a bold sentence, exported to html. This example: *The issuing bank must honour a credit when there is a complying presentation of documents.*[fn:117] exports to: *The issuing bank must honour a credit when there is a complying presentation of documents.*129 I would rather not have a space between the * and the [fn:117]. Is this a bug or expected behaviour? Thanks, Alan -- Alan L Tyreehttp://www2.austlii.edu.au/~alan Tel: 04 2748 6206 sip:172...@iptel.org
Re: [O] [texinfo] Appendix?
Aloha Jon, Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes: Hello Tom Appendixes should work as unnumbered headlines. I don't remember testing for that use specifically although there is a possible work-around that will allow for unnumbered headlines for sure. Indexes are always unnumbered, so using a property :INDEX: will produce an unnumbered headline. If you want it to insert one of the default indexes you set the property to the appropriate key: cp , fn , ky , pg , tp , vr I don't understand. This: * Concept index :PROPERTIES: :TEXINFO_MENU_TITLE: Concept Index :INDEX:cp :END: Gives me a numbered headline and an empty section. If I add this: @@info:@printindex cp@@ then an index is generated. The headline is still numbered. Am I doing something wrong? All the best, Tom -- Thomas S. Dye http://www.tsdye.com
Re: [O] Bug: New HTML exporter incorrect attributes
Hello, tftor...@tftorrey.com (T.F. Torrey) writes: Where attributes have been assigned to an image in a paragraph, the new exporter applies those attributes to both the image and a following link. You don't assign attributes to an image in a paragraph, you assign attributes to the paragraph itself. For the time being, Org syntax doesn't allow to specify attributes per link object. As a consequence, attributes will be assigned to every link within the paragraph. A hack could be implemented in ox-html.el so only image links get these attributes, but it would be the same with multiple images within the same paragraph. A proper solution to the problem would be to slightly change link syntax. Until then, you'll have to use workarounds (like, for example, writing the other link in raw HTML syntax within an export snippet). Regards, -- Nicolas Goaziou
Re: [O] Footnote following a bold sentence
Hello, Alan L Tyree alanty...@gmail.com writes: I need to have a footnote following a bold sentence, exported to html. This example: *The issuing bank must honour a credit when there is a complying presentation of documents.*[fn:117] exports to: *The issuing bank must honour a credit when there is a complying presentation of documents.*129 I would rather not have a space between the * and the [fn:117]. Is this a bug or expected behaviour? It is to be expected. By default, opening square bracket is not allowed as a character following emphasis marker. Tweak `org-emphasis-regexp-components' to solve this. Regards, -- Nicolas Goaziou
Re: [O] (no subject) How to sort agenda by timestamps (scheduled/deadline)?
Bastien bzg at altern.org writes: Hi Martin and Bernt, the master branch now have new sorting strategies: timestamp-up Sort by any timestamp, early first timestamp-down Sort by any timestamp, late first scheduled-up Sort by scheduled timestamp, early first scheduled-down Sort by scheduled timestamp, late first deadline-upSort by deadline timestamp, early first deadline-down Sort by deadline timestamp, late first ts-up Sort by active timestamp, early first ts-downSort by active timestamp, late first tsia-upSort by inactive timestamp, early first tsia-down Sort by inactive timestamp, late first Please have a try and let me know if this works as expected. Thanks both for your input on this, Hi Bastien, thanks a lot for your help and for your effort (and sorry for my late reply)!! I would love to test this, but I first have to manage to install the latest version. I've found the FAQ. I'll try to install it, test it and then get back to you with a feedback how it works as soon as I can. Kind regards Martin
Re: [O] [texinfo] Appendix?
Hello Tom On 22 February 2013 17:55, Thomas S. Dye t...@tsdye.com wrote: Aloha Jon, Jonathan Leech-Pepin jonathan.leechpe...@gmail.com writes: Hello Tom Appendixes should work as unnumbered headlines. I don't remember testing for that use specifically although there is a possible work-around that will allow for unnumbered headlines for sure. Indexes are always unnumbered, so using a property :INDEX: will produce an unnumbered headline. If you want it to insert one of the default indexes you set the property to the appropriate key: cp , fn , ky , pg , tp , vr I don't understand. This: * Concept index :PROPERTIES: :TEXINFO_MENU_TITLE: Concept Index :INDEX:cp :END: Gives me a numbered headline and an empty section. If I add this: @@info:@printindex cp@@ then an index is generated. The headline is still numbered. Am I doing something wrong? I don't think so. From the looks of things, index wasn't fixed along with other properties to be uppercase in ox-texinfo.el. I should be able to fix it on Monday (and make sure it now works), along with the spacing of the detailed node listing. Regards, Jon All the best, Tom -- Thomas S. Dye http://www.tsdye.com
[O] ox-texinfo.el copyright
The head of ox-texinfo.el says , | ;;; ox-texinfo.el --- Texinfo Back-End for Org Export Engine | | ;; Copyright (C) 2012, 2013 Jonathan Leech-Pepin | ;; Author: Jonathan Leech-Pepin jonathan.leechpepin at gmail dot com | ;; Keywords: outlines, hypermedia, calendar, wp | ;; | ;; This file is not part of GNU Emacs. ` Presumably that should be changed before too long (as in: before the next release)? There are a few more: org-colview-xemacs.el:;; This file is part of Org mode, it is not part of GNU Emacs. ox-odt.el:;; This file is not part of GNU Emacs. ox-publish.el:;; This file is not part of GNU Emacs. ox-texinfo.el:;; This file is not part of GNU Emacs. Nick
Re: [O] ob-doc-R-extended.org
On Fri, Feb 22, 2013 at 5:04 PM, Andreas Röhler andreas.roeh...@easy-emacs.de wrote: Am 22.02.2013 22:58, schrieb Achim Gratz: Andreas Röhler writes: IMHO it would be great if Jay moves it already at place. As it's a doku basically, giving a nice entry into a lot of things. If exporting is not perfect yet, it's not at the core here, we may fix it step by step. Also we might gather bug-reports that way. The thing with Worg is that it is auto-published to HTML whenever a change is pushed, so if something doesn't export cleanly, it will break all of Worg. So, if the document does in fact export without error to HTML with the latest maint version of Org it could be moved, otherwise not. Regards, Achim. Ahh, thanks for the explanation, Andreas Hmm... thanks for the heads-up, Achim. I usually work on the master branch and I haven't actually checked that what I did is compatible with the maint branch. I will checkout the maint branch and make sure everything exports smoothly. -- Jay
Re: [O] ob-doc-R-extended.org
On Fri, Feb 22, 2013 at 8:49 PM, Jay Kerns gjkerns...@gmail.com wrote: Hmm... thanks for the heads-up, Achim. I usually work on the master branch and I haven't actually checked that what I did is compatible with the maint branch. I will checkout the maint branch and make sure everything exports smoothly. -- Jay Alright, here goes: it looks like the maint branch does not yet include the new exporter (ox-latex.el and such). The whole point of my working on this to begin with was to get something compatible with the new exporter, so rather than go back all over again to make something work with something that's set to be outdated in the coming months (weeks?) anyway, I'd rather sit tight on the work done so far and patiently look forward to the new exporter's merge from master to maint. In the meantime, the latest updated draft (little more than some tweaks of Erik Iverson's original work) is here: https://github.com/gjkerns/org-mode-R-tutorial I've confirmed just now that it successfully exports to PDF/HTML under the new exporter based on a freshly pulled org from git mere minutes ago. There's still work to be done, and I welcome suggestions/corrections in the balance of time between now and when some rendition of this can safely land on Worg. Regards, Jay
Re: [O] footnotes export verbatim
On 2/21/13, Eric S Fraga e.fr...@ucl.ac.uk wrote: Even \par fails to work now. :( This last bit would be disturbing if true. However, on my system at least, \par in the middle of an inline footnote *does* lead to the start of a new paragraph within the footnote when exported to latex/pdf. Did you try HTML?
Re: [O] org-meta-return
42 147 aeuster at gmail.com writes: [continues off-topic] Have you tried a Dvorak keyboard? A friend of mine ridicules me for being a QWERTY typist, but I have found no empirical evidence that it is actually superior. At best, it has been proven, in /some/ studies, to be /slightly/ superior; and from a cost-benefit standpoint, /slight/ superiority according to /some/ studies (and I should add, only at extreme speeds), is not worth relearning how to type. FWIW, and I'm well aware this is purely anecdotal evidence with a sample size of 1, after I switched to Dvorak some years ago, the difference in the amount of strain and fatigue I felt in my fingers and wrists was (and still is) more than slight. I know it's still the case because I have my customized Dvorak layout in Linux (it's basically a mirror image, but slightly different from left-handed Dvorak), but I never figured out how to replicate it in Windows 7. I don't have to use win7 often, just for teaching some Windows-only software, so it hasn't been worth digging through Microsoft documents. I've actually gotten a fair amount of QWERTY speed back, but boy, I can sure feel how much more *work* it is. The muscle movements flow in Dvorak, and they don't in QWERTY (not surprising, since QWERTY's purpose was to slow typists down and prevent the machinery from jamming). I can believe that studies would find only a slight /speed/ improvement, but we aren't talking about speed. We're talking about RSI pain. I'd at least question the relevance of words/minute studies to measure reduction in muscle effort. Studies of finger travel are more on point. The cost of relearning to type is high, but the cost is temporary and the benefits last the rest of your life. Just my experience. hjh
Re: [O] bug-tracker
David Engster d...@randomsample.de writes: I was always under the impression that those tags are merely a way for, well, tagging bugs, so that you can search for them. Same for packages. I didn't know that this also implied that you're encouraged to report bugs against upstream packages, possibly for features which are not yet in Emacs (or may even never land there, like some stuff in org/contrib, cedet/contrib, etc.). This must be discussed with the Emacs maintainers, of course. If org error reports will contain a substantial part of non-core Emacs problems, an own debbugs package org might be better. Reports arriving via the Emacs report chain could be reassigned to both packages emacs,org then. I recommend to contact Glenn Morris. -David Best regards, Michael.
Re: [O] bug-tracker
Andreas Röhler andreas.roeh...@easy-emacs.de writes: There is `reporter-submit-bug-report' of reporter.el, which you could customize to your needs. Compare, how Tramp uses it in `tramp-bug' (Ha! another advertisement!). Hmm, maybe you are fastest just to copy a version with org-mode in the slots. That may replace org-submit-bug-report, if Bastien and the others agree. I believe it is better written by org maintainers. They know much better which kind of information is needed. Andreas Best regards, Michael.
