[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C and Emacs Lisp code parts
From: |
Eli Zaretskii |
Subject: |
Re: C and Emacs Lisp code parts |
Date: |
Sat, 02 Jul 2016 09:32:07 +0300 |
> Cc: Eli Zaretskii <address@hidden>, address@hidden
> From: Andreas Röhler <address@hidden>
> Date: Fri, 1 Jul 2016 22:04:08 +0200
>
> BTW think at the fate of bazaar. Here Python was at stake and for a time
> it growed quickly. Assume the easiness of Python as a factor of success.
> But finally a C-based tool won the race, while bazaar went into bigger
> and bigger issues. Why? :-)
Bazaar is fast enough. Its dropping out of favor was due to the fact
that that it stopped being actively maintained.
- Re: C and Emacs Lisp code parts, (continued)
- Re: C and Emacs Lisp code parts, Eli Zaretskii, 2016/07/02
- Re: C and Emacs Lisp code parts, Alan Mackenzie, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Alan Mackenzie, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/01
- Re: C and Emacs Lisp code parts, Davis Herring, 2016/07/01
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/02
- Re: C and Emacs Lisp code parts, Paul Eggert, 2016/07/02
- Re: C and Emacs Lisp code parts, Davis Herring, 2016/07/05
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/05
- Re: C and Emacs Lisp code parts,
Eli Zaretskii <=
- Re: C and Emacs Lisp code parts, Andreas Röhler, 2016/07/02
- Re: C and Emacs Lisp code parts, Eli Zaretskii, 2016/07/02
Re: C and Emacs Lisp code parts, Tom Tromey, 2016/07/01