Daimrod writes:
> @All: Can I use (require 'cl) and ignore the warning or is there better
> solution?
You could if this would never go into mainline, where it is not allowed
due to the namespace pollution that cl causes. You could use cl-lib
instead, but then this would be an Emacs-24 only soluti
Thomas S. Dye writes:
> I do have a problem here. I think I have mis-configured BTEST_POST.
>
> I have this:
>
> BTEST_POST =
> # -L /ert # needed for Emacs23, Emacs24 has ert
> built in
> # -L /ess # needed for running R tests
> -L contrib/lis
Aloha Jambunathan,
Jambunathan K writes:
>
> Even if my combative positioning doesn't amount to anything much, I want
> to throw in a little friction by the way of Bastien and the current
> release. I am stating my purpose in no uncertain terms - yes it is to
> delay the release or cause confus
Christopher Schmidt writes:
> Detlef Steuer writes:
>> But: The papers the FSF asked you to sign were constructed for exactly
>> this case I assume.
>
> That's not right.
>
> https://www.gnu.org/licenses/why-assign.html
>
> I am not a copyright lawyer. So is everyone else subscribed to this
Scott Randby gmail.com> writes:
> However, I am concerned about the future of org. There is one
> individual who is poisoning the atmosphere by engaging in unfair and
> unfounded name calling that simply should not be included in messages
> to this list. Now this person wants to take some of thei
Hi Bastien,
Thanks for removing the table tags. It looks great in w3m. Much less
confusing.
For some reason, I am getting no blank lines between footnotes, and no
blank lines between paragraphs in multi-paragraph footnotes. Any idea
why? Tested in Firefox.
I can try to dig up old exporter ou
On 11/03/13 06:30, Christopher Schmidt wrote:
Detlef Steuer writes:
But: The papers the FSF asked you to sign were constructed for exactly
this case I assume.
That's not right.
https://www.gnu.org/licenses/why-assign.html
I am not a copyright lawyer. So is everyone else subscribed to
Achim Gratz writes:
> Thomas S. Dye writes:
>> That works nicely. I found the error and orgmanual.pdf is now produced
>> without errors.
>
> Progress! :-)
>
> With the current version from git I cannot export to texinfo
This is fixed now.
>
> I've extended the Makefile to approximate the one i
I've now committed this patch.
--
Eric Schulte
http://cs.unm.edu/~eschulte
Frank Terbeck writes:
Hi Frank,
Thank you for the report; however, I'm unsure about the right solution.
There is a problem with the current (eval-when-compile ...) but there
are still warnings when I compile it (with emacs -batch -f batch-byte-compile).
> In org-contacts-db-need-update-p:
> or
Hello
On 10 March 2013 13:12, Achim Gratz wrote:
> Jambunathan K writes:
> > Emacs lisp has a manual of it's own. I don't see how Org export
> > reference *cannot* end in Emacs.
>
> I said that I'm expecting these references to become part of the
> manual(s). I still expect that and will try t
Michael Gauland writes:
> I'm working with an sqlite database of songs, and I've run into trouble
> with titles that start with a '(' (for example,
> (I Can't Get No) Satisfaction). 'Verbatim' results work:
>
> #+BEGIN_SRC sqlite :db test-db :results verbatim
> .mode csv
> .separator
Sebastien Vauban writes:
> A more general question: shouldn't cache be unusable (generate an
> error) when there is a session? In the presence of a session, I've
> the impression that caching results is always wrong. Who knows its
> contents before executing the code, in the next Emacs session?
T
Hello,
On 10 March 2013 16:23, Nicolas Goaziou wrote:
> Hello,
>
> Jonathan Leech-Pepin writes:
>
> > The error is not actually within ox-texinfo in this case however I
> suspect.
> > The exact same code (at the location of the error in ox-texinfo) appears
> > within
> > ox-latex and ox-ascii.
Aloha Christopher,
Christopher Schmidt writes:
> #+BEGIN my2cents
> If Jambunathan does not want code he wrote to be part of Org any more,
> I'd respect his wish. At first sight this is a loss for Org. This
> does not need to be the end, though. GSoC is coming up, rewriting
> specific exporte
Hello,
Jonathan Leech-Pepin writes:
> The error is not actually within ox-texinfo in this case however I suspect.
> The exact same code (at the location of the error in ox-texinfo) appears
> within
> ox-latex and ox-ascii.
>
> `(org-trim contents)', which removes whitespace at start and end of s
Achim, Eric,
Achim Gratz wrote:
> Eric Schulte writes:
>> A hash marks a *result* with an indication of what was used to generate
>> it (code block & parameters). The point of a hash is to allow the
>> result to be returned without having to re-execute. For this reason, I
>> think that the hash
Hello Dario,
On 12 February 2013 17:09, Dario Hamidi wrote:
>
> Hello Jonathan,
>
> > Using your patch as is would wrap the source blocks in both example and
> > verbatim blocks. If going with verbatim it would be better to remove all
> > references to @example/@end example.
>
> I don't underst
On 10 March 2013 15:25, Achim Gratz wrote:
> Jonathan Leech-Pepin writes:
> > The error is actually on line 6069 of the manual. The {{{vindex
> > [...]}}} line and subsequent paragraph. As far as the list is
> > concerned there is no associated content for that list
> > entry. Indenting them appr
Detlef Steuer writes:
> But: The papers the FSF asked you to sign were constructed for exactly
> this case I assume.
That's not right.
https://www.gnu.org/licenses/why-assign.html
I am not a copyright lawyer. So is everyone else subscribed to this
list. The FSF's copyright clerk should as
Jonathan Leech-Pepin writes:
> The error is actually on line 6069 of the manual. The {{{vindex
> [...]}}} line and subsequent paragraph. As far as the list is
> concerned there is no associated content for that list
> entry. Indenting them appropriately to be recognized as part of the
> list allows
Am 10.03.2013 19:55, schrieb Detlef Steuer:
I am willing to go as far is humanly possible for me to have my
displeasure registered.
Dear Jambunathan,
your displeasure is very well registered by the hundreds or even
thousands of readers of this list.
It is very sad to see an obviously very
Hello Achim,
On 10 March 2013 08:24, Achim Gratz wrote:
> Thomas S. Dye writes:
> > That works nicely. I found the error and orgmanual.pdf is now produced
> > without errors.
>
> Progress! :-)
>
> With the current version from git I cannot export to texinfo
> successfully, though, I get this er
> I am willing to go as far is humanly possible for me to have my
> displeasure registered.
>
Dear Jambunathan,
your displeasure is very well registered by the hundreds or even
thousands of readers of this list.
It is very sad to see an obviously very gifted and energetic programmer
going in
Hi,
Is there a way to specify publishing options (e.g. the location) at the
level of the file to be published, instead doing this globally in the
=.emacs= file?
I have many projects in orgmode which consist of a single file. I have
been looking at #+SETUPFILE (which seems to deal only with
t...@tsdye.com (Thomas S. Dye) writes:
> Aloha all,
>
> I'm not sure how this happened, but chapter 2 of orgmanual now has all
> the macros replaced by their expansions. You can see this here:
>
> https://github.com/tsdye/orgmanual/blob/master/orgmanual.org
Apologies for the brief post earlier.
Aloha Jambunathan,
Jambunathan K writes:
> Thomas
>
> I will reply to you in private.
>
> I am talking to Samuels and Ricks who think that I have no right to
> offer my opinions on what gets in to that file.
If this is indeed what is being discussed, then there is no reason to
discuss it on the
Jambunathan K writes:
> Emacs lisp has a manual of it's own. I don't see how Org export
> reference *cannot* end in Emacs.
I said that I'm expecting these references to become part of the
manual(s). I still expect that and will try to help it along, but it
doesn't necessarily need to take the
Last September, I attended a talk given by the lead developers of a
prominent free software project. One of the developers spoke about the
importance of maintaining a friendly community that does not drive
people away. In particular, the developer emphasized that the
community is more important tha
Achim Gratz writes:
> Bastien writes:
>> No, the documents can go into the distribution with contributions from
>> anyone, because they won't be in Emacs. FSF assignment is needed only
>> for things that go into Emacs.
>
> I understood that these or substantial parts of it will end up in the
> O
Bastien writes:
> No, the documents can go into the distribution with contributions from
> anyone, because they won't be in Emacs. FSF assignment is needed only
> for things that go into Emacs.
I understood that these or substantial parts of it will end up in the
Org manual, which is in Emacs. I
On 03/03/2013 08:33 PM, François Pinard wrote:
> 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
Bastien
> But both reference documents don't fit into the manual IMO.
You are a jerk, a BIG JERK.
Jambunathan K.
--
Nicolas Goaziou writes:
> 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.
Thanks a lot!
Alan
I would like to remove ox-html.el from Org distribution. My
relationship with ox-html.el is a bit complicated and I am not sure how
far I can go forward on this front.
I am willing to go as far is humanly possible for me to have my
displeasure registered.
--
ox-odt.el/ox-freemind.el: Please remove it from Org core and don't
distribute these files with Org.
I don't want to discuss property rights. I am the sole author of
ox-odt.el and I don't want it as part of Org distribution.
As for ox-html.el etc, interested people can watch emacs-devel for
eith
hi all
I badly need the feature of exporting org-mode to wiki(like mediawiki).
After google for a while, I found some links but they don't work for me.
Do you guys have any suggestion for this? If no option, I may use lisp
to implement them by myself.
http://lists.gnu.org/archive/html/emacs-org
Achim Gratz writes:
> Obviously, multicols is a LaTeX package and that code snippet was from
> one of my own documents that was written directly in LaTeX. So, sadly,
> I do not have any working example of how to do it in TeX, let alone
> TeXinfo. So we will have to ask elsewhere to get that kin
Achim Gratz writes:
> Bastien writes:
>> That said, we can also bundle both documents into Org's distribution,
>> as .org files in the doc/ directory. And have a make rule to convert
>> them to .pdf and info docs.
>
> I don't want to be the party pooper, but if these documents should go
> into t
Bastien writes:
Hi there,
> Alan Schmitt writes:
>
>> even though the cursor is on a structure element. Maybe a more
>> information "this function is disabled" would work (if it's possible).
>> But as I said, it's a nitpick.
thank you very much for testing the patch.
> I agree with Alan, let'
Hi Charles,
On Wed, Mar 06, 2013 at 07:11:48AM +, Charles Berry wrote:
> I added to org-hacks.org at the bottom of ** Exporting org files. I tried to
> push to worg but got a permission error - its been years since I last pushed
> anything, so something on my end probably needs to be updated.
Jambunathan K writes:
> Or try
> C-u M-x info RET org-syntax.info RET
Bye, bye webbrowser! Finally a (relatively) painless way to get info
documentation, great.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
ht
Bastien writes:
> That said, we can also bundle both documents into Org's distribution,
> as .org files in the doc/ directory. And have a make rule to convert
> them to .pdf and info docs.
I don't want to be the party pooper, but if these documents should go
into the distribution, then we must in
Karl Voit writes:
> Since my Org-mode update from today (from
> 5d467d6f8affc0afe34922e885ac6e2492ddd091 Fri Feb 15 15:28:35 2013
> +0100) it takes very long to export the ics file.
>
> I guess this relates to ...
>
> org-babel-exp processing... [25 times]
>
> ... which also pops up some babel re
Bastien writes:
> Feel free to make the change in org.texi if you know how to achieve
> this in a simple way. I checked the Texinfo manual and the control
> over columns and font size is rudimentary. My tests using @iftex
> didn't go anywhere :/
Obviously, multicols is a LaTeX package and that c
Thomas S. Dye writes:
> That works nicely. I found the error and orgmanual.pdf is now produced
> without errors.
Progress! :-)
With the current version from git I cannot export to texinfo
successfully, though, I get this error near the end of the export:
Debugger entered--Lisp error: (wrong-typ
Hello,
Before Org 8 is out, I'm willing to put light on some last syntax which I find
counter-intuitive and not along the lines of the rest: it concerns the
`results' parameter.
Let's sum up first the list of all parameters:
1. Collection
- :results value
- :results output
2. Type of res
Jambunathan K writes:
> I wrote the code, I know where it will bite. I will not say it, because
> you seem so confident. Yes, go ahead and fix it.
Done, thanks.
--
Bastien
Bastien writes:
> Jambunathan K writes:
>
>> I was typing faster. So I consider what I typed grammatically
>> malformed. Sorry.
>
> No problem.
>
>> People who want improvements to ox-html.el should be willing to work
>> with me or act on my comments or argue with me or openly call me I am
>>
Thomas
I will reply to you in private.
I am talking to Samuels and Ricks who think that I have no right to
offer my opinions on what gets in to that file.
Jambunathan K.
Jambunathan K writes:
> I was typing faster. So I consider what I typed grammatically
> malformed. Sorry.
No problem.
> People who want improvements to ox-html.el should be willing to work
> with me or act on my comments or argue with me or openly call me I am
> wrong.
People who want to wor
Bastien writes:
> But both reference documents don't fit into the manual IMO. They
> are great resources for developers, not for users. The footnotes
> are enough for advanced users who want to go beyond the manual.
That said, we can also bundle both documents into Org's distribution,
as .org
Bastien writes:
> Jambunathan K writes:
>
>> I asked him to remove ox-html.el and he indicated how he wanted to
>> proceed ahead. He wants ox-html.el in the tree and not GNU ELPA.
>
> Just to prevent confusion: I never said anything like this.
>
> ox-html.el is in the master branch of Org's rep
Hi Nicolas,
the manual would enjoy a subsection in "Hacking" on how to create
a new exporter, either from scratch or as a derived exporter.
(Such a subsection can be short enough, thanks to derived backend.)
>From this section, we can throw links to the exporter reference
document and the Org syn
Carsten Dominik writes:
> 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
Jambunathan K writes:
> 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 coul
Hi Bastien,
On Sun, Mar 10, 2013 at 10:34:26AM +0100, Bastien wrote:
> Suvayu Ali writes:
>
> > I remember someone (maybe Bastien) putting in a safeguard quite sometime
> > back that would unfold a headline with a warning when you tried to edit
> > near the ellipses. This was to protect against
Hi Alan and Christopher,
Alan Schmitt writes:
> even though the cursor is on a structure element. Maybe a more
> information "this function is disabled" would work (if it's possible).
> But as I said, it's a nitpick.
I agree with Alan, let's update the user-error to something more
informative -
Jambunathan K writes:
> I asked him to remove ox-html.el and he indicated how he wanted to
> proceed ahead. He wants ox-html.el in the tree and not GNU ELPA.
Just to prevent confusion: I never said anything like this.
ox-html.el is in the master branch of Org's repository, it will be
in GNU EL
Hi Samuel,
Samuel Wales writes:
> How do we make it a reality NOW?
No, I stated my reasons here:
http://article.gmane.org/gmane.emacs.orgmode/67829
--
Bastien
Hi Suvayu,
Suvayu Ali writes:
> I remember someone (maybe Bastien) putting in a safeguard quite sometime
> back that would unfold a headline with a warning when you tried to edit
> near the ellipses. This was to protect against accidental edits. I see
> this not there anymore, can we have it b
Christopher Schmidt writes:
> 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.
It's looking good, thanks. One small nitpick: when a key is disabled,
the message is
orgst
* Marvin Doyley wrote:
>
> Hi there,
Hi!
> Does anybody know how to export deadline or schedule items from org to
> ical ?
I think you want to read following pages:
http://orgmode.org/manual/iCalendar-export.html
http://orgmode.org/worg/org-tutorials/org-google-sync.html
--
Karl Voit
Eric Schulte writes:
> A hash marks a *result* with an indication of what was used to generate
> it (code block & parameters). The point of a hash is to allow the
> result to be returned without having to re-execute. For this reason, I
> think that the hash should live with the result.
Here Babe
TexInfo conversion of Org syntax (Success!)
The info file looks good. But, I feel some stylistic aspects can be
improved.
Eval this form
(info "/home/kjambunathan/src/worg/dev/org-syntax.info" nil)
Or try
C-u M-x info RET org-syntax.info RET
65 matches
Mail list logo
