Jambunathan K writes:
> My proposal and patch to always use utf-8 stands annulled then.
Okay. I guess we shall go with the workaround solution for
ox-freemind.el, then. Can you provide a patch for this?
Thanks!
--
Bastien
Hi Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> Alan Schmitt writes:
>
>> Rasmus writes:
>>
>>> Export the following to LaTeX:
>>>
>>> #+BEGIN_SRC Org
>>> #+TITLE:test
>>> #+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
>>> #+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a t
Hi Dexter,
Dexter Rodriguez writes:
> Each time I try to org-publish-project RET the debugger produces this
> error
> Can you help?
Please update to the latest release, it has been fixed there.
Thanks,
--
Bastien
Hi Rick,
please check against the latest ox-html.el, I updated it yesterday
with some modifications in this area, fixing typos and reintroducing
`org-html-head-extra'.
(I'm in a rush right now and need to leave.)
Thanks in advance,
--
Bastien
To: emacs-orgmode@gnu.org
Subject: Bug: org-publishing error [7.9.3e (7.9.3e-7-g1056fc-elpa @
c:/home/.emacs.d/elpa/org-20130211/)]
--text follows this line--
Each time I try to org-publish-project RET the debugger produces this error
Can you help?
Thanks
Dexter
--
Hi,
Although I enforced a staring value of the ordered list inside
unordered list, the list in exported PDF starts from 1.
I attached an example file. When it is exported to PDF, numbering of
the ordered list would be incorrect.
Here is my output of org-submit-bug-report.
Emacs : GNU Emacs 24.2
Hi Rick,
Rick Frankel writes:
> * ox-deck.el (org-deck--get-packages): Check for non-blank deck-theme
> and deck-transition.
Applied, thanks.
Do you want direct commit access? If so, please send me your public
key and I'll add you!
Thanks for your help,
--
Bastien
Hi James,
James Harkins writes:
> After a recent update, I noticed that the agenda buffer now moves the
> displayed text when you change an item's TODO state using 't'.
Fixed, thanks!
--
Bastien
Hi, Org people. Here is my (short) weekly status on the colorg project!
This weekend either, I did not have much time to push on colorg. Yet, I
got the inner guts of a test generator, using a fresh colorg server for
each test. Starting and stopping colorg servers in quick succession
showed late
>
> I do confirm.
Thank you. I have been trying to migrate to the new-exporter. I have
not had much success so far but I hope to be able to figure it all out
soon. Since we do not yet have a documentation, it is difficult.
Nicolas has been very kind with help.
I have a website that is built usi
On Mar 4, 2013 1:24 AM, "Nicolas Goaziou" wrote:
> Try
>
> :BEAMER_opt: t
>
> property.
Worked perfectly, thanks! Eventually I'll be able to generalize these
little tidbits on my own.
hjh
Robert Horn writes:
> Achim Gratz writes:
>
>> Jambunathan K writes:
>>> Always use utf-8 for HTML export (No support for other coding systems).
>>>
>>> For or against. Please register your views.
>>
>> It is becoming more rare these days, but still possible that the
>> document encoding cannot
G'day Orgers,
Problem 1: definition lists when exported to HTML, ODT or ASCII look
just like they do in the ort-mode file. Shouldn't they be "fixed up"
somehow?
Problem 2: I need to export footnotes that are not Org footnotes. They
look like this:
1. This is footnote one
2. This is footnote two
Just +1 on incorporating Julia. @Eric, babel is amazing. I am developing on it
and I can't wait to use it with my students. Thanks to both of you.
On Sun, Mar 3, 2013 at 5:27 PM, Jay Kerns wrote:
> Dear Eric,
>
> On Sun, Mar 3, 2013 at 2:05 PM, Eric Schulte wrote:
>> Hi Jay,
>>
>> Having read
* ox-deck.el (org-deck--get-packages): Check for non-blank deck-theme
and deck-transition.
---
contrib/lisp/ox-deck.el | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/contrib/lisp/ox-deck.el b/contrib/lisp/ox-deck.el
index 5d25369..23cc3ab 100644
--- a/contri
Bastien-
On Sat, Mar 02, 2013 at 07:14:07PM +0100, Bastien wrote:
> Done. You can now use HTML_HEAD instead of HTML_STYLE.
>
> Some variables were also renamed, check the details here:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=2752ef
In trying to migrate these changes to the slide e
Jambunathan K 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
Hi Ryo,
Ryo TAKAISHI writes:
> * lisp/org-protocol.el: (org-protocol-convert-query-to-plist): New function.
> (org-protocol-do-capture): Use new function.
> (org-protocol-data-separator): Change default separator.
Applied, thanks a lot!
--
Bastien
* lisp/org-protocol.el: (org-protocol-convert-query-to-plist): New function.
(org-protocol-do-capture): Use new function.
(org-protocol-data-separator): Change default separator.
When org-protocol's url has query, org-capture get query using plist-get from
store-link.
For example:
Url is "org-pro
Achim Gratz writes:
> Jambunathan K writes:
>> Always use utf-8 for HTML export (No support for other coding systems).
>>
>> For or against. Please register your views.
>
> It is becoming more rare these days, but still possible that the
> document encoding cannot be UTF-8 for whatever reason.
Dear Eric,
On Sun, Mar 3, 2013 at 2:05 PM, Eric Schulte wrote:
> Hi Jay,
>
> Having read through intro-julia.org and scanned ob-julia.el I have to
> say this looks great. Thanks for sharing!
I should be saying "Thanks" to you! Org Babel is truly great work; I
use it almost every day of my life
Achim Gratz writes:
> Neuwirth Erich writes:
>>
>> 4 unexpected results:
>>FAILED test-org-table/references/format-specifier-E
>>FAILED test-org-table/references/format-specifier-EL
>>FAILED test-org-table/references/format-specifier-L
>>FAILED test-org-table/references/format
Jambunathan K writes:
> Jambunathan K writes:
>
>> Nicolas Goaziou writes:
>>
>>> Bastien writes:
>>>
Achim Gratz writes:
> It also requires that the HTML is output in UTF-8. I would
> (reluctantly, I don't really know much about how this would work)
> suggest that the
Hello,
Andreas Leha writes:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> Hi Vikas,
>>>
>>> François Allisson writes:
>>>
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/oldexp during the process of
migration t
Nicolas Goaziou writes:
> Bastien writes:
>
>> Hi Vikas,
>>
>> François Allisson writes:
>>
>>> org-exp-bibtex, because of its dependency on the old exporter, was first
>>> moved from contrib/lisp to contrib/oldexp during the process of
>>> migration towards org new exporter. And yesterday, the
Nagarjuna G writes:
> I am not sure if it effects our project. We use org and Emacs for
> post-processing our wiki pages to produce html pages. Currently we are
> getting proper exports since we get the output in utf-8. As far as I
> know, using utf-8 will support other coding systems as well. Am I
Neuwirth Erich writes:
>
> 4 unexpected results:
>FAILED test-org-table/references/format-specifier-E
>FAILED test-org-table/references/format-specifier-EL
>FAILED test-org-table/references/format-specifier-L
>FAILED test-org-table/references/format-specifier-none
I've reported
Hi Jay,
Having read through intro-julia.org and scanned ob-julia.el I have to
say this looks great. Thanks for sharing!
Would you be willing to contribute ob-julia.el to the Org-mode
repository? I don't see you listed as an Org-mode contributor (see
[1]), so to do so you would likely have to co
On Sun, Mar 3, 2013 at 11:58 PM, Achim Gratz wrote:
> Jambunathan K writes:
> > Always use utf-8 for HTML export (No support for other coding systems).
> >
> > For or against. Please register your views.
>
>
I am not sure if it effects our project. We use org and Emacs for
post-processing our
Jambunathan K writes:
> Always use utf-8 for HTML export (No support for other coding systems).
>
> For or against. Please register your views.
It is becoming more rare these days, but still possible that the
document encoding cannot be UTF-8 for whatever reason. So if it's not
unduly complicati
Jambunathan K writes:
> In short, the concern you have raised is more cosmetic than
> functional.
I trust you. The thing is, I have this small incertainty in my
mind on whether there is something functional involved here or not.
Also, IIUC the change is triggered only because ox-freemind.el ne
Hello,
Simon Thum writes:
> I have scripted an ical export that invokes:
>
> org-icalendar-combine-agenda-files
>
> but the thing fails on my server and home boxes. I investigated and
> found that a misguided babel block I added in a hurry and forgot about
> was causing trouble:
>
> #+BEGIN_SR
Good day!
So, I tried giving org-contacts another go.
For capturing new contacts, I have this template configured (based on
the example on org-contacts.el):
#+begin_src elisp
(add-to-list 'org-capture-templates
'("c" "Contacts" entry (file "~/org/contacts.org")
"
Always use utf-8 for HTML export (No support for other coding systems).
For or against. Please register your views.
--
Emacs : GNU Emacs 23.3.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.5)
of 2011-08-14 on allspice, modified by Debian
Package: Org-mode version 7.9.3d (7.9.3d-dist @
/home/myth/.emacs-lisp/org/lisp/)
To reproduce:
In an org agenda buffer, mark a task as done. Then, run org-agenda-undo.
If the t
Bastien writes:
> Also, the change in ox-html.el is not good IMHO: it will populate
> everyone's HTML code with unfamiliar strings (like " " instead
> of " ") just for the sake of keeping ox-freemind.el users happy.
How many people are going to read HTML code? There is correctness and
there is
Jambunathan K writes:
> ps: I have a feeling that `org-html-display-buffer-mode' is superfluous.
> A simple `set-auto-mode' will do the trick.
Indeed, I applied a patch using `set-auto-mode'.
Thanks for the suggestion!
--
Bastien
Hi,
I'm pleased to announce that with commit b06735aa85506e04f9b2e agneda
performance is back to lighting-fast and the agenda works with
birthdays. Thanks a lot!
On 03/03/2013 05:50 PM, Bastien wrote:
Hi Simon,
Simon Thum writes:
I tried a lot of stuff and this is triggering it for me:
(
Hello,
Alan Schmitt writes:
> Rasmus writes:
>
>> Export the following to LaTeX:
>>
>> #+BEGIN_SRC Org
>> #+TITLE:test
>> #+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
>> #+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
>> #+LATEX_HEADER:\newcommand{tttest}{\textsc{p
On 03/03/2013 05:54 PM, Bastien wrote:
Hi Simon,
Simon Thum writes:
this breaks my setup.
I've removed the check when org-agenda-write is called
non-interactively. Please let me know if this fixes your
setup.
Thanks,
Works like a charm!
Thank you very much!
Hello,
James Harkins writes:
> According to beameruserguide.pdf, I can give an option "t" to a
> columns environment to align the columns by the top line of text. It's
> not clear to me how to put this into org.
>
> So far, I have:
>
> *** Columns
Bastien writes:
> Hi Vikas,
>
> François Allisson writes:
>
>> org-exp-bibtex, because of its dependency on the old exporter, was first
>> moved from contrib/lisp to contrib/oldexp during the process of
>> migration towards org new exporter. And yesterday, the directory
>> contrib/oldexp was eve
Hi Vikas,
François Allisson writes:
> org-exp-bibtex, because of its dependency on the old exporter, was first
> moved from contrib/lisp to contrib/oldexp during the process of
> migration towards org new exporter. And yesterday, the directory
> contrib/oldexp was eventually removed[1].
Yes. W
Hi Sean,
"Sean O'Halpin" writes:
> Also, it's just struck me - wouldn't it be more consistent if
> ATTR_HTML were HTML_ATTR, ATTR_LATEX were LATEX_ATTR, etc.?
I don't really think so -- ATTR_HTML is more like BEGIN_HTML than
#+HTML_HEAD, which is a global option, not a local setting or an
envir
Hi David,
David Naumann writes:
> What I would like to be able to do is insert a new heading at the same
> level as current, _following_ all the others. For example, with the
> cursor on the A in this tree:
>
> * top
> -> ** A
> ** B
> ** C
> * next
>
> I would like to insert a
Hi Nick and John,
Nick Dokos writes:
> So the heuristic might not be perfect, but it seems to work for
> all but the first headline.
I fixed this and the heuristic should not insert undue blank lines
anymore. Thanks for confirming,
--
Bastien
Hi Nicolas,
I have scripted an ical export that invokes:
org-icalendar-combine-agenda-files
but the thing fails on my server and home boxes. I investigated and
found that a misguided babel block I added in a hurry and forgot about
was causing trouble:
#+BEGIN_SRC xml
#+END_SRC
It seems th
Hi Simon,
Simon Thum writes:
> this breaks my setup.
I've removed the check when org-agenda-write is called
non-interactively. Please let me know if this fixes your
setup.
Thanks,
--
Bastien
Hi Rüdiger,
Rüdiger Sonderfeld writes:
> * contrib/lisp/org-contacts.el: Add defvar for date. Similar to org.el.
>
> (org-contacts-anniversaries): Setting date to nil breaks the
> function. Bug was introduced in e4cebbe40.
Applied, thanks a lot.
--
Bastien
Hi Simon,
Simon Thum writes:
> I tried a lot of stuff and this is triggering it for me:
> (setq org-highest-priority ?B)
> (setq org-lowest-priority ?D)
> (setq org-default-priority ?D)
>
> However, this seems just a factor. Removing it works but is undesirable for
> me, and re-adding it in an o
Jambunathan K writes:
> Nicolas Goaziou writes:
>
>> Bastien writes:
>>
>>> Achim Gratz writes:
>>>
It also requires that the HTML is output in UTF-8. I would
(reluctantly, I don't really know much about how this would work)
suggest that the export should always be done with sy
Dear Bastien,
On 03/01/2013 03:07 PM, Bastien wrote:
Hi Rainer,
Rainer Stengele writes:
How can I stop org-agenda-write from overwriting existing files?
Should we consider to introduce an option instead of advising the
function?
You are now asked before overwriting the file, thanks for sug
Rasmus writes:
> Export the following to LaTeX:
>
> #+BEGIN_SRC Org
> #+TITLE:test
> #+LATEX_HEADER:\newcommand{test}{\textsc{ps}:this is a test}
> #+LATEX_HEADER:\newcommand{ttest}{\textsc{ps}\:this is a test}
> #+LATEX_HEADER:\newcommand{tttest}{\textsc{ps}\\:this is a test}
> #+LATEX_HEADER:\ne
Ahh, crap. Sorry to have spread confusion. The issues persit - except
for the last one (4). I probably defected to the emacs org which
miraculousy had 2 secs agenda generation time, not 16.
I removed the built-in one to avoid future confusion, but cannot dig
deeper now.
Cheers,
Simon
On
Nicolas Goaziou writes:
> Bastien writes:
>
>> Achim Gratz writes:
>>
>>> It also requires that the HTML is output in UTF-8. I would
>>> (reluctantly, I don't really know much about how this would work)
>>> suggest that the export should always be done with symbolic entities and
>>> a post-exp
Hi Bastien,
I tried to reproduce using -q and had another error occurring in
customizing the agenda (hard to reproduce agenda problem with a blank list):
apropos-parse-pattern: Wrong type argument: stringp
occurs when using the search button. This is emacs org, from
GNU Emacs 24.2.1 (x86_64-
* contrib/lisp/org-contacts.el: Add defvar for date. Similar to org.el.
(org-contacts-anniversaries): Setting date to nil breaks the
function. Bug was introduced in e4cebbe40.
Signed-off-by: Rüdiger Sonderfeld
---
contrib/lisp/org-contacts.el | 4 ++--
1 file changed, 2 insertions(+), 2 d
Hello,
Maybe you've heard about the relatively new language, "julia" [1]?
The ESS team added support for it some months back [2] and they've
been working on it more recently even [3]. It seemed natural to
investigate Babel support for julia and after quite a bit of fiddling
with ob-R.el I believe
I am using OSX 10.8.2 and Emacs 2.24.1
I am trying to build org-mode from the current version in git, and I get the
following errors:
Ran 423 tests, 419 results as expected, 4 unexpected (2013-03-03 13:23:56+0100)
5 expected failures
4 unexpected results:
FAILED test-org-table/references/for
Torsten Wagner writes:
> I didn't follow this thread in detail. But shouldn't it be enough to symlink
> e.g. org-icalendar against ox-icalendar. As far as I understood emacs would
> prioritize those local symlinks over the system wide installation. This would
> be a temporary solution until a new e
On Sat, Mar 2, 2013 at 6:14 PM, Bastien wrote:
> Hi Sean,
>
> "Sean O'Halpin" writes:
>
>> One small point: as we're going to have to change the meta directive
>> "#+STYLE" to "#+HTML_STYLE", can we change the name to reflect what it
>> really does in the HTML backend, i.e. insert text verbatim i
Hi Bastien,
I didn't follow this thread in detail. But shouldn't it be enough to symlink
e.g. org-icalendar against ox-icalendar. As far as I understood emacs would
prioritize those local symlinks over the system wide installation. This would
be a temporary solution until a new emacs release
Michael Brand writes:
> Hi John
>
> On Feb 21, 2013 10:16 PM, "42 147" wrote:
>> [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 ha
Le dimanche 3 mars 2013 à 08h06, Vikas Rawal a écrit:
> org-exp-bibtex seems to have gone missing from git repository. Can
> somebody confirm pleae.
>
> Vikas
Dear Vikas,
I do confirm.
org-exp-bibtex, because of its dependency on the old exporter, was first
moved from contrib/lisp to contrib/ol
Hi John
On Sun, Mar 3, 2013 at 12:59 AM, 42 147 wrote:
> That said, were you a QWERTY user before you transitioned into Colemak?
Yes.
Michael
Hello,
Nathaniel Cunningham writes:
> Alright, I solved my own problem.
> I was able to get verbatim working with a unicode symbol (√) as delimeter,
> by editing both org-emphasis-alist and org-export-latex-emphasis-alist.
> Cheers!
FYI, modifying `org-emphasis-alist' will not be compatible wit
Bastien writes:
> Achim Gratz writes:
>
>> It also requires that the HTML is output in UTF-8. I would
>> (reluctantly, I don't really know much about how this would work)
>> suggest that the export should always be done with symbolic entities and
>> a post-export filter should then replace them
Vikas Rawal writes:
>> > I have been trying to figure out how to do this. I saw Suvayu's config
>> > files which he has kindly kept on github
>> > (https://github.com/suvayu/.emacs.d).
>> >
>> > I tried to evaluate the following lines
>> >
>> > (add-to-list 'org-latex-classes
>> > '
Achim Gratz writes:
> It also requires that the HTML is output in UTF-8. I would
> (reluctantly, I don't really know much about how this would work)
> suggest that the export should always be done with symbolic entities and
> a post-export filter should then replace them with whatever the
> part
Achim Gratz writes:
> Bastien writes:
>> What maximum size is it now? What maximum size would you like?
>
> Only the list admin can see that setting.
Yes -- I'm asking what James wants to ask the list admins if they
think it would be a sensible default and if they can implement it.
--
Bastie
Bastien writes:
> What maximum size is it now? What maximum size would you like?
Only the list admin can see that setting. But the standard
configuration is to send the digest at fixed intervals with no size cap,
IIRC.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda X
Bastien writes:
> Also, the change in ox-html.el is not good IMHO: it will populate
> everyone's HTML code with unfamiliar strings (like " " instead
> of " ") just for the sake of keeping ox-freemind.el users happy.
It also requires that the HTML is output in UTF-8. I would
(reluctantly, I don't
72 matches
Mail list logo
