In ksh93 you can have:
The ${USER}${HOSTNAME} and $(_collapsed_pwd) are in 'ticks' for late evaluation.
Most complicated is the late invocation of the function (I had ran some tests: it only works in ksh93 not ksh88).
BTW there is an echo too many, resulting in double evaluation. Should be
Last edited by MadeInGermany; 10-28-2019 at 09:30 AM..
Reason: consolidated into one printf command
This User Gave Thanks to MadeInGermany For This Post:
An odd problem using .kshrc, if I run with this in my home login directory it works fine other than if I use 'man', where each word of the manual entry is on a seperate line ?. I'm using AIX 5.3 (it worked fine on 5.2). Anyone seen this before ? (3 Replies)
How to get the current working directory as part of the command prompt? Every time I chage the folder, my command prompt path shoud change. I am using Korn Shell. Any help is greatly appreciated. (3 Replies)
Hi,
I am facing two problems in my environment. Anyone can help on this?
Thanks in advance.
Problem 1
---------
When i login into my new unix system, only the .profile is executing.
.kshrc is not executing. But my default shell is .ksh
Any setup to be changed ?
Problem 2... (7 Replies)
In my .profile, my prompt is set like this:
set -o vi
PS1=`logname`@`hostname -s`:'$PWD>'
Is there a way to show what the history number would be of the command I'm typing in the prompt? For example, I frequently run commands then run 'history' to pull up the history number of a command... (2 Replies)
When I use "/" to look for a particular command that I typed in the current session it says
D02:-/home/user1/temp> /job
ksh: /job: not found.
D02:-/home/user1/temp>
previously it used to fetch all the commands which had job in it..
for example subjob, endjob, joblist etc...
may I... (7 Replies)
Greetings!
I have to work with a NFS user id between two hosts: A running Ksh 93 and B running pdksh 88.
My problem has to do with the custom prompt I created on A: it works like a charm and display colors:
PS1="$'\E
But I switch over to B, it all goes to hell (private info... (4 Replies)
I am trying to create my custom prompt and I have almost succeeded. Right now I have PS1='\n\\$\ '
What I have not figured out is how to make the directories bold when I'm using commands ls or ls -la.
Any idea how to do it???
Many thanx. (2 Replies)
I have used this color prompt on my servers for long time, in file ~\.bashrc
Black="\"
Dark="\"
Blue="\"
LBlue="\"
Green="\"
LGreen="\"
Cyan="\"
LCyan="\"
Red="\"
LRed="\"
Purple="\"
LPurple="\"
Brown="\"
Yellow="\"
LGray="\"
White="\"
Reset="\"
PS1="$Yellow\u@\h $LBlue\w... (4 Replies)
Hi,
I'm trying to customize the ksh prompt for users on a RHEL 6.6 system for having user@host pwd : $ and user@host pwd # in red color for root.
I think it's possible but i do not even succeded for a non root user :
I added in my ~/.kshrc :
PS1="Hello : " and it works
but when i... (4 Replies)
Hi,
I am trying to run this command to connect to each server without being prompted for the password. How can I do this in Linux redhat 7.2:
for HOST in $VIPS; do
su - Myadminid -c "ssh -o ConnectTimeout=10 $HOST 'date; hostname; pkill -9 -f -u Myadminid xx00 ; ps -ef |grep Myadminid'" ... (7 Replies)
Perl::Critic::Policy::InputOutput::RequireEncodingWithUTUseryContributed Perl DoPerl::Critic::Policy::InputOutput::RequireEncodingWithUTF8Layer(3)NAME
Perl::Critic::Policy::InputOutput::RequireEncodingWithUTF8Layer - Write "open $fh, q{<:encoding(UTF-8)}, $filename;" instead of "open $fh,
q{{<:utf8}, $filename;".
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Use of the ":utf8" I/O layer (as opposed to ":encoding(UTF8)" or ":encoding(UTF-8)") was suggested in the Perl documentation up to version
5.8.8. This may be OK for output, but on input ":utf8" does not validate the input, leading to unexpected results.
An exploit based on this behavior of ":utf8" is exhibited on PerlMonks at <http://www.perlmonks.org/?node_id=644786>. The exploit involves
a string read from an external file and sanitized with "m/^(w+)$/", where $1 nonetheless ends up containing shell meta-characters.
To summarize:
open $fh, '<:utf8', 'foo.txt'; # BAD
open $fh, '<:encoding(UTF8)', 'foo.txt'; # GOOD
open $fh, '<:encoding(UTF-8)', 'foo.txt'; # BETTER
See the Encode documentation for the difference between "UTF8" and "UTF-8". The short version is that "UTF-8" implements the Unicode
standard, and "UTF8" is liberalized.
For consistency's sake, this policy checks files opened for output as well as input, For complete coverage it also checks "binmode()"
calls, where the direction the operation can not be determined.
CONFIGURATION
This Policy is not configurable except for the standard options.
NOTES
Because "Perl::Critic" does a static analysis, this policy can not detect cases like
my $encoding = ':utf8';
binmode $fh, $encoding;
where the encoding is computed.
SEE ALSO
PerlIO
Encode
"perldoc -f binmode"
<http://www.socialtext.net/perl5/index.cgi?the_utf8_perlio_layer>
<http://www.perlmonks.org/?node_id=644786>
AUTHOR
Thomas R. Wyant, III wyant at cpan dot org
COPYRIGHT
Copyright (c) 2010-2011 Thomas R. Wyant, III
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::InputOutput::RequireEncodingWithUTF8Layer(3)