[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs Lisp's future
From: |
Eli Zaretskii |
Subject: |
Re: Emacs Lisp's future |
Date: |
Wed, 17 Sep 2014 18:03:45 +0300 |
> From: David Kastrup <address@hidden>
> Date: Wed, 17 Sep 2014 16:30:44 +0200
>
> One of the most costly changes was post 20.2 (?) when buffer and string
> positions became expressed as character offsets rather than byte
> offsets.
Yes, well, but that was more than 10 years ago (1997, if you are right
and it was 20.2).
- Re: Emacs Lisp's future, (continued)
Re: Emacs Lisp's future, Phillip Lord, 2014/09/17
- Re: Emacs Lisp's future, Nic Ferrier, 2014/09/17
- Re: Emacs Lisp's future, Stefan Monnier, 2014/09/17
- Re: Emacs Lisp's future, Phillip Lord, 2014/09/17
- Re: Emacs Lisp's future, Eli Zaretskii, 2014/09/17
- Re: Emacs Lisp's future, David Kastrup, 2014/09/17
- Re: Emacs Lisp's future,
Eli Zaretskii <=
Re: Emacs Lisp's future, Phillip Lord, 2014/09/17
performance isn't a concern in ... Emacs Lisp's future, Nic Ferrier, 2014/09/17
Re: performance isn't a concern in ... Emacs Lisp's future, David Kastrup, 2014/09/17
Re: Emacs Lisp's future, Thorsten Jolitz, 2014/09/18
Re: Emacs Lisp's future, Stefan Monnier, 2014/09/17
Re: Emacs Lisp's future, Taylan Ulrich Bayirli/Kammer, 2014/09/17
Re: Emacs Lisp's future, David Kastrup, 2014/09/17
Re: Emacs Lisp's future, Taylan Ulrich Bayirli/Kammer, 2014/09/17
Re: Emacs Lisp's future, Daniel Colascione, 2014/09/17
Re: Emacs Lisp's future, Stefan Monnier, 2014/09/17