Command Line Pasting - BUG?

Command Line Pasting - BUG?

Post by Andy Brush » Wed, 01 Apr 1992 01:47:00



Software: OS/2 2.0 6e.304 beta
Hardware: Gateway 2000 386/25 8Mb

Sometimes, I'd like to copy a filename (for example) from one window, and
paste it into the OS/2 command line.  For example:

d:\ab> copy <pasted filename> a:\

Unfortunately, the "paste" operation generates an "enter" on the command
line.  In the above example, the file could be copied onto itself.

I would much rather have the paste just put the text into the command line,
and let me type in more text, or paste in more text, before *I* press
"enter".  What do the rest of you think about this?


Sverdrup Technology         | 2001 Aerospace Parkway
NASA LeRC Group             | Brook Park, OH 44142
"Opinions are Mine, Only"   | (216) 826-6770

 
 
 

Command Line Pasting - BUG?

Post by Dan Keh » Tue, 31 Mar 1992 22:26:17




>Software: OS/2 2.0 6e.304 beta
>Hardware: Gateway 2000 386/25 8Mb

>Sometimes, I'd like to copy a filename (for example) from one window, and
>paste it into the OS/2 command line.  For example:

>d:\ab> copy <pasted filename> a:\

>Unfortunately, the "paste" operation generates an "enter" on the command
>line.  In the above example, the file could be copied onto itself.

>I would much rather have the paste just put the text into the command line,
>and let me type in more text, or paste in more text, before *I* press
>"enter".  What do the rest of you think about this?


>Sverdrup Technology         | 2001 Aerospace Parkway
>NASA LeRC Group             | Brook Park, OH 44142
>"Opinions are Mine, Only"   | (216) 826-6770

Here's my low-tech solution.  Prefix your command with "rem", paste,
recall the command, delete "rem", then execute it.

Not real elegant, but it works.  ;-)

Dan Kehn

 
 
 

Command Line Pasting - BUG?

Post by Brooke Paul Anders » Wed, 01 Apr 1992 08:09:01


I agree:  pasting should not insert carriage returns unless they
were present in the text that was copied -- at least the first
line should not have a CR inserted automatically.  Thus, the paste
feature should have a switch so that a CR is inserted only if
more than one lines are copied and pasted.

 
 
 

Command Line Pasting - BUG?

Post by Michael Harr » Wed, 01 Apr 1992 23:28:54



Quote:>Unfortunately, the "paste" operation generates an "enter" on the command
>line.  In the above example, the file could be copied onto itself.

It isn't the paste operation that generates an "enter".  It is the copy
operation.  If you have text on the clipboard that you pasted from the system
editor and it doesn't have a CR, then you don't get one when you paste into
an OS/2 window.  I guess this was done to handle multiple lines.  I guess
instead of sometimes putting in CR and sometimes not, someone decided to
always put them in for consistency.

______________________________________________________________________________

 Vice-President, Computer and Technologies Theme Program, NC State University
(My opinions are my own and do not represent those of NCSU or IBM Corporation)

 
 
 

Command Line Pasting - BUG?

Post by Andy Brush » Thu, 02 Apr 1992 05:04:00




>>Unfortunately, the "paste" operation generates an "enter" on the command
>>line.  In the above example, the file could be copied onto itself.

>It isn't the paste operation that generates an "enter".  It is the copy
>operation.  If you have text on the clipboard that you pasted from the system
>editor and it doesn't have a CR, then you don't get one when you paste into
>an OS/2 window.

This isn't true.  I can select from the middle of a line, and still get an
enter when I paste.  I definitely did not copy a "CR". I think it's a bug.


Sverdrup Technology         | 2001 Aerospace Parkway
NASA LeRC Group             | Brook Park, OH 44142
"Opinions are Mine, Only"   | (216) 826-6770

 
 
 

Command Line Pasting - BUG?

Post by Bert Moshi » Thu, 02 Apr 1992 03:10:24



>Software: OS/2 2.0 6e.304 beta
>Hardware: Gateway 2000 386/25 8Mb

>Sometimes, I'd like to copy a filename (for example) from one window, and
>paste it into the OS/2 command line.  For example:

>d:\ab> copy <pasted filename> a:\

>Unfortunately, the "paste" operation generates an "enter" on the command
>line.  In the above example, the file could be copied onto itself.

>I would much rather have the paste just put the text into the command line,
>and let me type in more text, or paste in more text, before *I* press
>"enter".  What do the rest of you think about this?


>Sverdrup Technology         | 2001 Aerospace Parkway
>NASA LeRC Group             | Brook Park, OH 44142
>"Opinions are Mine, Only"   | (216) 826-6770

Andrew:

I COMPLETELY AND 100% AGREE WITH YOU!!!!!

I reported this problem multiple times to IBM through the EEP.  We will have
to wait for GA to occur to see if they did fix it.  If it does not work, I
strongly suggest you call the 1-800 number for OS/2 service in the product's
manuals (shrink wrap version).  I will be doing the same!

Bert Moshier

 
 
 

Command Line Pasting - BUG?

Post by Bert Moshi » Thu, 02 Apr 1992 03:25:18



Quote:

>I agree:  pasting should not insert carriage returns unless they
>were present in the text that was copied -- at least the first
>line should not have a CR inserted automatically.  Thus, the paste
>feature should have a switch so that a CR is inserted only if
>more than one lines are copied and pasted.

To all IBMers on this forum:

PLEASE, get someone in Boca to fix this problem!

Bert Moshier

 
 
 

Command Line Pasting - BUG?

Post by Bert Moshi » Thu, 02 Apr 1992 03:36:03




>>Unfortunately, the "paste" operation generates an "enter" on the command
>>line.  In the above example, the file could be copied onto itself.

>It isn't the paste operation that generates an "enter".  It is the copy
>operation.  If you have text on the clipboard that you pasted from the system
>editor and it doesn't have a CR, then you don't get one when you paste into
>an OS/2 window.  I guess this was done to handle multiple lines.  I guess
>instead of sometimes putting in CR and sometimes not, someone decided to
>always put them in for consistency.

>______________________________________________________________________________

> Vice-President, Computer and Technologies Theme Program, NC State University
>(My opinions are my own and do not represent those of NCSU or IBM Corporation)

Michael:

Thanks for the technical correction.  Please do me a favor!  FIX THE .......
THING!

Bert Moshier

 
 
 

Command Line Pasting - BUG?

Post by Bert Moshi » Thu, 02 Apr 1992 03:51:22





>>>Unfortunately, the "paste" operation generates an "enter" on the command
>>>line.  In the above example, the file could be copied onto itself.

>>It isn't the paste operation that generates an "enter".  It is the copy
>>operation.  If you have text on the clipboard that you pasted from the system
>>editor and it doesn't have a CR, then you don't get one when you paste into
>>an OS/2 window.

>This isn't true.  I can select from the middle of a line, and still get an
>enter when I paste.  I definitely did not copy a "CR". I think it's a bug.


>Sverdrup Technology         | 2001 Aerospace Parkway
>NASA LeRC Group             | Brook Park, OH 44142
>"Opinions are Mine, Only"   | (216) 826-6770

Andrew:

I believe Doug was saying:

  - You copy the text without the CR
  - The system while the text is in the clipboard adds the CR
  - You do the paste and you get the text and CR.

The solution is for the number of CR(s) to be "n - 1" where "n" equals
the number of lines copied to the clipboard.  If an append occurs then
add a CR to the existing text before doing the append.

Bert Moshier

 
 
 

1. cut-n-paste bug, first character of each line is lost...

I have been experiencing a very weird cut-n-paste bug from both text and PM
apps.  When I cut-n-paste some text, the first character of each line
disappears.  It does not always happen and almost seams random in it's
occurance.  Here is an example, I will cut-n-paste these 4 lines:

  have been experiencing a very weird cut-n-paste bug from both text and PM
 pps.  When I cut-n-paste some text, the first character of each line
 isappears.  It does not always happen and almost seams random in it's
 ccurance.  Here is an example, I will cut-n-paste these 4 lines:

See?  The first character has disappeared from each line!  Has anyone else
experienced this and is there a fix available?

FWIW, I have experienced this while using the generic 800x600x256 drivers and
the 800x600x16 generic drivers with a Trident card and now with the
800x600x256 color drivers with my Cirrus 5422 based card.

--Ron TeamOS2
--
Ronald Van Iwaarden, TeamOS2      |
The OS/2 Source BBS (303)744-0373 |         This space available.
190+ megs of OS/2 files           |
16 OS/2 Echo Mail areas           |    Email for leasing arrangements

2. ?? editor has lost its color coding and the toolbox has lost its tools ??

3. ILINK command line bug

4. Ballerburg for Amiga

5. Passing commands into EPM from the command line

6. CISCO router to study with

7. Returning to Command Line after HELP <command>

8. Win2k professional/win98 doesn't connect to win2k server

9. Replacing IBM's 16-bit commands with the Command Line Utilities

10. unix.commands in the os/2-command-line

11. Copy & Paste Bug? (2.1GA)

12. Repeatable Telnet paste bug

13. Ultimail Bug When Pasting