preventing case translation

Thread View: net.eunice

5 messages

[T] Back to Threads [V] Tree View [G] Group Articles

5 total messages Started by Don Libes Sun, 24 Feb 1985 03:24

#170

Author: Don Libes
Date: Sun, 24 Feb 1985 03:24

24 lines
1217 bytes

I would like to be able to call Eunice programs from DCL.  The problem
is that I want the arguments untouched.  I get them all lowercased.
Even when I quote them, they are lowercased.  Does any one know how to
prevent this?

E.g.

$ echo :== $unix:[usr.bin]echo echo    ! the 2nd echo is for execl argv[0]
$ echo Foo
foo
$ echo "Foo"
"foo"

Apparently the quotes don't do a damn thing, because if I say
$ echo "Foo Bar"

what the program sees is:
	argv[1] = "foo
	argv[2] = bar"

I can handle the screwy tokenizing and unstripped quotes, but the
lowercasing is really fouling me up.  Suggestions?

Don Libes	seismo!nbs-amrf!libes

Re: preventing case translation

#174

Author: Lew Mullen
Date: Tue, 05 Mar 1985 03:29

17 lines
1187 bytes

    > I would like to be able to call Eunice programs from DCL.  The problem
    > is that I want the arguments untouched.  I get them all lowercased.
    > Even when I quote them, they are lowercased.  Does any one know how to
    > prevent this?
    > 
    > $ echo :== $unix:[usr.bin]echo echo    ! the 2nd echo is for execl argv[0]

Try:

$ echo ^Foo		(same as  $ ECHO ^FOO    ! of course)

This is similar to what you have to do if you login to a
real Unix system using an upper-case only terminal.
-- 

t4test!lew  ( Lew Mullen  @ Intel/Santa Clara )

Re: preventing case translation

#175

Author: Scott Anderson
Date: Thu, 07 Mar 1985 04:02

21 lines
1187 bytes

>> I would like to be able to call Eunice programs from DCL.  The problem
>> is that I want the arguments untouched.  I get them all lowercased.
>> Even when I quote them, they are lowercased.  Does any one know how to
>> prevent this?
>> 
>> $ echo :== $unix:[usr.bin]echo echo    ! the 2nd echo is for execl argv[0]
>
>Try:
>
>$ echo ^Foo		(same as  $ ECHO ^FOO    ! of course)
>

Yes, this works for echo on our system, but why can't I get multi-column
output with 

$ ls -^C

?

					Scott Anderson
					ihnp4!oddjob

Re: preventing case translation

#179

Author: Anders Ardo
Date: Tue, 12 Mar 1985 14:01

8 lines
899 bytes

  What about calling ls or rm from DCL with wildcards like
$ ls *.o
or
$ rm *.ckp
I cant get this to work on our system.
       Anders Ardo, Dept of computer engineering, University of Lund
   UUCP:  ...seismo!mcvax!enea!lth!anders

Re: preventing case translation

#183

Author: Barry Shein
Date: Sat, 16 Mar 1985 23:15

26 lines
1555 bytes

'ls *.o' or anything like that involving wild-cards is not
likely to ever work correctly from DCL. Remember that
the wildcard expansions are done by the SHELL in unix,
not the individual programs. In UNIX or EUNICE what 'ls'
really sees as a result of that command is quite literally:

	'ls a.o b.o c.o etc.'

Try (from EUNICE/UNIX) for example: 'ls "*.o"' (double quotes
as shown) and I think you will see what I mean [*.o: No such file or Directory]

	-Barry Shein, Boston University

P.S. It doesn't mean it *couldn't* be made to work, just that it won't
as you show it. A more plausible form would be:

	sh -c "ls *.o"

which would invoke the shell on the command and hence take care of
the wildcards. If you can run sh or csh from VMS than you could probably
write a satisfactory, simple DCL command file to take your commands
and produce that, how about:

	$ unix ls *.o
anyone? As I said, I dunno if you can get 'sh' started from VMS.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads