* Using mount consistently to print
@ 1997-10-28 3:46 vischne
0 siblings, 0 replies; 4+ messages in thread
From: vischne @ 1997-10-28 3:46 UTC (permalink / raw)
To: gnu-win32
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 580 bytes --]
As long as you can do things like mount /dev/cdrom under cygwin's
bash shell, how about a mount /dev/lp option?
That way, Unix lpr can be used to print, and even do graphics printing
using the gswin.exe postscript interpreter.
You might check this out on your system, but I think cygwin bash permits
a call of the form:
cat textfile > prn
Was this a loophole that you overlooked in the quest to make bash
impractical for Windows?
Â\v
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using mount consistently to print
@ 1997-10-28 18:40 vischne
0 siblings, 0 replies; 4+ messages in thread
From: vischne @ 1997-10-28 18:40 UTC (permalink / raw)
To: gnu-win32
Larry Hall wrote:
At 11:46 AM 10/28/97 GMT, you wrote:
>You might check this out on your system, but I think cygwin bash permits
>a call of the form:
>
> cat textfile > prn
>
>Was this a loophole that you overlooked in the quest to make bash
>impractical for Windows?
I'm assuming this was meant "tongue in cheek" however I would like to
clarify that noone is attempting to make bash impractical for Windows.
Like everything else, it is evolving at the pace at which people who
contribute to it are inclined to fix issues. The DOS style notation
for printing is an artifact of the underlying O/S and is a nice "free-bee"
for printing at the moment.
In other words, the developers mean to close this `loophole' as well?
Actually, when Unix programs ask for the name of a printer, using `prn'
is perfectly valid, and the Unix `lpr' program has no problem with this
either. Since it doesn't cause any problems with cygwin, AND SINCE MOUNT
DOESN'T RECOGNIZE PRN, it is the perfect solution.
And, believe me, `tongue in cheek' isn't all it's cracked up to be.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Using mount consistently to print
@ 1997-10-29 2:35 Sergey Okhapkin
0 siblings, 0 replies; 4+ messages in thread
From: Sergey Okhapkin @ 1997-10-29 2:35 UTC (permalink / raw)
To: gnu-win32, 'vischne@ibm.net'
vischne@ibm.net wrote:
> As long as you can do things like mount /dev/cdrom under cygwin's
> bash shell, how about a mount /dev/lp option?
1:/usr/src$ mount -b //master_1/dfxl /dev/lp
2:/usr/src$ ls -l >/dev/lp
3:/usr/src$
That works as expected. NT 4.0 SP3.
--
Sergey Okhapkin, http://www.lexa.ru/sos
Moscow, Russia
Looking for a job.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Using mount consistently to print
@ 1997-10-29 8:46 Larry Hall
0 siblings, 0 replies; 4+ messages in thread
From: Larry Hall @ 1997-10-29 8:46 UTC (permalink / raw)
To: vischne, gnu-win32
At 10:34 PM 10/28/97 GMT, vischne@ibm.net wrote:
>Larry Hall wrote:
>At 11:46 AM 10/28/97 GMT, you wrote:
>>You might check this out on your system, but I think cygwin bash permits
>>a call of the form:
>>
>> cat textfile > prn
>>
>>Was this a loophole that you overlooked in the quest to make bash
>>impractical for Windows?
>
>I'm assuming this was meant "tongue in cheek" however I would like to
>clarify that noone is attempting to make bash impractical for Windows.
>Like everything else, it is evolving at the pace at which people who
>contribute to it are inclined to fix issues. The DOS style notation
>for printing is an artifact of the underlying O/S and is a nice "free-bee"
>for printing at the moment.
>
>In other words, the developers mean to close this `loophole' as well?
>Actually, when Unix programs ask for the name of a printer, using `prn'
>is perfectly valid, and the Unix `lpr' program has no problem with this
>either. Since it doesn't cause any problems with cygwin, AND SINCE MOUNT
>DOESN'T RECOGNIZE PRN, it is the perfect solution.
>
I cannot speak about Cygnus' plans but I would submit that classifying the
ability to use "prn" as a "loophole" to be "closed" is not only too harsh but
probably improper since I expect it would be a major undertaking to attempt
to disable what is an intrinsic "feature" of the Windows O/S's. I've heard
noone make this statement or even suggest this classification. I wouldn't
get too worked up about "prn" disappearing. Its not likely to happen IMHO.
As for other Windows capabilities, I think you can expect to see all these
tools working more seamlessly with Windows utilities over time. It has
always been my impression that these tools are being put in place to
supplement the Windows environment to help make porting UNIX programs
easier. The fact that there are some inconsistencies in the environment
right now is just a result of looking at a snapshot of a developing entity.
I submit that there is no benefit to reading more into it than that.
I don't think anyone has seriously conceived the notion that these tools
and/or environment will replace ALL Windows functionality (although it may
be possible to work in this way some day if one wanted to). Regardless, I
don't think anyone is trying to make the two environments incompatible.
Larry
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~1997-10-29 8:46 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
1997-10-28 3:46 Using mount consistently to print vischne
1997-10-28 18:40 vischne
1997-10-29 2:35 Sergey Okhapkin
1997-10-29 8:46 Larry Hall
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).