What appears to be a subtle difference in html export detail between
Emacs 22 and Emacs 23+ breaks these latest tests on Emacs 22.
The attached patch fixes them (and the subtle difference is not relevant
to these tests).
Best, Martyn
>From b67f2c34fb2bea791b847c3dbb7dc26e313f779f Mon Sep 17 00:
Hi Thomas,
Thomas S. Dye wrote:
> "Sebastien Vauban"
> writes:
>> Thomas S. Dye wrote:
>>> I'm sometimes running into this error message when I capture:
>>>
>>> condition-case: Capture abort: (quit pasteboard doesn't contain valid data)
>>>
>>> Unfortunately, this doesn't mean anything to me. Th
Martyn Jago writes:
> What appears to be a subtle difference in html export detail between
> Emacs 22 and Emacs 23+ breaks these latest tests on Emacs 22.
>
> The attached patch fixes them (and the subtle difference is not relevant
> to these tests).
Applied, thanks!
This commit has also been r
Thanks a lot!
Lasse
Am 05.01.2012 um 16:49 schrieb Bernt Hansen:
> Carson Chittom writes:
>
>> Bernt Hansen writes:
>>
>>> Lasse Bombien writes:
>>>
Hi,
first of all: thanks for org-mode. I'm still new to it but love it already.
Now, I need to find a way to produc
Nick Dokos writes:
> François Pinard wrote:
>> When Org mode defines a link for me, it sometimes changes it so it
>> becomes relative. [...] This is OK in general, but not always.
>> [...] I have feeling that there is something deeper which might
>> likely affect many Org mode users, and for
Hi François,
François Pinard wrote:
> Nick Dokos writes:
>
>> François Pinard wrote:
>
>>> When Org mode defines a link for me, it sometimes changes it so it
>>> becomes relative. [...] This is OK in general, but not always.
>>> [...] I have feeling that there is something deeper which might
>
Hi Nick,
Nick Dokos wrote:
> Sebastien Vauban wrote:
>> Quite "simple": the following block generates an "Invalid face" error when
>> exported to HTML.
>>
>> #+begin_src sh
>> svn checkout http://svn/trunk/dev/ mydev
>> #+end_src
>>
>> This worked yesterday. Does it ring a bell to someone? Could
Hello,
Ab Cd writes:
> Please consider the following file :
>
> * TODO working
> ** TODO 1st part of the work
> CLOCK: [2012-01-05 jeu. 17:18]
>
> ** TODO second part of the work [0/3]
> - [ ] Task 1
> - [ ] Subtask 1
> - [ ] Subtask 2
> - [ ] Subtask 3
> - [ ] Task 2
>
Hi Jonathan,
Jonathan Arkell writes:
> Wow Bao! I am just checking out your org-jira2 project right now...
>
> Your thing was what my thing (contrib/lisp/org-jira.el) was going to
> become when I got the time... Then I got put on a project that didn't use
> Jira, and abandoned it (as mentioned e
Hi, OSiUX
OSiUX writes:
> El lun, 02 ene 2012, Bao Haojun decía:
>
>> Hi, all
>>
>> I have implemented org-jira.el, bringing org-mode and Jira system
>> together.
>>
>> Wrote a Wiki page for it on emacswiki:
>> http://www.emacswiki.org/emacs/OrgJiraMode
>>
>> Hope somebody find it useful, if
Hi, all
I have updated the org-jira.el as suggested by Bastien and Richard
Riley:
- Renamed jira2 to jiralib, to avoid confusion with the '2' and add the
note that it is a library (I looked to merge with jira.el, but backed
off as I myself do not use jira-mode).
- Fixed a bug for emacs versi
Hi, Org people.
There is a little problem I often observed, about bad vertical alignment
of text in Org mode buffers. Let me try to illustrate by mimicking from
an example right out from the window I currently see ;-).
Ellipses "[...]" have been added to make the example shorter.
--
Bao Haojun gmail.com> writes:
> I have updated the org-jira.el as suggested by Bastien and Richard
> Riley:
Amazing. Just 120 seconds ago I got out of a meeting where we talked about
using Jira more widely in our company, and I worried that I'd duplicate too much
between my org-mode journals and
Achim Gratz writes:
> It may still have to
> do with the environment — I start NTemacs from Cygwin to be able to use
> Cygwin's make and this combination is somewhat fragile.
... and that seems indeed to be the culprit, running NTemacs from the
Cygwin shell somehow causes Emacs to assume C:\ for
On Thu, Jan 5, 2012 at 9:01 PM, John Hendy wrote:
> On Thu, Jan 5, 2012 at 6:03 PM, Chris Malone wrote:
>
>> Hi John,
>>
>> I'm not sure what Org mode is doing behind the scenes, but I suspect
>> something is getting muddled because you specify both the src block file
>> header /and/ the output t
On Fri, Jan 6, 2012 at 10:59 AM, John Hendy wrote:
> On Thu, Jan 5, 2012 at 9:01 PM, John Hendy wrote:
>
>> On Thu, Jan 5, 2012 at 6:03 PM, Chris Malone wrote:
>>
>>> Hi John,
>>>
>>> I'm not sure what Org mode is doing behind the scenes, but I suspect
>>> something is getting muddled because yo
Torsten Wagner writes:
> Hmm...
> but this point is really interesting at least worse to write down in
> the manual.
> From my understanding a
> #+PROPERTY: var bar=2
> sets bar globally to 2
> somewhere and many lines and headers later
> #+PROPERTY: var bar=5
> would change this value to 5 for e
Achim Gratz writes:
> Achim Gratz writes:
>> It may still have to
>> do with the environment — I start NTemacs from Cygwin to be able to use
>> Cygwin's make and this combination is somewhat fragile.
>
> ... and that seems indeed to be the culprit, running NTemacs from the
> Cygwin shell somehow
Ken Williams writes:
> Bao Haojun gmail.com> writes:
>> I have updated the org-jira.el as suggested by Bastien and Richard
>> Riley:
>
> Amazing. Just 120 seconds ago I got out of a meeting where we talked about
> using Jira more widely in our company, and I worried that I'd duplicate too
> mu
`org-babel-result-end' bug fix and `org-babel-remove-result' regression tests.
* lisp/ob.el:
The code block below will currently act as though :results prepend
is set. This is due to `org-babel-result-end' being unable to
find the correct end of a raw result. This patch fixes that.
#+begin_src
Hi Martyn,
Unfortunately there is no way to remove raw results because there is no
way to know where the results end. While your patch will certainly work
most of the time, it will not work in cases where the results includes
an empty line, and ultimately I think any attempt to remove raw results
Bastien writes:
> Martyn Jago writes:
>
>> What appears to be a subtle difference in html export detail between
>> Emacs 22 and Emacs 23+ breaks these latest tests on Emacs 22.
>>
>> The attached patch fixes them (and the subtle difference is not relevant
>> to these tests).
>
> Applied, thanks!
Torsten Wagner writes:
> Hmm...
> but this point is really interesting at least worse to write down in the
> manual.
> From my understanding a
> #+PROPERTY: var bar=2
> sets bar globally to 2
> somewhere and many lines and headers later
> #+PROPERTY: var bar=5
> would change this value to 5 for
cbe...@tajo.ucsd.edu writes:
> Torsten Wagner writes:
>
>> Hmm...
>> but this point is really interesting at least worse to write down in
>> the manual.
>> From my understanding a
>> #+PROPERTY: var bar=2
>> sets bar globally to 2
>> somewhere and many lines and headers later
>> #+PROPERTY: var b
Eric Schulte writes:
Hi Eric
> Hi Martyn,
>
> Unfortunately there is no way to remove raw results because there is no
> way to know where the results end. While your patch will certainly work
> most of the time, it will not work in cases where the results includes
> an empty line, and ultimately
Hello,
pin...@iro.umontreal.ca (François Pinard) writes:
> There is a little problem I often observed, about bad vertical alignment
> of text in Org mode buffers.
How do you indent your text in the first place? Do you use C-j at the
end of line? Do you use `org-indent-mode'?
Also, what Org vers
Martyn Jago writes:
> Eric Schulte writes:
> Hi Eric
>
>> Hi Martyn,
>>
>> Unfortunately there is no way to remove raw results because there is no
>> way to know where the results end. While your patch will certainly work
>> most of the time, it will not work in cases where the results includes
Hi Eric
Eric Schulte writes:
[...]
>>
>> All the tests supplied with the exception of
>> `test-ob/org-babel-remove-result--results-raw' will still pass without
>> the change.
>>
>
> Alright, would you be willing to resubmit the patch including only those
> tests which should still apply? This
Nicolas Goaziou writes:
>> There is a little problem I often observed, about bad vertical
>> alignment of text in Org mode buffers.
> How do you indent your text in the first place?
I do not, at least so far that I know. Usually, I use a variable number
of stars before a headline, and write te
Applied, Thanks,
Martyn Jago writes:
> Hi Eric
>
> Eric Schulte writes:
>
>
> [...]
>
>>>
>>> All the tests supplied with the exception of
>>> `test-ob/org-babel-remove-result--results-raw' will still pass without
>>> the change.
>>>
>>
>> Alright, would you be willing to resubmit the patch inc
> "JK" == Joost Kremers writes:
JK> but org-drill isn't picking up the new entries. i've added a
JK> bunch of new entries to the file and they've all been given an
JK> :ID: property, but they are not being drilled. i'm sure i'm
JK> doing something wrong here, but i can't figur
pin...@iro.umontreal.ca (François Pinard) writes:
> I do not remember TAB has any indenting effect, but has you say, it
> might not be relevant when using `org-indent-mode'.
I take that back! :-)
TAB removes prefixing spaces if I happen to have any! Nice.
The problem I observed is that the ind
On Fri, Jan 06, 2012 at 09:27:53PM +0100, Milan Zamazal wrote:
> It may happen if there is some problem with the contents of the entries
> ("unrecognized" items are silently skipped). I was hit by a similar
> problem but once I realized what's wrong, org-drill started to work
> perfectly for me.
pin...@iro.umontreal.ca (François Pinard) writes:
> There is a little problem I often observed, about bad vertical
> alignment of text in Org mode buffers. [...] So, my real question :
> is there a quick way to correct the indentation?
I just got the problem again. OK, it seems a solution may
> * Class 7:00pm-9:00pm
><%% (org-class 2011 1 10 2011 4 10 2 8)>
Just figured out the problem. I was using 2011 and looking for the results in
agenda for 2012 (now). Classic "start of a new year" mistake. Doh!
35 matches
Mail list logo
