On May 7, 2010, at 10:30 AM, Michael Sperber wrote:
Carsten Dominik writes:
any progress with integrating noutline.el into XEmacs?
Yes: I've tweaked it (and its dependents) appropriately, committed
it to
the packages repository, and it's now in pre-release. My intention
was
to e-mai
Carsten Dominik writes:
> any progress with integrating noutline.el into XEmacs?
Yes: I've tweaked it (and its dependents) appropriately, committed it to
the packages repository, and it's now in pre-release. My intention was
to e-mail you as soon as there was an official release of the relevan
Hi Michael,
any progress with integrating noutline.el into XEmacs?
Thanks
- Carsten
On Apr 19, 2010, at 1:00 PM, Michael Sperber wrote:
Carsten Dominik writes:
The compromise for me would be this:
- You fix the things above.
- I leave the rest of the necessary compatibility code in
- I
Hi Michael,
thank you very much for this! I have (sort-of) applied the patch.
Please try to make your patches always against the latest git version
of Org-mode - we are moveing very fast.
- Carsten
On Apr 23, 2010, at 5:50 PM, Michael Sperber wrote:
Carsten Dominik writes:
4. Can you
Carsten Dominik writes:
> 4. Can you make XEmacs understand mouse-3 instead of button3 ? Or
>maybe it does understand these by now?
It actually does this now. I've attached a patch that eliminates the
relevant featurep conditionals.
--
Cheers =8-} Mike
Friede, Völkerverständigung und üb
On Apr 19, 2010, at 1:00 PM, Michael Sperber wrote:
Carsten Dominik writes:
The compromise for me would be this:
- You fix the things above.
- I leave the rest of the necessary compatibility code in
- I program any new features with whatever is available
in Emacs 22/23 and rely on you to
OK.
- Carsten
On Apr 19, 2010, at 5:54 PM, Michael Sperber wrote:
Carsten Dominik writes:
That is acceptable - but I think that making BUFFER default to
(current-buffer) does make a lot of sense - which is why making that
argument optional in XEmacs is a good idea anyway.
It would - but
Carsten Dominik writes:
> That is acceptable - but I think that making BUFFER default to
> (current-buffer) does make a lot of sense - which is why making that
> argument optional in XEmacs is a good idea anyway.
It would - but the problem is that in XEmacs, an omitted BUFFER argument
means som
On Apr 19, 2010, at 1:19 PM, Michael Sperber wrote:
One more thing: Are patches like this one acceptable? (Needed to make
yesterday's checkout work on XEmacs)
diff --git a/lisp/org.el b/lisp/org.el
index 7cad962..5cca11e 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -17743,7 +17743,7 @@ the f
One more thing: Are patches like this one acceptable? (Needed to make
yesterday's checkout work on XEmacs)
diff --git a/lisp/org.el b/lisp/org.el
index 7cad962..5cca11e 100644
--- a/lisp/org.el
+++ b/lisp/org.el
@@ -17743,7 +17743,7 @@ the functionality can be provided as a fall-back.")
(org-s
Carsten Dominik writes:
> The compromise for me would be this:
>
> - You fix the things above.
> - I leave the rest of the necessary compatibility code in
> - I program any new features with whatever is available
> in Emacs 22/23 and rely on you to make it XEmacs compatible.
That would be
Hi Carsten,
many thanks for your e-mail! (And many thanks for your work on
org-mode, which is the best piece of software I've started using for a
few years.)
Carsten Dominik writes:
> However, I have recently more and more the feeling how having to
> cater for several Emacs versions is a drag
Hi Michael,
On Apr 18, 2010, at 10:22 AM, Michael Sperber wrote:
Hi Carsten,
many thanks for your e-mail! (And many thanks for your work on
org-mode, which is the best piece of software I've started using for a
few years.)
Carsten Dominik writes:
However, I have recently more and more th
On Apr 17, 2010, at 5:39 PM, Michael Sperber wrote:
Carsten Dominik writes:
If you object to such a development, please step into this
discussion.
I do - I'm an avoid org-mode user, an XEmacs maintainer. and I'd be
happy to help support XEmacs, if that would help change your mind.
Hi M
Carsten Dominik writes:
> If you object to such a development, please step into this
> discussion.
I do - I'm an avoid org-mode user, an XEmacs maintainer. and I'd be
happy to help support XEmacs, if that would help change your mind.
--
Cheers =8-} Mike
Friede, Völkerverständigung und überha
Fixed, thanks
- Carsten
On Apr 16, 2010, at 9:15 PM, Bernt Hansen wrote:
Another bug.
Attempting to get a clock report in the agenda. (R in the daily
agenda)
-Bernt
Debugger entered--Lisp error: (void-function org-dblock-write:)
org-dblock-write:((:name nil :link nil :maxlevel 2 :tstar
Another bug.
Attempting to get a clock report in the agenda. (R in the daily agenda)
-Bernt
Debugger entered--Lisp error: (void-function org-dblock-write:)
org-dblock-write:((:name nil :link nil :maxlevel 2 :tstart 733878 :tend
733879 :scope agenda :indentation-column 0 :content "\n"))
fun
There are more new changes on that branch - pretty much complete now,
I think.
Thanks for all your help.
- Carsten
___
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mail
On Apr 16, 2010, at 4:42 PM, Bernt Hansen wrote:
Thanks. I'll beat on it some more :)
What a team! :-)
Regards,
Bernt
Carsten Dominik writes:
Hi Bernt, thanks a lot for this report - I believe I know
what was causing this and have fixed it, still on that branch of
course.
- Carste
Thanks. I'll beat on it some more :)
Regards,
Bernt
Carsten Dominik writes:
> Hi Bernt, thanks a lot for this report - I believe I know
> what was causing this and have fixed it, still on that branch of course.
>
> - Carsten
>
> On Apr 16, 2010, at 3:13 PM, Bernt Hansen wrote:
>
>> Found a bug
Hi Bernt, thanks a lot for this report - I believe I know
what was causing this and have fixed it, still on that branch of course.
- Carsten
On Apr 16, 2010, at 3:13 PM, Bernt Hansen wrote:
Found a bug.
I'll switch to this branch for regular work to try to find issues with
it.
I'm running it
Rémi Vanicat writes:
> Sebastian Rose writes:
>
>> * One git question:
>>
>> When I pulled, I got the message, that there is a new branch. But that
>> branch did not show up in the list `git branch' gives me.
>
> use git branch -r (or git branch -a) to list remote (or all branch)
>
>> Then I did:
Quoting Carsten Dominik :
Hi,
I have made a test version of Org with the compatibility code
for XEmacs and without some of the left-over compatibility
code for Emacs 21.
I would appreciate if some people could check out the
`remove-compatibility-code' branch from repo.or.cz and report back
if
Sebastian Rose writes:
> * One git question:
>
> When I pulled, I got the message, that there is a new branch. But that
> branch did not show up in the list `git branch' gives me.
use git branch -r (or git branch -a) to list remote (or all branch)
> Then I did:
> sh$ git checkout origin/remove-
Found a bug.
I'll switch to this branch for regular work to try to find issues with
it.
I'm running it on two versions of emacs uncompiled:
GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11) of 2008-11-09
on raven, modified by Debian
and
GNU Emacs 23.1.50.1 (i386-mingw-nt5.1.2600) of 2
On 16.04.2010 12:26, Carsten Dominik wrote:
> Hi,
>
> I have made a test version of Org with the compatibility code
> for XEmacs and without some of the left-over compatibility
> code for Emacs 21.
>
> I would appreciate if some people could check out the
> `remove-compatibility-code' branch from
Carsten Dominik writes:
> I would appreciate if some people could check out the
> `remove-compatibility-code' branch from repo.or.cz and report back
> if they experience any problems with Emacs 22, 23, and 24, either
> during compilation or while running.
I'm testing it with emacs 24.
The build
Hi Carsten,
Carsten Dominik writes:
> I have made a test version of Org with the compatibility code
> for XEmacs and without some of the left-over compatibility
> code for Emacs 21.
>
> I would appreciate if some people could check out the
> `remove-compatibility-code' branch from repo.or.cz and
On Apr 16, 2010, at 12:26 PM, Carsten Dominik wrote:
Hi,
I have made a test version of Org with the compatibility code
I am such a bad writer.
I mean with that compatibility code *removed*!
- Carsten
for XEmacs and without some of the left-over compatibility
code for Emacs 21.
I would
Hi,
I have made a test version of Org with the compatibility code
for XEmacs and without some of the left-over compatibility
code for Emacs 21.
I would appreciate if some people could check out the
`remove-compatibility-code' branch from repo.or.cz and report back
if they experience any problems
30 matches
Mail list logo
