Hi Nicolas,
* Nicolas Goaziou n.goaz...@gmail.com [22. May. 2014]:
Bastien b...@gnu.org writes:
Yes -- I suggest we simply put this aside for the moment.
Well, actually it required more work than I thought. Here is the patch,
with some documentation. I didn't test it thoroughly, so feedback is
Hi all,
I'm slowly securing a bit more time for Org. Don't expect
miracles before the beginning of the next week, though.
Nicolas kindly accepted to dedicate more time to the general
maintainance of Org during the weeks where I could not spent
as much time as I wanted -- let's join me in
Hi
guys, I just wanted to thank you all for the great work!I'm
a theoretical physicist and I regularly use org-mode for almost every
aspect of my research.All the best,Domenico Orlando--
Domenico
Orlando, CERN Fellow Theory division
phone: +41 22 767 29 59
Patrick O'Neill p...@umbc.edu wrote:
I just wanted to give a quick word of thanks to Bernt Hansen and
everyone else answering questions on the emacs-orgmode list. Since
the mailing list is publicly archived, answered questions can remain
useful to others long after the original respondents
Nick Dokos nicholas.do...@hp.com wrote:
Patrick O'Neill p...@umbc.edu wrote:
I just wanted to give a quick word of thanks to Bernt Hansen and
everyone else answering questions on the emacs-orgmode list.=C2=A0 Since
the mailing list is publicly archived, answered questions can remain
Nick Dokos nicholas.do...@hp.com wrote:
#+TBLFM: $1=3Dfind(@address@hidden,$2)
Address rewriting by the list/archive manager: the original formula was
#+TBLFM: $1=find(@I$2..@III$2,$2)
Never mind ;-)
Nick
PS. But corruptions like this are a problem if we want to use the
list
Patrick O'Neill p...@umbc.edu writes:
I just wanted to give a quick word of thanks to Bernt Hansen and
everyone else answering questions on the emacs-orgmode list.
You're most welcome :). I've completely forgotten all about this
(ancient) post.
Regards,
Bernt
I just wanted to give a quick word of thanks to Bernt Hansen and everyone
else answering questions on the emacs-orgmode list. Since the mailing list
is publicly archived, answered questions can remain useful to others long
after the original respondents have probably forgotten about them. This
Bastien b...@altern.org writes:
Hi Suvayu,
thanks for sharing this suggestion and to make it so clear.
I understand the model you describe and I see why it's appropriate for
projects like git -- as IIUC, your proposal is very close to the one
described by git's maintainer.
- The latest
On Tue, Jul 19, 2011 at 2:29 PM, Bernt Hansen be...@norang.ca wrote:
With Suvayu's model you would only merge for the release and that means
the new master won't have the same level of testing exposure before a
release is created. We don't have full coverage of org-mode's features
in the ERT
Hi Suvayu,
thanks for sharing this suggestion and to make it so clear.
I understand the model you describe and I see why it's appropriate for
projects like git -- as IIUC, your proposal is very close to the one
described by git's maintainer.
Let me summarize my ideas about how we should use git
Hi Bastien,
On Mon, Jul 11, 2011 at 6:50 PM, Bastien b...@altern.org wrote:
This additional work is only worth undertaking when people are
*really* using the branches to collaborate -- which is quite unlikely to
happen given the three reasons above
I failed to consider the above bit of
Hi Bastien,
On Sat, 09 Jul 2011 10:44:45 +0200
Bastien b...@altern.org wrote:
http://www.kernel.org/pub/software/scm/git/docs/howto/maintain-git.txt
Nice read, thanks.
I guess the relevance of such a development model mainly depends on
how many developers are trying to collaborate,
Hi Suvayu,
Suvayu Ali fatkasuvayu+li...@gmail.com writes:
Maybe the development model followed by git itself would be a good
solution (merges instead of cherry-picking)? Although I fear org is a
much smaller project compared to git and it could be an overkill.
Hi Achim,
Achim Gratz strom...@nexgo.de writes:
Pure fixes should probably be applied on top of maint and then merged
into master (not cherry-picked from master to maint, this would create
duplicate history). On occasion this might produce a merge conflict,
but these instances should be
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
Thanks for finding this error Torsten! I've just pushed up a fix.
Thanks.
Bastien,
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
Bastien b...@altern.org 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
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
Martyn
Hi Nick,
Nick Dokos nicholas.do...@hp.com 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
Hi Bastien,
On Fri, 08 Jul 2011 11:08:07 +0200
Bastien b...@altern.org 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
Bastien b...@altern.org 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
Dear Martyn Jago,
Congratulations to the Lilypond support included in the new Org version 7.6!
For someone who uses both Org-mode and Lilypond anyway (like me :), this is
great to have!
Some brief comments. Support for additional languages like Lilypond and also
awk should be celebrated by
Hi Torsten,
Torsten Anders torsten.and...@beds.ac.uk writes:
Some brief comments. Support for additional languages like Lilypond and
also awk should be celebrated by including them in the list of languages in
the documentation (http://orgmode.org/org.html#Languages).
Fixed in latest org.texi
Bastien b...@altern.org writes:
Hi Torsten,
Torsten Anders torsten.and...@beds.ac.uk writes:
Some brief comments. Support for additional languages like Lilypond and
also awk should be celebrated by including them in the list of languages in
the documentation
24 matches
Mail list logo