Nick Dokos writes:
> I'm actually hoping that nothing of the sort will be needed, but given
> that I don't have either debian squeeze or slackware available, I can't
> really see what goes wrong.
Well, I've had a look on some server I have admin access to: what goes
wrong on Debian (Lenny+Backpor
I've made a gist at
https://gist.github.com/1073383
that details some problems with ob-clojure.el and ob-sh.el.
In particular, there are a few problems with :results verbatim/scalar and
:results output for the two modes.
M-x org-version returns:
Org-mode version 7.5 (release_7.5.516.gf06e.dirty
Vinh
> Suppose I have styles.xml and
> ./Pictures/1274034B83A526F3.png in the working
> directory of my org file, both extracted from my original odt file
> that I did myself. What exactly must I do to get these files packaged
> into the generated odt file? How do I set org-expo
Hummm... thanks for the tip! It works now. :D
---
Rafael Calsaverini
Dep. de Física Geral, Sala 336
Instituto de Física - Universidade de São Paulo
rafael.calsaver...@gmail.com
http://stoa.usp.br/calsaverini/weblog
CEL: (11) 7525-6222
USP: (11) 3091-6803
On Fri, Jul 8, 2011 at 15:26, Nick Do
There's been a recent discussion about using csquotes in the latex
exporter[fn:1] and Tom Dye came up with a good idea of how to implement
it. We have been discussing it off list but there is a point that might
benefit from more general airing, so I offered to solicit opinions on
the list.
The qu
Achim Gratz wrote:
> Nick Dokos writes:
> > Most Linux systems I know of have a description of what distro is
> > installed in the /etc/issue file: Ubuntu, Debian, RH, Fedora, SuSE
> [...]
>
> True, but it's not reliable since it is quite common to customize the
> login message. And the next t
Eric S Fraga writes:
> thanks; but cygwin seems natural to install in conjunction with emacs as
> I want bash et al. if I ever have to use Windows. having said this,
> it's been years since I have had to do this luckily (for me).
Yes, but even with a complete Cygwin install running X in fullscre
Russell Adams writes:
Hi Russell,
>> This is *beautiful*.
>
> I concur completely! This has filled a gap I've had for quite a while,
> needing to visualize org tasks across a calendar.
>
> Two minor FRs (I hope you continue to monitor the list):
>
> - 'q' key to close the calendar buffer, like
Nick Dokos writes:
> Most Linux systems I know of have a description of what distro is
> installed in the /etc/issue file: Ubuntu, Debian, RH, Fedora, SuSE
[...]
True, but it's not reliable since it is quite common to customize the
login message. And the next thing of course is that you don't ha
Rainer
Thanks for reporting the bug. I have pushed a fix few moments ago. Could
you please try again?
The problem was that timestamps were occuring as list item in the
example you provided which confused the exporter.
If you encounter corruption issue or issues related to formatting of odt
file
Bastien writes:
>> is there a process for bug-fix commits like this one which should be
>> pushed through to Emacs24? I'm thinking a branch (maintenance?) to
>> which this should be pushed or a special way to tag the commit?
>
> there is none for now -- I need to think about it.
Pure fixes shoul
writes:
> Hi,
>
> I know from the manual that I can set 'org-confirm-babel-evaluate' to t,
> or nil, or a function, to control whether I'm asked permission to run a
> code block.
>
> However, that only gives me two choices - ask the user, or pretend the
> user said "yes". Sometimes I'd like to p
Jambunathan K writes:
> In org-footnote-forbidden-blocks
>
> '("example" "verse" "src" "latex" "html" "docbook")
>
> should we make use of org-export-backends.
>
> I introduced the above variable as part of org-odt compatibility
> changes.
>
>
> ,[ C-h v org-export-backends RET ]
> | org-exp
Hi,
I know from the manual that I can set 'org-confirm-babel-evaluate' to t,
or nil, or a function, to control whether I'm asked permission to run a
code block.
However, that only gives me two choices - ask the user, or pretend the
user said "yes". Sometimes I'd like to pretend the user said "no
Rafael Calsaverini wrote:
> Hi. I'm noticed a problem with latex equations and footnotes. I'm not
> sure, but I believe it started after I downloaded the newest version
> of org-mode.
>
> When I try to export a $...$ block that is inside a footnote, the
> latex file end up with \$...\$ instead o
Hi. I'm noticed a problem with latex equations and footnotes. I'm not
sure, but I believe it started after I downloaded the newest version
of org-mode.
When I try to export a $...$ block that is inside a footnote, the
latex file end up with \$...\$ instead of $...$. As an example, this:
#+LaTeX_C
Nicolas
> Footnotes cannot live anymore in example, src, verse, latex, html and
> docbook blocks.
In org-footnote-forbidden-blocks
'("example" "verse" "src" "latex" "html" "docbook")
should we make use of org-export-backends.
I introduced the above variable as part of org-odt compatibility
c
Hello,
Bastien writes:
> Nicolas Goaziou writes:
>
>> I will remove the opportunity to have footnotes in some specific
>> contexts, like example blocks.
>
> Wise decision -- the less feet we have, less shoots in the feet
> we may have.
Done.
Footnotes cannot live anymore in example, src, ver
Frederik writes:
> Am 08.07.2011 04:09, schrieb Nick Dokos:
>> Thomas S. Dye wrote:
>>
>>> Hi Nick,
>>>
>>> Good point.
>>>
>>> How about three new variables, org-export-latex-open-double-quotes,
>>> org-export-latex-close-double-quotes, and org-export-latex-single-quote?
>>>
>>> The regexp stuf
After every release there are messages like this.
And Memmon is right. It cannot be said too often. Thank you everyone for
your hard work.
On 7/07/11 11:01 AM, "Achim Gratz" wrote:
>Bastien writes:
>> I'm releasing Org 7.6.
>
>Thank you and everyone else for all the work that has been put in
Hi Bastien,
On Fri, 08 Jul 2011 11:08:07 +0200
Bastien wrote:
> As long that I'm confident many testers use the latest master branch,
> I'm reluctant to go through the hassle of cherry-picking commits...
> and just release a minor release with all latest dev from master.
>
> Call me lazy, bu
Eric Schulte writes:
> I don't see this error when running make, I'm using the Emacs git head,
> perhaps this is Emacs version specific?
I don't think so: in ob-lilypond.el, the `ly-tangle' function calls
`org-babel-tangle', so requiring ob-tangle.el seems the right thing
to do here.
No?
--
Bastien,
Thanks! I was just hoping to make sure that I had made the correction
in an appropriate fashion for those on this project (having it require
the file that had the function defined instead of re-defining the
file). I am still relatively new here, new to elisp and git. Again,
thanks for
Am 08.07.2011 04:09, schrieb Nick Dokos:
Thomas S. Dye wrote:
Hi Nick,
Good point.
How about three new variables, org-export-latex-open-double-quotes,
org-export-latex-close-double-quotes, and org-export-latex-single-quote?
The regexp stuff could stay as hard code and the user would only be
Hi Matthew,
Matthew Sauer writes:
> Thanks for all the work everyone puts in on this list and on this
> project. Org-Mode has really gotten me squared away and keeps things
> organized for me. In an effort to try and start help giving back I
> just submitted a patch reference a compiler error.
I don't see this error when running make, I'm using the Emacs git head,
perhaps this is Emacs version specific?
-- Eric
Matthew Sauer writes:
> ---
> diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el
> index 6971a69..5a08ca4 100644
> --- a/lisp/ob-lilypond.el
> +++ b/lisp/ob-lilypond.el
>
Hi Matthew,
Matthew Sauer writes:
> ---
> diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el
> index 6971a69..5a08ca4 100644
> --- a/lisp/ob-lilypond.el
> +++ b/lisp/ob-lilypond.el
> @@ -30,6 +30,7 @@
> ;;; Code:
> (require 'ob)
> (require 'ob-eval)
> +(require 'ob-tangle) ;;compiler requ
Hi,
Quick question: I'd like to use a babel inline call to calculate
something in a table based on other values in the table. Is this
possible? Probably using elisp directly? If so, I cannot figure out
what the magic incantation should be! I hope somebody can help.
For illustration, I'd like
Bastien writes:
> Hi Eric,
>
> Eric Schulte writes:
>
>> I do prefer to fold new languages in early so that they can benefit from
>> wider use and testing.
>>
>> This is now located in contrib/babel/langs/.
>
> Thanks. I slightly updated library-of-babel.org to list existing
> supported languag
Thanks for all the work everyone puts in on this list and on this
project. Org-Mode has really gotten me squared away and keeps things
organized for me. In an effort to try and start help giving back I
just submitted a patch reference a compiler error. I know they aren't
high priority necessaril
---
diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el
index 6971a69..5a08ca4 100644
--- a/lisp/ob-lilypond.el
+++ b/lisp/ob-lilypond.el
@@ -30,6 +30,7 @@
;;; Code:
(require 'ob)
(require 'ob-eval)
+(require 'ob-tangle) ;;compiler requesting fun org-babel-tangle
(defalias 'lilypond-mode 'Li
Russell Adams writes:
> Two minor FRs (I hope you continue to monitor the list):
https://github.com/kiwanami/emacs-calfw/issues ?
> - 'q' key to close the calendar buffer, like org-agenda does
,[ https://github.com/kiwanami/emacs-calfw/pull/4 ]
TSDH: aee24d8 Bind q to b
Hi Eric,
Eric Schulte writes:
> I do prefer to fold new languages in early so that they can benefit from
> wider use and testing.
>
> This is now located in contrib/babel/langs/.
Thanks. I slightly updated library-of-babel.org to list existing
supported languages, either in core or in contrib/
Hi Rainer,
Rainer Stengele writes:
> DONE [#A] Test
> #+OPTIONS: <:nil
> - [2011-07-08 Fr] test
>
>
> So if I want to export timestamps the exporter fails.
I confirm -- here is the faulty string:
,
|
| text:style-name="OrgTimestampWrapper">
| 2011-07-08 Fr
| test
`
Ja
Torsten Anders writes:
> Dear Eric,
>
> On 8 Jul 2011, at 02:38, Eric Schulte wrote:
>>
>> Thanks for sharing this, it looks great, short clear and to the point.
>>
>> Shall I add it to the contrib/ directory?
>
> If you think it is already at that point, that is certainly fine by me.
>
Great,
Hi Loris,
"Loris Bennett" writes:
> I think maybe I need to start a new thread some time about generally
> approaches to using tags vs. categories. I am sure there must a few
> fairly standard idioms that people are using.
Good idea.
Personally, I use tags for contexts and categories for proje
On Wed, Jul 06, 2011 at 11:30:02AM +, Memnon Anon wrote:
> This is *beautiful*.
I concur completely! This has filled a gap I've had for quite a while,
needing to visualize org tasks across a calendar.
Two minor FRs (I hope you continue to monitor the list):
- 'q' key to close the calendar
Hi Rainer,
Rainer Stengele writes:
> DONE [#A] Test
> #+OPTIONS: <:t
> - [2011-07-08 Fr] test
Why would you put #+OPTIONS here?
> this works:
>
> DONE [#A] Test
> #+OPTIONS: <:t
> - [2011-07-08 Fr] test
What is the difference between the 2?
--
Bastien
Am 08.07.2011 14:22, schrieb Rainer Stengele:
> Hi!
>
> Having this simple org file
>
> DONE [#A] Test
> #+OPTIONS: <:t
> - [2011-07-08 Fr] test
>
> the export with C-c C-e O stops when starting LibreOffice 3.4.1 with the
> message:
>
>
> Read Error.
> Format Error in textdocument
Hi Nicolas,
Nicolas Goaziou writes:
> I will remove the opportunity to have footnotes in some specific
> contexts, like example blocks.
Wise decision -- the less feet we have, less shoots in the feet
we may have.
--
Bastien
Nicolas Goaziou writes:
> Hello,
>
> Bernt Hansen writes:
>
>> Sample org file
>> * Using the clock history to clock in old tasks
>> *Clock history selection buffer for C-u C-c C-x C-i*
>> #+begin_example
>> Default Task
>> [d] norang Organization <-- Task B
Memnon Anon writes:
> "Loris Bennett" writes:
>
What should the correct syntax be and where is it described?
>>>
>>> Did you look in the manual? What is missing?
>>
>> I looked here
>>
>>http://orgmode.org/manual/Block-agenda.html#Block-agenda
>>
>
> ,[ C-h v org-agenda-custom-comm
Hello,
Bernt Hansen writes:
> Nicolas Goaziou writes:
>
>> Samuel Wales writes:
>>
>>> On 2011-07-05, Nicolas Goaziou wrote:
As I cannot reproduce this on my test files, I will need an ECM to debug
this.
>>>
>>> Included.
>>>
>>> The bug occurs in ASCII export also.
>>
>> Thank you
"Loris Bennett" writes:
>>> What should the correct syntax be and where is it described?
>>
>> Did you look in the manual? What is missing?
>
> I looked here
>
>http://orgmode.org/manual/Block-agenda.html#Block-agenda
>
,[ C-h v org-agenda-custom-commands ]
| matchWhat to search for
"Loris Bennett" writes:
> Hi Bastien,
>
> Bastien writes:
>
>> Hi Loris,
>>
>> "Loris Bennett" writes:
>>
>>> In my org-agenda-custom-commands I've got two block entries:
>>>
>>> tags-todo "office&(project|task)"
>>>
>>> and
>>>
>>> tags-todo "home&(project|task)"
>>>
>>> Items with :office:pr
Hi!
Having this simple org file
DONE [#A] Test
#+OPTIONS: <:t
- [2011-07-08 Fr] test
the export with C-c C-e O stops when starting LibreOffice 3.4.1 with the
message:
Read Error.
Format Error in textdocument content.xml at position 288,114 found.
this works:
DONE [#A] Test
On Fri, Jul 08 2011,Bastien wrote:
> Hi Sivaram,
>
> Sivaram Neelakantan writes:
>
>> This makes it easier to read as you can see below
>> | BEL | EQ | 02-Jan-2006 | 993.15 | 998 |1001 | 983 |..
>> | BEL | EQ | 03-Jan-2006 | 989.05 | 999.5 |1000 | 989.9 |..
>> | BEL | EQ |
Hi all,
having standard clock entries like
CLOCK: [2011-07-08 Fr 08:45]--[2011-07-08 Fr 09:15] => 0:30
many a times later on I want to adjust the beginning timestamp.
Moving the whole clock range backward or forward maybe half an hour is a 2 step
procedure:
First I have to adjust the begi
Torsten Wagner writes:
> There is jabref [1].
Exactly. I was also going to point out JabRef. I have had Bibtex
illiterates manageing Bib files using JabRef.
> It also claims to have a Openoffice support
> never tried.
I tried it once and it works very nice. There were annoying limitations
in O
Hi there,
I don't like the flashy warnings org-odt.el produces,
so I introduced this defcustom in latest git:
(setq org-lparse-use-flashy-warning nil)
will turn off the warnings.
--
Bastien
Bastien writes:
>
> Indeed. I'll apply every patch that
>
> - doesn't break current Makefile commands
> - does add a new func (even tiny) for specific distro
>
> Please send some :)
One way to make the whole deployment really portable could also be to
pass from plain Makefile to the autoconf be
Hi Bastien,
Bastien writes:
> Hi Loris,
>
> "Loris Bennett" writes:
>
>> In my org-agenda-custom-commands I've got two block entries:
>>
>> tags-todo "office&(project|task)"
>>
>> and
>>
>> tags-todo "home&(project|task)"
>>
>> Items with :office:project: and :home:project: are separated prope
On Fri, Jul 08 2011,Rainer M Krug Rainer M Krug wrote:
[snipped 20 lines]
> Definitely useful - a read-only viewer of delimited files, would be a
> useful feature (and sometimes safer then an editor) which I would use
> regularly.
>
> But a really nice feature would be to be able to open a deli
Jude DaShiell writes:
> No I can't provide any patch that works with all distros. I don't have
> all distros available to me; not all Linux distros are accessible for
> screen reader users either. I use screen reading software just to use a
> computer and I don't have all distros even unde
Hi Matthieu,
Matthieu Lemerre writes:
> Compared to what org-mode currently exports, only three fields are missing:
>
> - Organizer. This should not be too hard to do (using
>user-mail-adress).
Okay.
> - Method:request (should also be easy...)
Should this field be present in every entry
Hi Masashi,
SAKURAI Masashi writes:
> the re-design of the whole org-agenda-list algorithm
> seems to be needed, because the key function
> org-agenda-get-day-entries requires only one date and the subsequent
> dependent functions also are designed by the API.
FWIW, I'm all ears -- if you have
Not at all.
Pierre
Le 8 juil. 11 à 09:36, Sebastien Vauban a écrit :
Hi Pierre,
Any objection for applying this patch?
Pierre de Buyl wrote:
I checked and indeed "content" is working well.
Pierre
Le 1 juil. 11 à 16:06, Sebastien Vauban a écrit :
Hi Pierre,
Pierre de Buyl wrote:
Le 28
Hi Nick,
Nick Dokos writes:
> PS and then there is OS X and Windows, and other Unixes and who knows
> what else...
Indeed. I'll apply every patch that
- doesn't break current Makefile commands
- does add a new func (even tiny) for specific distro
Please send some :)
--
Bastien
Jude DaShiell wrote:
> To use org-mode default uncomment /usr/local as prefix for all systems
> that put emacs stuff or some emacs stuff under /usr/local. For
> Slackware and Debian though, /usr/local isn't in the load-paths. The
> install-info part of the patch was using debian's install-in
Matthieu Lemerre writes:
>>
>> I have no idea what I will need to do! I really am truly ignorant of
>> the whole MS world other than I know, if push comes to shove, I can
>> install cygwin and then Emacs when I have to... ;-)
>
> Actually, there are emacs binaries for win32 that work without ne
Hi Nick,
Nick Dokos writes:
> I'm not sure whether I posted this before but if you haven't seen
> it before, it's probably worth reading:
>
>http://nvie.com/posts/a-successful-git-branching-model/
Nice read -- thanks.
In fact, we *do* have a documented process for important fixes
that nee
Eric Schulte writes:
> Hi Eric,
>
> Unfortunately I recently became very busy, so I will not be able to
> address this any time soon.
Hi Eric. That's perfectly fine! I completely understand. As I said,
it's a very low priority request.
> However, the indexing behavior is self
> contained i
Dear Eric,
On 8 Jul 2011, at 02:38, Eric Schulte wrote:
>
> Thanks for sharing this, it looks great, short clear and to the point.
>
> Shall I add it to the contrib/ directory?
If you think it is already at that point, that is certainly fine by me.
Best,
Torsten
>
> Best -- Eric
>
> Torste
Dear Henri-Paul,
On 8 Jul 2011, at 00:27, Henri-Paul Indiogine wrote:
> Yes, but the sad thing is that using emacs+orgmode is so fast, easy
> and productive. Writer or Word feel so clunky and backwards.
Sure, you can write with orgmode and then export for your supervisor to
OpenOffice/Word.
Hi Manuel,
Manuel Hermenegildo writes:
> I.e., an idea would be to add a back end to the code
> that generates the org agenda which, instead of rendering the agenda
> creates the calfw objects.
I'm all for an Org agenda backend -- but before that, we *need* to
make `org-agenda-get-day-entries'
Hi Jiang,
"jiangzuo...@gmail.com" writes:
> Formulas reference in a long table are very easy corrupted by
> manually inserting. so, I think, refer using name instead of num. is
> better.
>
> but how to refer the rows by name?
>
> For example,
>
> |---+--+-++-+--|
Hi Jude,
I understand.
I think we can go with a FAQ: "How to compile and install Org under
Debian and Slackware?", then include your patch in the answer.
Can someone confirm Jude's patch solves install issues for Debian
and Slackware?
Thanks,
--
Bastien
On Fri, Jul 8, 2011 at 10:12 AM, Bastien wrote:
> Hi Sivaram,
>
> Sivaram Neelakantan writes:
>
> > This makes it easier to read as you can see below
> > | BEL | EQ | 02-Jan-2006 | 993.15 | 998 |1001 | 983 |..
> > | BEL | EQ | 03-Jan-2006 | 989.05 | 999.5 |1000 | 989.9 |..
Hi Loris,
"Loris Bennett" writes:
> In my org-agenda-custom-commands I've got two block entries:
>
> tags-todo "office&(project|task)"
>
> and
>
> tags-todo "home&(project|task)"
>
> Items with :office:project: and :home:project: are separated properly,
> but :office:task: and :home:task: end u
Hi Sivaram,
Sivaram Neelakantan writes:
> This makes it easier to read as you can see below
> | BEL | EQ | 02-Jan-2006 | 993.15 | 998 |1001 | 983 |..
> | BEL | EQ | 03-Jan-2006 | 989.05 | 999.5 |1000 | 989.9 |..
> | BEL | EQ | 04-Jan-2006 | 994.35 | 998 |1014 | 98
Hi
>>> I first had to load dot support (because you are calling
>>> org-babel-expand-body:dot). If you want to also attract musicians (without
>Thanks for finding this error Torsten! I've just pushed up a fix.
Thanks Torsten for the heads-up, and
thanks Eric for the rapid response.
Regards
No I can't provide any patch that works with all distros. I don't have
all distros available to me; not all Linux distros are accessible for
screen reader users either. I use screen reading software just to use a
computer and I don't have all distros even under the category of distros
that ar
Hi Pierre,
Any objection for applying this patch?
Pierre de Buyl wrote:
> I checked and indeed "content" is working well.
>
> Pierre
>
> Le 1 juil. 11 à 16:06, Sebastien Vauban a écrit :
>
>> Hi Pierre,
>>
>> Pierre de Buyl wrote:
>>> Le 28 juin 11 à 23:45, Sebastien Vauban a écrit :
Here is
Hi Nick and Tom,
Nick Dokos writes:
> Sounds good: there's always tomorrow. BTW, since you are doing the hard
> work here, I'll volunteer to write a section for the LaTeX tutorial (but
> if you prefer to write it, I will defer).
I'm following this thread and waiting for the patch -- would be ni
Bastien wrote:
> > is there a process for bug-fix commits like this one which should be
> > pushed through to Emacs24? I'm thinking a branch (maintenance?) to
> > which this should be pushed or a special way to tag the commit?
>
> there is none for now -- I need to think about it.
>
> As I wil
75 matches
Mail list logo
