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 http://besttexteditor.com";>besttexteditor.com
--
https://mail.python.org/mailman/listinfo/python
субота, 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
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
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
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 a
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 betwe
On Sun, 19 Jun 2016 07:23:15 -0600, Michael Torrie wrote:
> On 06/19/2016 01:34 AM, Lawrence D’Oliveiro wrote:
>> On Sunday, June 19, 2016 at 7:13:26 PM UTC+12, Christian Gollwitzer
>> wrote:
>>
>>> Am 19.06.16 um 02:12 schrieb Lawrence D’Oliveiro:
>>>
But not vi/vim. It only lets you place
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 display
Am 20.06.16 um 00:15 schrieb Michael Torrie:
On 06/19/2016 03:21 PM, Quivis wrote:
On Sat, 18 Jun 2016 20:26:36 -0400, Joel Goldstick wrote:
that it is on every linux system
No, it isn't! I can be *installed* on every Linux system, but that a
whole other can of worms.
True vim is not. But
On 2016-06-20 11:32, Steven D'Aprano wrote:
> On Mon, 20 Jun 2016 04:58 am, Michael Torrie wrote:
>
> > When the cursor is over character, do command "ga" and it will
> > show you the hex code for that character.
> >
> > http://vim.wikia.com/wiki/Showing_the_ASCII_value_of_the_current_character
>
On Mon, 20 Jun 2016 04:58 am, Michael Torrie wrote:
> When the cursor is over character, do command "ga" and it will show you
> the hex code for that character.
>
> http://vim.wikia.com/wiki/Showing_the_ASCII_value_of_the_current_character
/me cries
Every time somebody refers to "the ASCII valu
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
Michael Vilain wrote:
BBEdit has been around a long time and for it's price ($130) it does a
lot but it's falling behind the times. New versions aren't really adding
much in terms of new features.
There's a free version of BBEdit called TextWrangler that's
pretty good. I'm currently using it f
On 06/19/2016 03:21 PM, Quivis wrote:
> On Sat, 18 Jun 2016 20:26:36 -0400, Joel Goldstick wrote:
>
>> that it is on every linux system
>
> No, it isn't! I can be *installed* on every Linux system, but that a
> whole other can of worms.
True vim is not. But vi should be. I'm not aware of any L
On 06/19/2016 12:06 PM, Christian Gollwitzer wrote:
> Am 19.06.16 um 18:20 schrieb Rustom Mody:
>> I gave an emacs solution to the issue not because I find editor-wars engaging
>> but because I dont know how to do *this* with vi.
>> I'd be surprised if vi actually cant do these:
>> 1. Look under th
On 06/19/2016 10:20 AM, Rustom Mody wrote:
> Yes the OP said he was using vim
> And he could not handle a unicode encoding issue
I missed that part! I somehow thought the unicode issues were coming
from his use of the built-in Mac text editor.
In any case, I have never had unicode problems with v
On Sunday, June 19, 2016 at 11:36:17 PM UTC+5:30, Christian Gollwitzer wrote:
> Am 19.06.16 um 18:20 schrieb Rustom Mody:
> > I gave an emacs solution to the issue not because I find editor-wars
> > engaging
> > but because I dont know how to do *this* with vi.
> > I'd be surprised if vi actually
Am 19.06.16 um 18:20 schrieb Rustom Mody:
I gave an emacs solution to the issue not because I find editor-wars engaging
but because I dont know how to do *this* with vi.
I'd be surprised if vi actually cant do these:
1. Look under the unicode-hood to peek at what a char is -- C-u C-x = in emacs
2
On Sunday, June 19, 2016 at 6:49:55 PM UTC+5:30, Michael Torrie wrote:
> On 06/19/2016 04:41 AM, Pete Forman wrote:
> > Both emacs and vim are powerful tools in the hands of experienced users
> > but I would recommend neither to someone starting out who is just
> > looking for a code-aware editor.
On 2016-06-18 22:56, Michael Torrie wrote:
> And I got it wrong anyway. Both ed and vim either put the cursor
> between characters (insert mode), or on the character (command
> mode). Probably made sense at the time.
Correct for vi/vim, but not ed which has no real concept of a
characterwise "ins
On 06/19/2016 01:34 AM, Lawrence D’Oliveiro wrote:
> On Sunday, June 19, 2016 at 7:13:26 PM UTC+12, Christian Gollwitzer wrote:
>
>> Am 19.06.16 um 02:12 schrieb Lawrence D’Oliveiro:
>>
>>> But not vi/vim. It only lets you place your cursor *on* a character,
>>> not *in-between* characters.
>>
>>
On 06/19/2016 04:41 AM, Pete Forman wrote:
> Both emacs and vim are powerful tools in the hands of experienced users
> but I would recommend neither to someone starting out who is just
> looking for a code-aware editor.
In any case this doesn't matter here because the original poster already
said
Pete Forman :
> Both emacs and vim are powerful tools in the hands of experienced
> users but I would recommend neither to someone starting out who is
> just looking for a code-aware editor.
I don't know. I'm recommending emacs to everybody, especially the
complete beginners, who don't yet have to
Joel Goldstick writes:
> On Sat, Jun 18, 2016 at 8:12 PM, Lawrence D’Oliveiro
> wrote:
>> On Sunday, June 19, 2016 at 11:07:23 AM UTC+12, Michael Torrie wrote:
>>>
>>> On 06/17/2016 05:52 PM, Chris via Python-list wrote:
Any suggestions for a good open source text editor for the Mac ou
Am 19.06.16 um 09:34 schrieb Lawrence D’Oliveiro:
On Sunday, June 19, 2016 at 7:13:26 PM UTC+12, Christian Gollwitzer wrote:
Am 19.06.16 um 02:12 schrieb Lawrence D’Oliveiro:
But not vi/vim. It only lets you place your cursor *on* a character,
not *in-between* characters.
This is true if yo
On Sunday, June 19, 2016 at 1:04:37 PM UTC+5:30, Lawrence D’Oliveiro wrote:
> On Sunday, June 19, 2016 at 7:13:26 PM UTC+12, Christian Gollwitzer wrote:
>
> > Am 19.06.16 um 02:12 schrieb Lawrence D’Oliveiro:
> >
> >> But not vi/vim. It only lets you place your cursor *on* a character,
> >> not *i
On Sunday, June 19, 2016 at 7:13:26 PM UTC+12, Christian Gollwitzer wrote:
> Am 19.06.16 um 02:12 schrieb Lawrence D’Oliveiro:
>
>> But not vi/vim. It only lets you place your cursor *on* a character,
>> not *in-between* characters.
>
> This is true if you use the text-mode version. I prefer gvim
Am 19.06.16 um 02:12 schrieb Lawrence D’Oliveiro:
The trouble with vim/vi/whatever, is that it doesn’t work like any
other editor on Earth.
Pull up any old GUI-based editor you like, for example Windows
(shudder) Notepad. If there are N characters in your file, then the
insertion point can be pl
On Sunday, June 19, 2016 at 4:54:36 PM UTC+12, Michael Torrie wrote:
> Two different ways of doing things. Let's not make the mistake of thinking one
> way is necessarily better.
When one leads to more complications, the answer is pretty clear...
--
https://mail.python.org/mailman/listinfo/pytho
On 06/18/2016 08:51 PM, Lawrence D’Oliveiro wrote:
> On Sunday, June 19, 2016 at 2:09:31 PM UTC+12, Michael Torrie wrote:
>> It was later on that they figured out the N+1 thing you mentioned
>> by ignoring the character cells:
>>
>> 0 1 2 3 4 5 6 7 8 9 10 H E L L O W O R L D
>>
>> That works well
On 06/18/2016 08:51 PM, Lawrence D’Oliveiro wrote:
> On Sunday, June 19, 2016 at 2:09:31 PM UTC+12, Michael Torrie wrote:
>> It was later on that they figured out the N+1 thing you mentioned by
>> ignoring the character cells:
>>
>> 0 1 2 3 4 5 6 7 8 9 10
>> H E L L O W O R L D
>>
>> That works we
On Sunday, June 19, 2016 at 2:09:31 PM UTC+12, Michael Torrie wrote:
> It was later on that they figured out the N+1 thing you mentioned by
> ignoring the character cells:
>
> 0 1 2 3 4 5 6 7 8 9 10
> H E L L O W O R L D
>
> That works well for interactive editing, but it doesn't lend itself as
On 06/18/2016 06:12 PM, Lawrence D’Oliveiro wrote:
> Pull up any old GUI-based editor you like, for example Windows
> (shudder) Notepad. If there are N characters in your file, then the
> insertion point can be placed at N + 1 positions: in-between two
> adjacent characters, or before the first cha
On 06/18/2016 06:50 PM, Michael Torrie wrote:
> On 06/18/2016 06:12 PM, Lawrence D’Oliveiro wrote:
>> But not vi/vim. It only lets you place your cursor *on* a character,
>> not *in-between* characters. That’s why you need two separate
>> insertion commands, insert-before and insert-after. And one
On 06/18/2016 06:12 PM, Lawrence D’Oliveiro wrote:
> On Sunday, June 19, 2016 at 11:07:23 AM UTC+12, Michael Torrie
> wrote:
>>
>> On 06/17/2016 05:52 PM, Chris via Python-list wrote:
>>>
>>> Any suggestions for a good open source text editor for the Mac
>>> out there? For now, I am going to sti
On Sat, Jun 18, 2016 at 8:12 PM, Lawrence D’Oliveiro
wrote:
> On Sunday, June 19, 2016 at 11:07:23 AM UTC+12, Michael Torrie wrote:
>>
>> On 06/17/2016 05:52 PM, Chris via Python-list wrote:
>>>
>>> Any suggestions for a good open source text editor for the Mac out
>>> there? For now, I am going
On Sunday, June 19, 2016 at 11:07:23 AM UTC+12, Michael Torrie wrote:
>
> On 06/17/2016 05:52 PM, Chris via Python-list wrote:
>>
>> Any suggestions for a good open source text editor for the Mac out
>> there? For now, I am going to stick with vim.
>
> Good choice.
The trouble with vim/vi/whatev
On 06/17/2016 05:52 PM, Chris via Python-list wrote:
> Any suggestions for a good open source text editor for the Mac out
> there? For now, I am going to stick with vim.
Good choice.
--
https://mail.python.org/mailman/listinfo/python-list
On Saturday, June 18, 2016 at 3:10:23 PM UTC+5:30, Marko Rauhamaa wrote:
> Michael Vilain :
>
> > "best" is subjective. Anytime someone wants the "best", I ask "what
> > features are important to you that would make it the best" because I'm
> > pretty sure what I find important wouldn't be what th
On Sat, 18 Jun 2016 12:40:09 +0300, Marko Rauhamaa wrote:
>
>> - integrated documentation so you don't have to lookup the syntax and
>> arguments of a function
>
> I have seen that in action with eclipse and Java. It could never match
> having a web browser window next to the editor window: htt
On Saturday, June 18, 2016 at 9:40:23 PM UTC+12, Marko Rauhamaa wrote:
> Michael Vilain:
>
>> - expansion of keywords, variables, subroutines
Reminds me of a story by a local CompSci lecturer who originally learned Java
through an IDE with autocomplete. Then one day he sat down to write some Ja
Michael Vilain :
> "best" is subjective. Anytime someone wants the "best", I ask "what
> features are important to you that would make it the best" because I'm
> pretty sure what I find important wouldn't be what they find
> important.
That's a bit like asking what gender, nationality and religio
On 6/18/2016 3:04 AM, Michael Vilain via Python-list wrote:
In article ,
supp...@ecourierz.com wrote:
use notepad++
To me, for programming only in Python, IDLE beats Notepad++. Some
features noted below.
[pay no attention to the little windows troll behind the curtain]
"best" is subjec
use notepad++
--
https://mail.python.org/mailman/listinfo/python-list
On Sat, 18 Jun 2016 11:50 am, Lawrence D’Oliveiro wrote:
> On Saturday, June 18, 2016 at 12:59:16 PM UTC+12, MRAB wrote:
>
>> Did you specify the encoding as described in the PEP?
>
> Python 3 defaults to UTF-8.
That doesn't mean that upgrading to Python 3 will fix the problem. It *may*,
but si
On Sat, 18 Jun 2016 09:52 am, Chris wrote:
> 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://pyth
On Jun 17, 2016 6:56 PM, "Chris via Python-list"
wrote:
>
> I have been trying to write a simple Hello World script on my Mac at work
with TextEdit.
TextEdit is not just a simple text editor, it defaults to rich text mode.
You can either attempt to get TextEdit out of rich text mode and into plai
On Saturday, June 18, 2016 at 12:59:16 PM UTC+12, MRAB wrote:
> Did you specify the encoding as described in the PEP?
Python 3 defaults to UTF-8.
--
https://mail.python.org/mailman/listinfo/python-list
On 2016-06-18 00:52, Chris via Python-list wrote:
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://pyth
On Friday, June 17, 2016 at 8:19:46 PM UTC-4, Lawrence D’Oliveiro wrote:
> On Saturday, June 18, 2016 at 11:52:35 AM UTC+12, Chris wrote:
>
> > 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
>
On Saturday, June 18, 2016 at 11:52:35 AM UTC+12, Chris wrote:
> 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
The problem is the version of Python that comes with your Mac is obsolete.
--
htt
51 matches
Mail list logo
