Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #94758 > unrolled thread

Re: Gmail eats Python

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Gmail eats Python Cameron Simpson <cs@zip.com.au> - 2015-07-30 10:45 +1000
    Re: Gmail eats Python Rustom Mody <rustompmody@gmail.com> - 2015-07-29 19:21 -0700
      Re: Gmail eats Python wxjmfauth@gmail.com - 2015-07-29 23:31 -0700

#94758 — Re: Gmail eats Python

On 29Jul2015 18:32, Laura Creighton <lac@openend.se> wrote:
>In a message of Tue, 28 Jul 2015 20:35:15 -0700, Rustom Mody writes:
>>- I should not have to customize emacs so that CTRL/A, CTRL/E, CTRL/N, and
>>CTRL/P continue to work the way they've done since the mid-1970s.
>>
>>etc etc
>>--------------------------------
>>¹ emacs 18 dates from around 1992 (!!)
>
>No, the original one was written in 1976.
>
>These control characters are the very basic move characters in emacs.
>People have always been free to remap them if they want them to do
>something else, but waking up in the morning and discovering that you
>cannot move to the front of your current line, to the end ot it, one line
>up and one line down  because somebody has changed this ***for everybody***
>would get me quite upset, too.

Yeah, I'd be annoyed too. I'm a vi user, but use the emacs mode for shell 
command line editing as it is modeless. ^A, ^E, ^P and ^N are really quite 
critical.

>Laura (happy emacs user since 1979)

Cheers,
Cameron Simpson <cs@zip.com.au> (happy vi user since 1985)

English is a living language, but simple illiteracy is no basis for
linguistic evolution.   - Dwight MacDonald

[toc] | [next] | [standalone]

#94759

On Thursday, July 30, 2015 at 6:15:56 AM UTC+5:30, Cameron Simpson wrote:
> On 29Jul2015 18:32, Laura Creighton  wrote:
> >These control characters are the very basic move characters in emacs.
> >People have always been free to remap them if they want them to do
> >something else, but waking up in the morning and discovering that you
> >cannot move to the front of your current line, to the end ot it, one line
> >up and one line down  because somebody has changed this ***for everybody***
> >would get me quite upset, too.
> 
> Yeah, I'd be annoyed too. I'm a vi user, but use the emacs mode for shell 
> command line editing as it is modeless. ^A, ^E, ^P and ^N are really quite 
> critical.
> 
> >Laura (happy emacs user since 1979)
> 
> Cheers,
> Cameron Simpson (happy vi user since 1985)
> 
> English is a living language, but simple illiteracy is no basis for
> linguistic evolution.   - Dwight MacDonald

That footer says it best:
Some stability is expected, also some change.
Finding a sweetspot midway is hard and very necessary

BTW I think python does a better job -- 2→3 transition than most other
long-lived projects.
Emacs is too much on the conservative side.
Haskell is too  much on the 'progress-is-heaven' side.

[toc] | [prev] | [next] | [standalone]

#94764

> > On 29Jul2015 18:32, Laura Creighton  wrote:

> BTW I think python does a better job -- 2→3 transition than most other
> long-lived projects.
> Emacs is too much on the conservative side.
> Haskell is too  much on the 'progress-is-heaven' side.

Python 3 will never work because its "Characters
Encoding Model" is wrong by design.

It's a child play to illustrate this.

jmf

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web