Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #110069 > unrolled thread
| Started by | Chris <cspears2002@yahoo.com> |
|---|---|
| First post | 2016-06-17 16:52 -0700 |
| Last post | 2016-07-06 03:27 -0700 |
| Articles | 8 on this page of 88 — 29 participants |
Back to article view | Back to comp.lang.python
best text editor for programming Python on a Mac Chris <cspears2002@yahoo.com> - 2016-06-17 16:52 -0700
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-17 17:19 -0700
Re: best text editor for programming Python on a Mac Ned Batchelder <ned@nedbatchelder.com> - 2016-06-17 17:36 -0700
Re: best text editor for programming Python on a Mac wxjmfauth@gmail.com - 2016-06-20 01:39 -0700
Re: best text editor for programming Python on a Mac MRAB <python@mrabarnett.plus.com> - 2016-06-18 01:58 +0100
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-17 18:50 -0700
Re: best text editor for programming Python on a Mac Steven D'Aprano <steve@pearwood.info> - 2016-06-18 12:05 +1000
Re: best text editor for programming Python on a Mac Steven D'Aprano <steve@pearwood.info> - 2016-06-18 11:55 +1000
Re: best text editor for programming Python on a Mac Zachary Ware <zachary.ware+pylist@gmail.com> - 2016-06-17 20:59 -0500
Re: best text editor for programming Python on a Mac support@ecourierz.com - 2016-06-17 22:18 -0700
Re: best text editor for programming Python on a Mac Michael Vilain <mev94303y@yahoo.com> - 2016-06-18 00:04 -0700
Re: best text editor for programming Python on a Mac Terry Reedy <tjreedy@udel.edu> - 2016-06-18 05:09 -0400
Re: best text editor for programming Python on a Mac Marko Rauhamaa <marko@pacujo.net> - 2016-06-18 12:40 +0300
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-18 03:08 -0700
Re: best text editor for programming Python on a Mac Michael Vilain <mev94303y@yahoo.com> - 2016-06-18 07:12 -0700
Re: best text editor for programming Python on a Mac alister <alister.ware@ntlworld.com> - 2016-06-18 13:22 +0000
Re: best text editor for programming Python on a Mac Michael Vilain <mev94303y@yahoo.com> - 2016-06-18 07:08 -0700
Re: best text editor for programming Python on a Mac Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-18 16:08 -0400
Re: best text editor for programming Python on a Mac Rustom Mody <rustompmody@gmail.com> - 2016-06-18 09:02 -0700
Re: best text editor for programming Python on a Mac Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-06-20 10:38 +1200
best text editor for programming Python on a Mac MrJean1 <MrJean1@gmail.com> - 2016-06-18 08:52 -0700
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-18 17:07 -0600
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-18 17:12 -0700
Re: best text editor for programming Python on a Mac Joel Goldstick <joel.goldstick@gmail.com> - 2016-06-18 20:26 -0400
Re: best text editor for programming Python on a Mac Pete Forman <petef4+usenet@gmail.com> - 2016-06-19 11:41 +0100
Re: best text editor for programming Python on a Mac Marko Rauhamaa <marko@pacujo.net> - 2016-06-19 15:57 +0300
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-19 07:19 -0600
Re: best text editor for programming Python on a Mac Rustom Mody <rustompmody@gmail.com> - 2016-06-19 09:20 -0700
Re: best text editor for programming Python on a Mac Christian Gollwitzer <auriocus@gmx.de> - 2016-06-19 20:06 +0200
Re: best text editor for programming Python on a Mac Rustom Mody <rustompmody@gmail.com> - 2016-06-19 11:13 -0700
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-19 13:04 -0600
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-19 12:58 -0600
Re: best text editor for programming Python on a Mac Steven D'Aprano <steve@pearwood.info> - 2016-06-20 11:32 +1000
ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-19 19:07 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Steven D'Aprano <steve@pearwood.info> - 2016-06-20 13:29 +1000
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Phil Boutros <philb@philb.ca> - 2016-06-20 04:30 +0000
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-19 22:03 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Random832 <random832@fastmail.com> - 2016-06-20 02:04 -0400
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-20 07:00 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-20 00:57 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2016-06-20 20:24 +1000
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Grant Edwards <grant.b.edwards@gmail.com> - 2016-06-20 14:23 +0000
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Steven D'Aprano <steve@pearwood.info> - 2016-06-21 01:00 +1000
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-20 08:12 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-19 21:36 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-19 21:41 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Larry Hudson <orgnut@yahoo.com> - 2016-06-21 00:40 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Marko Rauhamaa <marko@pacujo.net> - 2016-06-21 11:35 +0300
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-21 03:46 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Marko Rauhamaa <marko@pacujo.net> - 2016-06-21 16:08 +0300
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-21 06:56 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-21 07:11 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-22 19:01 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-22 19:07 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Rustom Mody <rustompmody@gmail.com> - 2016-06-21 07:29 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Marko Rauhamaa <marko@pacujo.net> - 2016-06-21 21:56 +0300
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Tim Chase <python.list@tim.thechases.com> - 2016-06-21 14:42 -0500
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Marko Rauhamaa <marko@pacujo.net> - 2016-06-21 23:08 +0300
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-22 00:55 -0700
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Tim Chase <python.list@tim.thechases.com> - 2016-06-22 06:09 -0500
Re: ASCII or Unicode? (was best text editor for programming Python on a Mac) Tim Chase <python.list@tim.thechases.com> - 2016-06-21 10:08 -0500
Re: best text editor for programming Python on a Mac Tim Chase <python.list@tim.thechases.com> - 2016-06-19 21:41 -0500
Re: best text editor for programming Python on a Mac Quivis <quivis@domain.invalid> - 2016-06-19 21:21 +0000
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-19 16:15 -0600
Re: best text editor for programming Python on a Mac Christian Gollwitzer <auriocus@gmx.de> - 2016-06-20 09:37 +0200
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-18 18:50 -0600
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-18 19:01 -0600
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-18 20:09 -0600
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-18 19:51 -0700
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-18 22:54 -0600
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-18 22:57 -0700
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-18 22:56 -0600
Re: best text editor for programming Python on a Mac Tim Chase <python.list@tim.thechases.com> - 2016-06-19 06:36 -0500
Re: best text editor for programming Python on a Mac Christian Gollwitzer <auriocus@gmx.de> - 2016-06-19 09:13 +0200
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-19 00:34 -0700
Re: best text editor for programming Python on a Mac Rustom Mody <rustompmody@gmail.com> - 2016-06-19 00:47 -0700
Re: best text editor for programming Python on a Mac Christian Gollwitzer <auriocus@gmx.de> - 2016-06-19 09:57 +0200
Re: best text editor for programming Python on a Mac Michael Torrie <torriem@gmail.com> - 2016-06-19 07:23 -0600
Re: best text editor for programming Python on a Mac alister <alister.ware@ntlworld.com> - 2016-06-20 08:30 +0000
Re: best text editor for programming Python on a Mac Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2016-06-20 10:44 +1200
Re: best text editor for programming Python on a Mac Lawrence D’Oliveiro <lawrencedo99@gmail.com> - 2016-06-20 00:59 -0700
Re: best text editor for programming Python on a Mac Random832 <random832@fastmail.com> - 2016-06-20 09:26 -0400
Re: best text editor for programming Python on a Mac Christian Gollwitzer <auriocus@gmx.de> - 2016-06-20 15:36 +0200
Re: best text editor for programming Python on a Mac Rustom Mody <rustompmody@gmail.com> - 2016-06-20 06:48 -0700
Re: best text editor for programming Python on a Mac Christian Gollwitzer <auriocus@gmx.de> - 2016-06-20 16:03 +0200
best text editor for programming Python on a Mac drednot57 <dpresley@midiowa.net> - 2016-06-18 19:48 -0700
Re: best text editor for programming Python on a Mac jennifer.greeen@gmail.com - 2016-07-06 03:25 -0700
Re: best text editor for programming Python on a Mac jennifer.greeen@gmail.com - 2016-07-06 03:27 -0700
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
| From | Lawrence D’Oliveiro <lawrencedo99@gmail.com> |
|---|---|
| Date | 2016-06-20 00:59 -0700 |
| Message-ID | <8c3bd89d-b560-4adb-8c7e-c6de7b364ac3@googlegroups.com> |
| In reply to | #110161 |
On Monday, June 20, 2016 at 10:45:08 AM UTC+12, Gregory Ewing wrote: > > Lawrence D’Oliveiro wrote: > >> But not vi/vim. It only lets you place your cursor *on* a character, not >> *in-between* characters. > > That's because the terminals it was designed to work on > didn't have any way of displaying a cursor between two > characters. That’s a dumb excuse. I’ve been using full-screen editors since 1979, on VT52 and later VT100 and then VT220 terminals, until text-mode terminals became obsolete. They all worked the way Emacs does, and vi does not.
[toc] | [prev] | [next] | [standalone]
| From | Random832 <random832@fastmail.com> |
|---|---|
| Date | 2016-06-20 09:26 -0400 |
| Message-ID | <mailman.153.1466429212.2288.python-list@python.org> |
| In reply to | #110161 |
On Sun, Jun 19, 2016, at 18:44, Gregory Ewing wrote: > Lawrence D’Oliveiro wrote: > > But not vi/vim. It only lets you place your cursor *on* a character, not > > *in-between* characters. > > That's because the terminals it was designed to work on > didn't have any way of displaying a cursor between two > characters. Emacs is the same (except it doesn't go as > far as having two different insertion modes -- you just > think of the insertion point as being to the left of > the character that the cursor is on). So, basically, Emacs is *not* the same. The point is that in vim you can't position the normal-mode cursor in such a way that inserted characters are inserted at the end of the line. How the cursor is displayed has nothing to do with it. And, insertion is to the left of the character that the cursor is on in vim, too. That's why the "a" command moves the cursor. > I would say that's about the *least* weird thing about > vi[m] though... :-(
[toc] | [prev] | [next] | [standalone]
| From | Christian Gollwitzer <auriocus@gmx.de> |
|---|---|
| Date | 2016-06-20 15:36 +0200 |
| Message-ID | <nk8rhe$sfa$1@dont-email.me> |
| In reply to | #110195 |
Am 20.06.16 um 15:26 schrieb Random832: > The point is that in vim you > can't position the normal-mode cursor in such a way that inserted > characters are inserted at the end of the line. But you can press i at the end of the line, then arrow-right, which positions the cursor over the empty space after the line, and type. Try it. In vim this works, because vim understands cursor keys. In original vi not (there were no cursor keys on the old terminals). Usually, when editing in vim, you don't leave the insert mode because you can use the "special" keys as well as mouse actions to perform usual editing tasks. Leaving insert mode is only necessary to run a command. Christian
[toc] | [prev] | [next] | [standalone]
| From | Rustom Mody <rustompmody@gmail.com> |
|---|---|
| Date | 2016-06-20 06:48 -0700 |
| Message-ID | <5519d657-2405-4236-bfec-e5fbeb2b54f1@googlegroups.com> |
| In reply to | #110197 |
On Monday, June 20, 2016 at 7:06:57 PM UTC+5:30, Christian Gollwitzer wrote: > Am 20.06.16 um 15:26 schrieb Random832: > > The point is that in vim you > > can't position the normal-mode cursor in such a way that inserted > > characters are inserted at the end of the line. > > But you can press i at the end of the line, then arrow-right, which > positions the cursor over the empty space after the line, and type. Try > it. In vim this works, because vim understands cursor keys. In original > vi not (there were no cursor keys on the old terminals). Usually, when > editing in vim, you don't leave the insert mode because you can use the > "special" keys as well as mouse actions to perform usual editing tasks. > Leaving insert mode is only necessary to run a command. True and false (if one allows for vi = vim) In the default vi that comes with ubuntu (vi-tiny??) giving a arrow in insert mode enters all kinds of (control?) garbage. In (full) vim I guess its true
[toc] | [prev] | [next] | [standalone]
| From | Christian Gollwitzer <auriocus@gmx.de> |
|---|---|
| Date | 2016-06-20 16:03 +0200 |
| Message-ID | <nk8t3j$2bo$1@dont-email.me> |
| In reply to | #110199 |
Am 20.06.16 um 15:48 schrieb Rustom Mody: > On Monday, June 20, 2016 at 7:06:57 PM UTC+5:30, Christian Gollwitzer wrote: >> Am 20.06.16 um 15:26 schrieb Random832: >>> The point is that in vim you >>> can't position the normal-mode cursor in such a way that inserted >>> characters are inserted at the end of the line. >> >> But you can press i at the end of the line, then arrow-right, which >> positions the cursor over the empty space after the line, and type. Try >> it. In vim this works, because vim understands cursor keys. In original >> vi not (there were no cursor keys on the old terminals). Usually, when >> editing in vim, you don't leave the insert mode because you can use the >> "special" keys as well as mouse actions to perform usual editing tasks. >> Leaving insert mode is only necessary to run a command. > > True and false (if one allows for vi = vim) He wrote "in vim", which I assumed was on purpose. > In the default vi that comes with ubuntu (vi-tiny??) > giving a arrow in insert mode enters all kinds of (control?) garbage. Yes I know this crappy behaviour which has no place on a current desktop. Maybe it is just a setting? Try ":set nocompatible" which should turn on standard edit keys, if this is really a vim variant and not something else like elvis. > In (full) vim I guess its true Definitely. I wouldn't use an editor which requires me to learn special commands that are available as standard keys on a modern keyboard. Christian
[toc] | [prev] | [next] | [standalone]
| From | drednot57 <dpresley@midiowa.net> |
|---|---|
| Date | 2016-06-18 19:48 -0700 |
| Message-ID | <ab089f58-658b-48cc-aedf-f3e01019b474@googlegroups.com> |
| In reply to | #110069 |
My go to python editor is Dr. Python. Coded in Python with the wxPython GUI library, but I use Linux.
[toc] | [prev] | [next] | [standalone]
| From | jennifer.greeen@gmail.com |
|---|---|
| Date | 2016-07-06 03:25 -0700 |
| Message-ID | <babb5b3a-a964-4b08-94a3-29c669aacff9@googlegroups.com> |
| In reply to | #110069 |
I don't know anything about editors for coding, but as a writer that often use text editors (and I have seen them a lot!) I'd suggest you browsing this review site where you can find some cool apps <a href="http://besttexteditor.com">besttexteditor.com</a>
[toc] | [prev] | [next] | [standalone]
| From | jennifer.greeen@gmail.com |
|---|---|
| Date | 2016-07-06 03:27 -0700 |
| Message-ID | <11882431-dc45-433f-8455-0aa9d455a8ca@googlegroups.com> |
| In reply to | #110069 |
субота, 18 червня 2016 р. 02:52:35 UTC+3 користувач Chris написав: > I have been trying to write a simple Hello World script on my Mac at work with TextEdit. However, I keep getting this error message: > > SyntaxError: Non-ASCII character '\xe2' in hello_world.py on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details > > I am using TextEdit in plain text mode. The document was saved in UTF-8, and I still get the error message. I tried switching to Western ASCII encoding, but once I start typing, I get a message stating that the document can no longer be saved using its original Western (ASCII) encoding. > > Any suggestions for a good open source text editor for the Mac out there? For now, I am going to stick with vim. I don't know anything about editors for coding, but as a writer that often use text editors (and I have seen them a lot!) I'd suggest you browsing this review site where you can find some cool apps <a href="http://besttexteditor.com">besttexteditor.com</a>
[toc] | [prev] | [standalone]
Page 5 of 5 — ← Prev page 1 2 3 4 [5]
Back to top | Article view | comp.lang.python
csiph-web