 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 03 Dec 2007 14:55:54 -0500, Warp wrote:
> Jim Henderson <nos### [at] nospam com> wrote:
>> Personally, I use ctrl+shift+c and ctrl+shift+v in a GNOME terminal
>> window...
>
> That's a terminal emulator and thus not the same thing as a bare
> terminal.
True....
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Darren New wrote:
> It always throws me also that some programs will do the copy as soon as
> you highlight text. Or, if the text is still highlighted when you give
> the program focus, it'll replace whatever's in the copy buffer with
> whatever is highlighted.
I've never seen the latter happen. Can you give an example?
As for the former, usually if you explicitly copy something (using ^C or
^Ins), highlighting something won't erase that from memory. I guess
there may be exceptions.
--
Do Not Attempt to Traverse a Chasm in Two Leaps...
/\ /\ /\ /
/ \/ \ u e e n / \/ a w a z
>>>>>>mue### [at] nawazorg<<<<<<
anl
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mueen Nawaz wrote:
> I've never seen the latter happen. Can you give an example?
I'll keep it in mind to remember the circumstances next time it happens.
It tends to be old apps (like interpreters that have been around since
before Linux) that I see it happen in, IIRC.
> As for the former, usually if you explicitly copy something (using ^C or
> ^Ins), highlighting something won't erase that from memory. I guess
> there may be exceptions.
Depends how old the app is, and which copy/paste buffer it uses, I think.
--
Darren New / San Diego, CA, USA (PST)
It's not feature creep if you put it
at the end and adjust the release date.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Henderson wrote:
> Lots of seemingly simple things get overlooked in test cases for QA
Maybe it's just me, but if a URL can't have a space in it, I'd strip
spaces from what comes in from the user before trying to use it, without
even thinking about it. It just rather surprised me.
--
Darren New / San Diego, CA, USA (PST)
It's not feature creep if you put it
at the end and adjust the release date.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Maybe it's just me, but if a URL can't have a space in it, I'd strip
> spaces from what comes in from the user before trying to use it, without
> even thinking about it. It just rather surprised me.
Just like if you have a folder name coming in, and you're using it to access
a file, you append a "/" or "\" to the end if it isn't there already.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
scott escribió:
>> Maybe it's just me, but if a URL can't have a space in it, I'd strip
>> spaces from what comes in from the user before trying to use it,
>> without even thinking about it. It just rather surprised me.
>
> Just like if you have a folder name coming in, and you're using it to
> access a file, you append a "/" or "\" to the end if it isn't there
> already.
That is something the webserver does (redirect /dir to /dir/), not the
browser.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Mon, 03 Dec 2007 20:32:07 -0800, Darren New wrote:
> Jim Henderson wrote:
>> Lots of seemingly simple things get overlooked in test cases for QA
>
> Maybe it's just me, but if a URL can't have a space in it, I'd strip
> spaces from what comes in from the user before trying to use it, without
> even thinking about it. It just rather surprised me.
Well, if it were me, I'd code that way, too - but it could also be that
they replace the space internally with %20, which would be valid in a
URL. Could be that's the case they picked instead.
Jim
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
