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

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

Important features for editors

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

Contents

  Important features for editors cutems93 <ms2597@cornell.edu> - 2013-07-04 00:32 -0700
    Re: Important features for editors Νίκος <nikos@superhost.gr> - 2013-07-04 10:59 +0300
      Re: Important features for editors Dave Angel <davea@davea.name> - 2013-07-04 04:34 -0400
        Re: Important features for editors Νίκος <nikos@superhost.gr> - 2013-07-04 12:14 +0300
          Re: Important features for editors Chris Angelico <rosuav@gmail.com> - 2013-07-04 20:03 +1000
          Re: Important features for editors Robert Kern <robert.kern@gmail.com> - 2013-07-04 12:01 +0100
            Re: Important features for editors Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-04 15:48 +0000
          Re: Important features for editors Steve Simmons <square.steve@gmail.com> - 2013-07-04 14:33 +0100
            Re: Important features for editors Νίκος Γκρ33κ <nikos@superhost.gr> - 2013-07-04 16:36 +0300
              Re: Important features for editors feedthetroll@gmx.de - 2013-07-04 07:03 -0700
            Re: Important features for editors rusi <rustompmody@gmail.com> - 2013-07-04 07:02 -0700
              Re: Important features for editors Steve Simmons <square.steve@gmail.com> - 2013-07-04 16:35 +0100
              Re: Important features for editors Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-04 15:46 +0000
          Re: Important features for editors Grant Edwards <invalid@invalid.invalid> - 2013-07-04 18:40 +0000
            Re: Important features for editors Ferrous Cranus <nikos@superhost.gr> - 2013-07-04 21:52 +0300
              Re: Important features for editors Chris Angelico <rosuav@gmail.com> - 2013-07-05 07:59 +1000
              Re: Important features for editors Jason Swails <jason.swails@gmail.com> - 2013-07-04 17:59 -0400
              Re: Important features for editors Terry Reedy <tjreedy@udel.edu> - 2013-07-05 03:25 -0400
              Re: Important features for editors Grant Edwards <invalid@invalid.invalid> - 2013-07-05 14:11 +0000
      Re: Important features for editors Νίκος Gr33k <nikos@superhost.gr> - 2013-07-05 10:41 +0300
        Re: Important features for editors feedthetroll@gmx.de - 2013-07-05 01:28 -0700
    Re: Important features for editors Dave Angel <davea@davea.name> - 2013-07-04 05:02 -0400
    Re: Important features for editors Tim Chase <python.list@tim.thechases.com> - 2013-07-04 08:22 -0500
    Re: Important features for editors MRAB <python@mrabarnett.plus.com> - 2013-07-04 15:24 +0100
      Re: Important features for editors rurpy@yahoo.com - 2013-07-04 08:56 -0700
        Re: Important features for editors Steve Simmons <square.steve@gmail.com> - 2013-07-04 17:14 +0100
    Re: Important features for editors William Ray Wing <wrw@mac.com> - 2013-07-04 09:42 -0400
    Re: Important features for editors Tim Chase <python.list@tim.thechases.com> - 2013-07-04 16:03 -0500
    Re: Important features for editors Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-05 01:38 +0100
      Re: Important features for editors Roy Smith <roy@panix.com> - 2013-07-04 21:50 -0400
        Re: Important features for editors Cameron Simpson <cs@zip.com.au> - 2013-07-05 12:59 +1000
    Re: Important features for editors Dave Angel <davea@davea.name> - 2013-07-04 21:15 -0400
    Fwd: Important features for editors Göktuğ Kayaalp <goktug.kayaalp@gmail.com> - 2013-07-04 11:07 +0300
      Re: Important features for editors rusi <rustompmody@gmail.com> - 2013-07-05 05:12 -0700
        Re: Important features for editors Cameron Simpson <cs@zip.com.au> - 2013-07-06 09:06 +1000
        Re: Important features for editors Rustom Mody <rustompmody@gmail.com> - 2013-07-06 08:43 +0530
          Re: Important features for editors Roy Smith <roy@panix.com> - 2013-07-05 23:25 -0400
            Re: Important features for editors Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-06 05:35 +0100
              Re: Important features for editors rusi <rustompmody@gmail.com> - 2013-07-05 22:19 -0700
                Re: Important features for editors Joshua Landau <joshua.landau.ws@gmail.com> - 2013-07-06 07:19 +0100
        Re: Important features for editors Rustom Mody <rustompmody@gmail.com> - 2013-07-06 13:39 +0530
        Re: Important features for editors "Eric S. Johansson" <esj@harvee.org> - 2013-07-06 02:52 -0400
    Re: Important features for editors jussij@zeusedit.com - 2013-07-07 23:16 -0700
      Re: Important features for editors Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2013-07-08 06:37 +0000
        Re: Important features for editors Skip Montanaro <skip@pobox.com> - 2013-07-08 05:21 -0500
        Re: Important features for editors Sivaram Neelakantan <nsivaram.net@gmail.com> - 2013-07-08 19:54 +0530
        Re: Important features for editors Skip Montanaro <skip@pobox.com> - 2013-07-08 13:03 -0500

Page 3 of 3 — ← Prev page 1 2 [3]

#50052

[Multipart message — attachments visible in raw view] — view raw

On Sat, Jul 6, 2013 at 12:22 PM, Eric S. Johansson <esj@harvee.org> wrote:

> **
> On Fri, 05 Jul 2013 23:13:24 -0400, Rustom Mody <rustompmody@gmail.com>
> wrote:
>
> Yes...
> The fact that rms has crippling RSI should indicate that emacs' ergonomics
> is not right.
>
>
>
> As someone crippled by Emacs ( actual cause not known), I should also
> point out that RMS, instead of doing the responsible thing and using speech
> recognition software, burns the hands of other human beings by using them
> as biological speech recognition units.
>
>
Hope youve seen this
http://www.cs.princeton.edu/~arora/RSI.html

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

#50056

[Multipart message — attachments visible in raw view] — view raw

On Fri, 05 Jul 2013 23:13:24 -0400, Rustom Mody <rustompmody@gmail.com>  
wrote:

> Yes...
> The fact that rms has crippling RSI should indicate that emacs'  
> ergonomics is not right.


As someone crippled by Emacs ( actual cause not known), I should also  
point out that RMS, instead of doing the responsible thing and using  
speech recognition software, burns the hands of other human beings by  
using them as biological speech recognition units.

Now for me, an important feature for editor is the ability to command it,  
not by keystrokes but by function/method invocation. This is be the first  
step to reducing the disasters caused by misrecognition events injecting  
unintentional commands into an editor. For example, bring up a file in VI  
in close your eyes and type some string like "save file" or "end of line".  
What kind of damage do you get?

With an editor RPC, you can bypass all this damage. You turn off keystroke  
input at the start of a recognition event and all keyboard queue data is  
injected as characters. All commands are injected by the API.

There's a few other things, I need in a very tiny editor to help a part of  
my accessibility problem. One of the ways I deal with speech recognition  
user interfaces by creating tiny domain specific languages to solve a  
problem. You can say them, they are resilient in the face of  
misrecognition, edit them and you can replay them. Bunch of wins.

The tiny editor needs to use the right Windows edit control to work with  
NaturallySpeaking, save data so that I never have to think about it. It's  
always on disk, always safe. If I invoke a file by name, I get exactly one  
instance. And last, I want the ability to filter the contents of the  
editor through a bit of Python code so I can do transformations on opening  
the file or writing the file.

Further down the road, instead of the classic syntax highlighting, I need  
dynamic naming of features so that I can say things like "replace third  
argument", "modify index" for format local times using pattern.

I will admit the last one is a bit of a cheat because that's a subset of  
the domain specific notation I think that earlier. Not a solved problem :-)

So important feature editor change depending on your perspective, or  
should I say, state of impending disability. We all become disabled with  
age, just some of us age much faster than the rest of the population

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

#50122

On Thursday, July 4, 2013 5:32:59 PM UTC+10, cutems93 wrote:
> I am researching on editors for my own reference. 

On the Windows platform there is the Zeus editor: http://www.zeusedit.com/python.html

It does the standard syntax highlighting, code folding and smarting indent etc etc.

It's also scriptable (in Python) making which makes it highly configurable.

The keyboard is fully configurable and my keyboard mapping of choice is Brief (there's an EMACS keyboard mapping but no vim mapping).

I couldn't live without the keyboard macro record and playback.

The automatic ctags also helps to navigate large code bases.

User defined templates help with common programming constructs like if, while, for etc.

I never was a big fan of code folding but have grow to use that feature a lot.

NOTE: I'm the author of Zeus, it is shareware, runs natively on the Windows platform and can run on Linux using Wine.

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

#50123

On Sun, 07 Jul 2013 23:16:39 -0700, jussij wrote:

> I couldn't live without the keyboard macro record and playback.

I used to work with a programmer who couldn't live without his insulin 
injections. 


-- 
Steven

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

#50140

>> I couldn't live without the keyboard macro record and playback.
>
> I used to work with a programmer who couldn't live without his insulin
> injections.

Hyperbole aside, two of my most common "crutches" are Emacs macros and
bash history.  Given how useful macros are, I find it very odd that
recent versions of GNU Emacs dispensed with the old key binding to C-x
c.

Skip

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

#50163

On Mon, Jul 08 2013,Skip Montanaro wrote:

>>> I couldn't live without the keyboard macro record and playback.
>>
>> I used to work with a programmer who couldn't live without his insulin
>> injections.
>
> Hyperbole aside, two of my most common "crutches" are Emacs macros and
> bash history.  Given how useful macros are, I find it very odd that
> recent versions of GNU Emacs dispensed with the old key binding to C-x
> c.
>
> Skip

Wasn't it C-x ( ?  From the manual

   In addition to the <F3> and <F4> commands described above, Emacs
also supports an older set of key bindings for defining and executing
keyboard macros.  To begin a macro definition, type `C-x ('
(`kmacro-start-macro'); as with <F3>, a prefix argument appends this
definition to the last keyboard macro.  To end a macro definition, type
`C-x )' (`kmacro-end-macro').  To execute the most recent macro, type
`C-x e' (`kmacro-end-and-call-macro').  If you enter `C-x e' while


 sivaram
 -- 

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

#50166

> Wasn't it C-x ( ?  From the manual
>
>    In addition to the <F3> and <F4> commands described above, Emacs
> also supports an older set of key bindings for defining and executing
> keyboard macros.  To begin a macro definition, type `C-x ('
> (`kmacro-start-macro'); as with <F3>, a prefix argument appends this
> definition to the last keyboard macro.  To end a macro definition, type
> `C-x )' (`kmacro-end-macro').  To execute the most recent macro, type
> `C-x e' (`kmacro-end-and-call-macro').  If you enter `C-x e' while

(We are getting a bit off-topic, but I suppose that's not too unusual...)

Thanks for pointing that out.

Things moved around on me while I wasn't looking.  For a long, long
time, I have used C-x e as a prefix for a number of ediff commands.  I
imagine that comes from my old XEmacs habits.  C-x c was always bound
to call-last-kbd-macro, and I'm pretty sure it used to be that way in
older versions of GNU Emacs.  The kmacro package probably appeared
while I was using XEmacs.  I found that in the interim, the GNU folks
inserted all sorts of extra keys, so that many things I used to do
with two keystrokes are now done with three.  I understand the logic
of what they did (easier to increase the number of keystrokes required
for some commands than to increase the number of keys on the
keyboard), but prefer many things the way I used to do them.

So, call-last-kbd-macro got unbound in the GNU switch to kmacro, and
reasserting my preference for the way I called ediff commands meant
that the new spelling of the kmacro stuff got dropped.  I do use C-x (
and C-x ) to define macros.

Skip

[toc] | [prev] | [standalone]

Page 3 of 3 — ← Prev page 1 2 [3]

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

csiph-web