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 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
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
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
eryk sun wrote:
> On Sat, Jun 18, 2016 at 7:09 AM, Olive
> wrote:
> > I am here on Linux.
> > ...
> > Note that if it is possible I would prefer that the launched command see
> > its standard
> > output connected to a terminal
>
> Try pexpect.
>
> https://pypi.python.org/pypi/pexpect
That'
On Sunday, June 19, 2016 at 8:29:50 PM UTC+12, Olive wrote:
>
> That's not what I am looking for. I want to let the end user intercat with the
> process, not my script. What I want is the content (after the process has
> exited) of all what it has written on standard output.
Use the logging featur
Rustom Mody writes:
> On Saturday, June 18, 2016 at 5:34:30 PM UTC+5:30, Pete Forman wrote:
>> Rustom Mody writes:
>> [snip]
>>
>> One subtle difference between your two citations is that VB uses a
>> leading dot. Might that lessening of ambiguity enable a future Python to
>> allow this?
>>
>> c
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
On 18 June 2016 at 23:47, Ethan Furman wrote:
> On 06/18/2016 07:05 AM, Joonas Liik wrote:
>>
>> On 18 June 2016 at 15:04, Pete Forman wrote:
>
>
>>> with obj:
>>> .a = 1# equivalent to obj.a = 1
>>> .total = .total + 1 # obj.total = obj.total + 1
>>
>>
>> the leading d
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
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
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:56 AM, Joonas Liik wrote:
On 18 June 2016 at 23:47, Ethan Furman wrote:
On 06/18/2016 07:05 AM, Joonas Liik wrote:
the leading dot does not resolve the ambiguity that arises from:
with ob_a:
with ob_b:
.attr_c = 42 # which object are we modifying right now?
On 06/19/2016 09:01 AM, Ethan Furman wrote:
> On 06/19/2016 04:56 AM, Joonas Liik wrote:
>> On 18 June 2016 at 23:47, Ethan Furman wrote:
>>> On 06/18/2016 07:05 AM, Joonas Liik wrote:
>
the leading dot does not resolve the ambiguity that arises from:
with ob_a:
with ob_b
Op 12-06-16 om 23:10 schreef BartC:
> On 12/06/2016 20:25, Ned Batchelder wrote:
>> Just as here there is no link between x
>> and y:
>>
>> x = 12
>> y = x
>
> (And that's a good illustration of why 'y' isn't a name reference to 'x',
> referring to the "...ducks limp" thread. But best n
On 06/19/2016 08:14 AM, Michael Torrie wrote:
On 06/19/2016 09:01 AM, Ethan Furman wrote:
On 06/19/2016 04:56 AM, Joonas Liik wrote:
On 18 June 2016 at 23:47, Ethan Furman wrote:
On 06/18/2016 07:05 AM, Joonas Liik wrote:
the leading dot does not resolve the ambiguity that arises from:
wit
On Sunday, June 19, 2016 at 9:26:54 PM UTC+5:30, Ethan Furman wrote:
> On 06/19/2016 08:14 AM, Michael Torrie wrote:
> > On 06/19/2016 09:01 AM, Ethan Furman wrote:
> >> On 06/19/2016 04:56 AM, Joonas Liik wrote:
> >>> On 18 June 2016 at 23:47, Ethan Furman wrote:
> On 06/18/2016 07:05 AM, Joo
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 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 Sun, Jun 19, 2016 at 10:35 AM, Antoon Pardon
wrote:
> Op 12-06-16 om 23:10 schreef BartC:
>> On 12/06/2016 20:25, Ned Batchelder wrote:
>>> Just as here there is no link between x
>>> and y:
>>>
>>> x = 12
>>> y = x
>>
>> (And that's a good illustration of why 'y' isn't a name referen
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 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
Hi,
I got a small interface handle with tkinter / Gridmanager.
I configure row and column to follow user window size adjustement, that'
fine. but i do not know how to adjust the main widget : a canvas
displaying a portion of a big image.
I bind a resize event that works, but do not know what to do
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 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 19/06/2016 15:35, Antoon Pardon wrote:
Op 12-06-16 om 23:10 schreef BartC:
On 12/06/2016 20:25, Ned Batchelder wrote:
Just as here there is no link between x
and y:
x = 12
y = x
(And that's a good illustration of why 'y' isn't a name reference to 'x', referring to
the "...ducks
Lawrence D’Oliveiro wrote:
I feel a new phrase coming on: “good enough for Bible work”!
I understand there's a passage in the Bible somewhere that
uses a 1 significant digit approximation to pi...
--
Greg
--
https://mail.python.org/mailman/listinfo/python-list
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
Ian Kelly wrote:
Remember, the cubit was based on the length of the
forearm, so it's not like it was a terribly precise measurement to
begin with;
Let's not sell them short. Just because it was based on a forearm
doesn't mean they didn't have a precise standard for it, any more
than people who
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
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
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
On Monday, June 20, 2016 at 7:03:01 AM UTC+5:30, 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_valu
On Mon, 20 Jun 2016 08:25 am, Gregory Ewing wrote:
> Ian Kelly wrote:
>> Remember, the cubit was based on the length of the
>> forearm, so it's not like it was a terribly precise measurement to
>> begin with;
>
> Let's not sell them short. Just because it was based on a forearm
> doesn't mean th
Hi everyone.
I'm having the following problem on an app I'm developing.
I'm writing a software that uses the Pyperclip module. I'm using pytest for the
tests. Everything worked well so far, as long as I run the tests via pytest.
The thing is, I want to use Tox, and now things didn't work so wel
On Mon, 20 Jun 2016 12:07 pm, Rustom Mody wrote:
> If python were to do more than lip service to REALLY being a unicode age
> language why are things like this out of bounds even for discussion?
>
> http://blog.languager.org/2014/04/unicoded-python.html
Quote:
"Why do we have to write x!=y the
Afternoon
Wondering has anyone much experience with lxml specifically objectify?
When I pick up a file with lxml and use objectify dumping root works as
expected actually better its quite nice. This is how i do it, file handling
part left out for brevity.
def getsMeet(file_list):
for filen
Steven D'Aprano wrote:
>
> Quote:
>
> "Why do we have to write x!=y then argue about the status of x<>y when we
> can simply write x≠y?"
>
> "Simply"?
>
> This is how I write x≠y from scratch:
To wrap this back full circle, here's how it's done on vim:
Ctrl-K, =, ! (last two steps interch
On Monday, June 20, 2016 at 8:59:44 AM UTC+5:30, Steven D'Aprano wrote:
> Without better tooling and more discoverability, non-ASCII characters as
> syntax are an anti-feature.
You need to decide which hat you have on
- idealist
- pragmatist
From a pragmatic pov nothing you are saying below is a
On Monday, June 20, 2016 at 10:06:41 AM UTC+5:30, Rustom Mody wrote:
> I have greater horror-stories to describe if you like
> On my recent ubuntu upgrade my keyboard broke -- totally ie cant type
> anything.
> Here's a detailed rundown...
>
> Upgrade complete; reboot -- NO KEYBOARD -- Yikes
> H
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 Monday, June 20, 2016 at 10:01:00 AM UTC+5:30, Phil Boutros wrote:
> Steven D'Aprano wrote:
> >
> > Quote:
> >
> > "Why do we have to write x!=y then argue about the status of x<>y when we
> > can simply write x≠y?"
> >
> > "Simply"?
> >
> > This is how I write x≠y from scratch:
>
>
> To
On Sun, Jun 19, 2016 at 4:25 PM, Gregory Ewing
wrote:
> Ian Kelly wrote:
>>
>> Remember, the cubit was based on the length of the
>> forearm, so it's not like it was a terribly precise measurement to
>> begin with;
>
>
> Let's not sell them short. Just because it was based on a forearm
> doesn't
On Monday, June 20, 2016 at 5:16:50 AM UTC+12, Joel Goldstick wrote:
> People who understand global variables generally avoid using them at
> all costs.
I use them occasionally.
> People who don't understand why globals create problems
> seem to want to use them, and then become baffled at the pr
On Monday, June 20, 2016 at 10:26:03 AM UTC+12, Gregory Ewing wrote:
> If you're building something the size of a pyramid, that could
> add up to quite a lot of error.
Particularly since so many of their neighbours had worked out how to do much
better than that, thousands of years earlier...
--
On Mon, Jun 20, 2016, at 01:03, Rustom Mody wrote:
> > Ctrl-K, =, ! (last two steps interchangeable). Done. Result: ≠
>
> Are these 'shortcuts' parameterizable?
They originate from RFC 1345, with the extension that they can be
reversed if the reverse doesn't itself exist as a RFC 1345 combinat
Sayth Renshaw wrote:
> Afternoon
>
> Wondering has anyone much experience with lxml specifically objectify?
>
> When I pick up a file with lxml and use objectify dumping root works as
> expected actually better its quite nice. This is how i do it, file
> handling part left out for brevity.
>
>
On Monday 20 June 2016 15:19, Ian Kelly wrote:
> Sure, but I think you've missed my central point, which is not that
> they wouldn't have made reasonably precise measurements in
> construction, but only that the storytellers would have rounded things
> off for their audience.
>
> We still do the
48 matches
Mail list logo
