I see following errors.
Saving file /home/kjambunathan/src/worg/dev/org-export-reference.texi...
Wrote /home/kjambunathan/src/worg/dev/org-export-reference.texi
Processing Texinfo file ./org-export-reference.texi ...
/home/kjambunathan/src/worg/dev/org-export-reference.texi:3117: Misplaced {.
/ho
On 03/10/2013 12:23 AM, Eric Schulte wrote:
> Mats Kindahl writes:
>
>> Hi all,
>>
>> I find the PlantUML support very useful to generate diagrams when
>> presenting designs, but unfortunately, I quite frequently have to send
>> simple descriptions requiring ASCII only. Since PlantUML support
>>
Hello,
Jambunathan K writes:
> Please consider adding the Org spec (and also the exporter reference)
> document to the Org manual.
>
> This will be a good excuse for exercising the TexInfo exporter and see
> where it leads.
>
> Committing to Org or Worg has same load cycle. I feel there is more
Samuel Wales writes:
> On 3/6/13, Bastien wrote:
>> Hello Jambunathan,
>>
>> You are not welcome on this list anymore, please ban yourself.
>>
>> Thanks,
>
> Thank you, Bastien. This has been necessary since around May of 2011.
> How do we make it a reality NOW?
I said I want to be banned. L
On 3/6/13, Bastien wrote:
> Hello Jambunathan,
>
> You are not welcome on this list anymore, please ban yourself.
>
> Thanks,
Thank you, Bastien. This has been necessary since around May of 2011.
How do we make it a reality NOW?
Samuel Wales
--
The Kafka Pandemic: http://thekafkapandemic.blo
Samuel Wales writes:
> On 3/9/13, Jambunathan K wrote:
>> I am sure Samuel will remind us infinitely if we forget about it.
>
>> Unless you say why it is confusing, I would count the above statement as
>> just mis-information and not a fact that other parties could agree with.
>
> You promised t
On 3/9/13, Jambunathan K wrote:
> I am sure Samuel will remind us infinitely if we forget about it.
> Unless you say why it is confusing, I would count the above statement as
> just mis-information and not a fact that other parties could agree with.
You promised to leave:
On 2/12/13, Jambunatha
Nicolas
>> Do you mind if I fix some obvious typos directly on Worg or do you'd
>> rather want patches?
>
> Please go ahead. This is on Worg so anyone can improve it.
Please consider adding the Org spec (and also the exporter reference)
document to the Org manual.
This will be a good excuse for
Jambunathan K writes:
>> They output a table, which looks IMO very confusing in both w3m and
>> Firefox. The old exporter worked fine. The solution IMO is to remove
>> the table tags.
I don't think footnotes export are confusing. I have seen people using
it and not complain about it.
Unless
Samuel Wales writes:
> On 2/27/13, Samuel Wales wrote:
>> On 2/13/13, Nicolas Goaziou wrote:
>>> Anyway, if you send the correct HTML that should be generated, I will
>>> fix it.
>>
>> Probably all that needs to be done is to not use a table. I tested this by
>> manually removingand their
Aloha all,
I'm not sure how this happened, but chapter 2 of orgmanual now has all
the macros replaced by their expansions. You can see this here:
https://github.com/tsdye/orgmanual/blob/master/orgmanual.org
Please don't ask for an ECM!
All the best,
Tom
--
T.S. Dye & Colleagues, Archaeologis
I'm working with an sqlite database of songs, and I've run into trouble
with titles that start with a '(' (for example,
(I Can't Get No) Satisfaction). 'Verbatim' results work:
#+BEGIN_SRC sqlite :db test-db :results verbatim
.mode csv
.separator |
drop table playlist;
create t
Without this patch (when I am _byte-compiling_ org-contacts.el), I am
getting error messages like this (when attempting address completion via
`completion-at-point' and `org-contacts-message-complete-function'):
Symbol's function definition is void: remove-duplicates
Symbol's function defi
On 6 December 2012 19:43, Brian van den Broek
wrote:
>
> On 6 Dec 2012 13:46, "Samuel Wales" wrote:
>>
>> Has anybody encountered ellipses instead of the first line of the window?
>>
>> On 8/21/12, Samuel Wales wrote:
>> > === beginning of window
>> > ...
>> > *** Above all
>> > Above all, i
On 2/27/13, Samuel Wales wrote:
> On 2/13/13, Nicolas Goaziou wrote:
>> Anyway, if you send the correct HTML that should be generated, I will
>> fix it.
>
> Probably all that needs to be done is to not use a table. I tested this by
> manually removingand their closing tags.
I am referring t
On 10/03/13 02:11, Carsten Dominik wrote:
On 9.3.2013, at 16:02, Achim Gratz wrote:
Carsten Dominik writes:
I am wondering, are we required to include the full text of the GFDL
in the manual? I find it a big waste of space and feed that a link
should do. But I have not been able to find th
Hi Bastien and others,
I remember someone (maybe Bastien) putting in a safeguard quite sometime
back that would unfold a headline with a warning when you tried to edit
near the ellipses. This was to protect against accidental edits. I see
this not there anymore, can we have it back?
I tried loo
Achim Gratz writes:
> Thomas S. Dye writes:
>> The orgmanual now creates a pdf file, too, but one lacking the indexes
>> and with links that look like they need another run through TeX.
>
> In that case, texi2dvi and hence make should have signaled an error
> (I've just pulled from your repo and
Hello,
Achim Gratz writes:
> Do you mind if I fix some obvious typos directly on Worg or do you'd
> rather want patches?
Please go ahead. This is on Worg so anyone can improve it.
> Nicolas Goaziou writes:
>> A core concept in this syntax is that only headlines and sections are
>> context-free
Mats Kindahl writes:
> Hi all,
>
> I find the PlantUML support very useful to generate diagrams when
> presenting designs, but unfortunately, I quite frequently have to send
> simple descriptions requiring ASCII only. Since PlantUML support
> generation of ASCII-art diagrams, I updated the org ba
Torsten Wagner writes:
> I plan to create new course materials for teaching at university level.
slightly OT, but you could have a look at LaTeX package
,--
| http://www.ctan.org/pkg/tcolorbox
`--
and its manual
,
Hello,
Achim Gratz writes:
> Done in commit 4f7d514f13. The double hyphens have been omitted based
> on a discussion with Eric Schulte.
Applied to ox.el in commit 69c617c.
Thank you.
Regards,
--
Nicolas Goaziou
Hi Nicolas,
here are my first comments. I'm still trying to wrap my head around some
things, so if I'm off the map on something, please be patient.
Do you mind if I fix some obvious typos directly on Worg or do you'd
rather want patches?
Nicolas Goaziou writes:
> A core concept in this syntax i
Based on discussion with Nicolas Goaziou and Eric Schulte, this patch
has been refactored and reimplemented as a patch series. Eric Schulte
has contributed additional improvements. The functionality is now in
Org.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Bl
Hi,
I plan to create new course materials for teaching at university level.
These materials should contain
- a printable course script
- an interactive web-course
- lecture slides
- exercises
- exams
I'm looking for a system which enables me to keep all materials together
and to reuse as much as
Nicolas Goaziou writes:
> I will wait for this patch to be committed.
Done in commit 4f7d514f13. The double hyphens have been omitted based
on a discussion with Eric Schulte.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles
Hi all,
I find the PlantUML support very useful to generate diagrams when
presenting designs, but unfortunately, I quite frequently have to send
simple descriptions requiring ASCII only. Since PlantUML support
generation of ASCII-art diagrams, I updated the org babel PlantUML
support to generate A
Hello,
Aaron Ecay writes:
> I think this patch is a welcome simplification. Would it be possible to
> merge the code that is used for reading babel header args (things like
> “:results output :file foo.txt”) with the code from the exporter?
It is probably possible, but that's way beyond the sc
>>
>> As I understand this particular case, the OP is using a hash not to mark
>> a result as up to date, but rather to mark a side effect (loading data
>> into R) as having taken place. I think this is a misuse of a cache.
>
> It depends on whether one looks at a cache as “a place to store resul
Eric Schulte writes:
> Ah, my fault for not completely reading and understanding your previous
> post. I'm currently working on a set of patches with Achim which should
> (I believe) resolve this issue.
It doesn't yet, but I#ll add another patch to rename this binding.
IIRC, the naming was so tha
Hi Nicolas,
I think this patch is a welcome simplification. Would it be possible to
merge the code that is used for reading babel header args (things like
“:results output :file foo.txt”) with the code from the exporter?
Unless they are parsed by the same code, the two syntaxes will differ in
sub
2013ko martxoak 9an, Eric Schulte-ek idatzi zuen:
> A hash marks a *result* with an indication of what was used to generate
> it (code block & parameters). The point of a hash is to allow the
> result to be returned without having to re-execute. For this reason, I
> think that the hash should liv
2013ko martxoak 9an, Eric Schulte-ek idatzi zuen:
> Maybe a better solution would be to add a feature to avoid echoing
> very large results to the minibuffer. It should be very
> straightforward to add a user customizable variable (e.g.,
> `org-babel-max-echo-length' or somesuch) which limits the
Achim Gratz writes:
> Eric Schulte writes:
>> I prefer leaving the hash with the results, as it is the results which
>> are "hashed". Also, same input does not always guarantee same output,
>> e.g.,
>>
>> #+begin_src sh
>> date
>> #+end_src
>
> That's not what I'm seeing, but I may be missing
aarone...@gmail.com writes:
> 2013ko martxoak 8an, Eric Schulte-ek idatzi zuen:
>>
>> I would agree. I don't believe *any* changes should take place in the
>> buffer when a code block is executed with ":results none".
>
> A common use case for me is to use a babel block to load a large dataset
>
Aaron and Nicolas,
Nicolas Goaziou writes:
> Hello,
>
> aarone...@gmail.com writes:
>
>> I think the following patch (on top of current master) will fix the
>> problem:
>
> [...]
>
> It does. Thank you.
>
Works here now. Thanks!
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
Hi there,
Does anybody know how to export deadline or schedule items from org to
ical ?
thanks
M
Alan Schmitt writes:
> Looking at it there seems to be occurrences of '++' that are a bit
> strange. Was it garbled when attached?
Ooops, I forgot to finalise my merge.
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -8658,7 +8658,7 @@ If WITH-CASE is non-nil, the sorting will be case-sensitive."
;; comm
Rick
I have my reservations in applying this patch - I am not concerned about
the patch, I have not looked at it.
Any improvements to existing backends should invariably answer the
question - "Can this change improve export tools or the parse tree
syntax."
If such a question is never asked and
Christopher Schmidt writes:
> Alan, here is patch for master that should solve the issue. It disables
> org-{pr,de}mote and org-{,shift}meta{left,right} in orgstruct-mode iff
> orgstruct-heading-prefix-regexp is non-nil. Could you please give it a
> try and tell us what you think?
Thanks a lot.
Jambunathan K writes:
>
> I am not clear about:
>
> 1. How multiple keys are to be handled.
> 2. What prenotes or postnotes mean.
> 3. Chicago note style etc.
>
>
> I think the community should answer and articulate 1, 2, 3 clearly.
> With my proposal, there could be some minor changes in Footnot
On Sat, Mar 09, 2013 at 10:32:11AM +0100, Bastien wrote:
> Hi Rick,
> One thing you may double-check in the meantime is: is it
> compatible with the org-info.js utility? The default should
> be "yes", even if users can replace "div" by something else
> (e.g. for the needs of specific backends.)
On 9.3.2013, at 16:25, Achim Gratz wrote:
> Carsten Dominik writes:
>> I still think it is crazy to add these 8 pages to each time someone prints
>> it
>
> It fits on exactly two pages (or front and back of one page) if wrapped in
>
> \begin{multicols}{2}
> \scriptsize
> …
>
> and it is
Jambunathan K writes:
> Citation processor could be whatever org-exp-bibtex interfaces with
> right now. I also have some proof-of-concept - see zotcite - for
> zotero.
I have a proof-of-concept on how to use Jabref to get citations in to
ODT export. I will share a recipe sometime (when it wil
Aloha dmg,
D M German writes:
> hi everybody,
>
> I have created a small document that describes how to use perl within
> org. Hopefully others will find it useful:
>
> http://turingmachine.org/~dmg/emacs/examplePerl.org
Nice.
It would be great to use this document as the basis of ob-doc-perl
On Sat, Mar 09, 2013 at 01:46:37AM +0100, Nicolas Goaziou wrote:
> Since I don't use html back-end, it would be better to hear from actual
> users what they think about it.
Sorry, forgot that you are not the keeper of ox-html, just the new
exporter at large ;).
> Anyway, just a few comments:
>
Nicolas Goaziou writes:
> I favor [cite:PROPERTIES] over [[cite:PROPERTIES]], because the latter
> (link syntax) implies a (optional) description part. I don't think
> a description is ever meaningful in citations.
I have been holding on to this for a while. Just typing it out as it
comes to my
Carsten Dominik writes:
> I still think it is crazy to add these 8 pages to each time someone prints
> it
It fits on exactly two pages (or front and back of one page) if wrapped in
\begin{multicols}{2}
\scriptsize
…
and it is still a lot more readable (even if printed out on A5 instead
of A
Bastien writes:
> Christopher Schmidt writes:
>> ( In the long term this should be fixed properly. Considering that
>> point is already on an actual headline, Org just needs to add or
>> remove a star. This should not be too hard with
>> org-heading-regexp. )
>
> Beware that there are *ma
Hello,
aarone...@gmail.com writes:
>> I think that if we ever implement a bibliography/citations handlers,
>> they should be first class objects in Org syntax (like footnotes).
>> Overloading link syntax would, IMO, be wrong in that case.
>
> Do you have a proposal for how this syntax would look?
On 9.3.2013, at 16:02, Achim Gratz wrote:
> Carsten Dominik writes:
>> I am wondering, are we required to include the full text of the GFDL
>> in the manual? I find it a big waste of space and feed that a link
>> should do. But I have not been able to find the rules that say what
>> needs to b
On 9.3.2013, at 15:42, Nicolas Goaziou wrote:
> Hello,
>
> Carsten Dominik writes:
>
>> On 9.3.2013, at 11:52, Waldemar Quevedo wrote:
>>
>>> Hey Nicolas, this looks very detailed and I think it could be useful
>>> for people trying to write other parsers implementations for org-mode.
>>> T
Hello,
Bastien writes:
> Nicolas Goaziou writes:
>
>> The only problem is when user doesn't load Babel at all, but still wants
>> to use smart quotes. Is it meaningful?
>
> It is not meaningful but it is now the default,
Actually, as Suvayu Ali suggested, it is meaningful only in the default
Carsten Dominik writes:
> I am wondering, are we required to include the full text of the GFDL
> in the manual? I find it a big waste of space and feed that a link
> should do. But I have not been able to find the rules that say what
> needs to be included in a document distributed under GFDL?
h
Hello,
Bastien writes:
> Nicolas Goaziou writes:
>> If there's no major problem with it, I'll apply it before Monday.
>> Though, I think ox-odt needs double-checking.
>
> How can we help with the double-checking?
Just test features using attributes (in particular ":width number"
attributes).
Hello,
Carsten Dominik writes:
> On 9.3.2013, at 11:52, Waldemar Quevedo wrote:
>
>> Hey Nicolas, this looks very detailed and I think it could be useful
>> for people trying to write other parsers implementations for org-mode.
>> Thanks for sharing!
>
> Maybe someone knowledgeable can turn Nic
Hi,
I am wondering, are we required to include the full text of the GFDL in the
manual? I find it a big waste of space and feed that a link should do. But I
have not been able to find the rules that say what needs to be included in a
document distributed under GFDL?
Thanks
- Carsten
Carsten Dominik writes:
> What happened to the color of the Unicorn? I don't think these
> should be changed.
This was part of an "experiment" -- I reverted back to the old
Unicorn.
--
Bastien
D M German writes:
> http://turingmachine.org/~dmg/emacs/examplePerl.org
Nice, would you consider contributing it to Worg? I'd like to ask you
to update your Org and that description to the extra features I've
recently implemented for Perl.
--8<---cut here---start
On 9.3.2013, at 11:52, Waldemar Quevedo wrote:
> Hey Nicolas, this looks very detailed and I think it could be useful
> for people trying to write other parsers implementations for org-mode.
> Thanks for sharing!
Maybe someone knowledgeable can turn Nicola's description into a formal parser
de
On 9.3.2013, at 11:06, Bastien wrote:
> Hi Suvayu,
>
> Suvayu Ali writes:
>
>> I don't know why I did not notice that before! Maybe this time I was
>> browsing around, checking things whereas earlier I knew which entry I
>> was looking for. In any case, it is less confusing after the
>> swi
Hi Terry,
I hear you. I completely agree that Org should not be less flexible
than it has been so far. At least not for very good reasons, shared
by both the developers and the users. IOW: ease of maintainance and
code consistency should not let us introduce rigidity for the users.
Let's focus
Hi Nicolas,
Nicolas Goaziou writes:
> From the user POV, it removes necessity to quote or escape characters.
> For example, these are now valid:
>
> #+attr_latex: :font \footnotesize :align |l|c|c|
> #+attr_foo: :prop var="value" :another-prop nil
>
> From the developer POV, each non-nil val
Hi Christopher,
Christopher Schmidt writes:
> I agree. I will come up with a patch ASAP.
Thanks!
> ( In the long term this should be fixed properly. Considering that
> point is already on an actual headline, Org just needs to add or
> remove a star. This should not be too hard with org-
Bastien writes:
> Alan Schmitt writes:
>
>> and do a shift-meta-right on the second line, I get:
>>
>> #+BEGIN_SRC emacs-lisp
>> ;;; * Test 1
>> ** Test2
>> #+END_SRC
>
> I confirm this issue.
>
> The easiest thing to do is to prevent some commands to run when
> `orgstruct-mode' is on and `or
hi everybody,
I have created a small document that describes how to use perl within
org. Hopefully others will find it useful:
http://turingmachine.org/~dmg/emacs/examplePerl.org
--dmg
--
Daniel M. German
http://turingmachine.org/
http://silvernegative.com/
dmg (at) uvic (dot) ca
replace (
Bastien writes:
> Achim Gratz writes:
>
>> Bastien writes:
>>> Thanks for confirming, I made the same change for http://orgmode.org.
>>
>> The server seems to be down atm (not just the web, also git)?
>
> Yes. The machine is inaccessible, no http, ssh, git or whatever.
It is now back.
--
Ba
Achim Gratz writes:
> Bastien writes:
>> Thanks for confirming, I made the same change for http://orgmode.org.
>
> The server seems to be down atm (not just the web, also git)?
Yes. The machine is inaccessible, no http, ssh, git or whatever.
I asked Jason privately about this, crossing fingers
Bastien writes:
> Thanks for confirming, I made the same change for http://orgmode.org.
The server seems to be down atm (not just the web, also git)?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
ht
Nicolas Goaziou writes:
> I admit I'm not very keen on this idea. Not because of the coding
> work, it would be around 10 loc, but because of syntax fester.
Speaking of syntax, having long blocks of #+GRMLLL_SOMETHING: lines is
somewhat of an eyesore, but instead of inventing yet another type of
b
Hey Nicolas, this looks very detailed and I think it could be useful
for people trying to write other parsers implementations for org-mode.
Thanks for sharing!
By the way, does it exist somewhere a set of examples of Emacs
org-mode -> html conversion for all org-mode features?
(How are changes fro
Hi Suvayu,
Suvayu Ali writes:
> I don't know why I did not notice that before! Maybe this time I was
> browsing around, checking things whereas earlier I knew which entry I
> was looking for. In any case, it is less confusing after the
> switch.
Thanks for confirming, I made the same change f
Nicolas Goaziou writes:
> Hello,
>
> Eric S Fraga writes:
>
>> Prompted by Nicolas's recent addition of the LATEX_HEADER_EXTRA
>> directive, I would like to request another related feature. Just as we
>> have the related LATEX and BEGIN_LATEX directives, I would like to see a
>> BEGIN_LATEX_HEA
Nicolas Goaziou writes:
> The only problem is when user doesn't load Babel at all, but still wants
> to use smart quotes. Is it meaningful?
It is not meaningful but it is now the default, this is what needs to
be fixed. Either by not using smart-quotes by default, or by letting
the user what t
Hi Nicolas,
Nicolas Goaziou writes:
> It makes sense indeed. latex back-end will use, by default, smart
> quotes.
We should turn this on by default unless we have a mechanism to fix
the LaTeX headers, if needed.
The default behavior now is wrong: for example, if I use quotes in
a document with
Achim Gratz writes:
> Bastien writes:
>>> 8dd2bfc291 release_8.0-alpha (move the new exporter into core)
>>> ee3b3eb421 release_8.0-beta (remove /contrib/oldexp/)
>>
>> Okay, please go ahead.
>
> Done.
Thanks!
--
Bastien
Hi Rick,
besides Nicolas good suggestions regarding the code, I think
the patch is good and I welcome more flexibility in the HTML
exporter so that HTML5-ready derived backends can be written.
I'll have a careful look next week.
One thing you may double-check in the meantime is: is it
compatible
Hi Aaron,
aarone...@gmail.com writes:
> This is now implemented, in the first of three patches attached to this
> email. The second patch is a reworked version of the bibliography
> support in my last patch, and the third implements link attributes for
> HTML links.
This is great -- I'll be off
Hi Alan,
Alan Schmitt writes:
> and do a shift-meta-right on the second line, I get:
>
> #+BEGIN_SRC emacs-lisp
> ;;; * Test 1
> ** Test2
> #+END_SRC
I confirm this issue.
The easiest thing to do is to prevent some commands to run when
`orgstruct-mode' is on and `orgstruct-heading-prefix-r
79 matches
Mail list logo
