Sorry,
I did not mention that I'm using csh as default shell on centos 5.10
It's the default shell set by the sys admin
Accordingly the PS1 does not exist
I have already added these commands to my .cshrc
---------- Post updated at 01:52 PM ---------- Previous update was at 01:42 PM ----------
Quote:
Originally Posted by RavinderSingh13
Hello aelhosiny,
Not sure completely about your requirement, but if you want to change prompt string then you can use PS1 command as follows.
Code:
[singh@localhost awk_programming]$
[singh@localhost awk_programming]$ PS1="TEST $"
TEST $man test
Similarly you can put any pwd according to your need in it. Also if you want to permanently fix prompt string you can add this command in the .profile of user.
Thanks,
R. Singh
What I need the command prompt to display the full path and $USER@HOST each in a separate line instead of both displayed in the same line so that I will have:
Code:
<The exact long path>
<my username> @ <hotsname> $
As you see, the path is not in the same line with the username and host.
Last edited by rbatte1; 10-20-2014 at 09:53 AM..
Reason: Changed ICODE tags to just CODE tags
just put blank harddisk in my ultra10. i see no display to show me the
boot> prompt. i don't know what happened....?? Got a third party graphic card. Display was ok. Monitor seems to be ok. i used different one with same result. (1 Reply)
I have two Dell x86 machines on which I am attempting to install Solaris 10 from CD. I am not doing a Jumpstart install. This is my first experience in installing Solaris (or any other OS). I am following the instructions at How to Quickly Install the Solaris 10 1/06 OS
The first machine... (3 Replies)
Hi all,
Can you tell me how to change the prompt color (only the path part) when I chnange directory with "cd"?
I use the sequence below in ".bashrc" (Solaris 8) to change my prompt colors and I'd like to modify it to change the path color when I cange directory.
PSC() { echo -ne "\"; }... (0 Replies)
HI ,
I am trying to wite a script that will prompt me saying " what is path that you want to find ?". once i specify the path, the script should put this path in the find command mentioned below and execute the script:
find <path> -ctime +200 -type f -exec ls -l {} \;
for example :
... (7 Replies)
I am new to to unix and I want to make my own basic shell. What is the code I can use to change the unix cmd console display? For example my unix display prompt says MyCompterName~, I want it to say WhatEverMan~ (3 Replies)
Hello All,
I would like to display the current time in prompt.
I tried using following command:
export PS1="$(date +%k:%M:%S) $ "
but it gave me a fixed time in prompt whereas my objective is to get the current time everytime.
$ export PS1="$(date +%k:%M:%S) $ "
17:42:42 $
17:42:42 $... (32 Replies)
I don't understand the question below..any can help me? thanks
Display the absolute path of the executable used when a
'grep' command is entered on the command line:
---------- Post updated at 08:30 PM ---------- Previous update was at 08:29 PM ----------
absolute (2 Replies)
In the below bash function multiple variants are input and stored in a variable $variant, and each is written to an out file at c:/Users/cmccabe/Desktop/Python27/out.txt stored on a separate line.
# enter variant
phox2b() {
printf "\n\n"
printf "What is the id of the patient getting... (0 Replies)
Discussion started by: cmccabe
0 Replies
LEARN ABOUT DEBIAN
py.test
PY.TEST(1) pytest PY.TEST(1)NAME
pytest - pytest usage
CALLING PY.TEST THROUGH PYTHON -M PY.TEST
New in version 2.0.
If you use Python-2.5 or later you can invoke testing through the Python interpreter from the command line:
python -m pytest [...]
This is equivalent to invoking the command line script py.test [...] directly.
GETTING HELP ON VERSION, OPTION NAMES, ENVIRONMENT VARIABLES
py.test --version # shows where pytest was imported from
py.test --funcargs # show available builtin function arguments
py.test -h | --help # show help on command line and config file options
STOPPING AFTER THE FIRST (OR N) FAILURES
To stop the testing process after the first (N) failures:
py.test -x # stop after first failure
py.test --maxfail=2 # stop after two failures
SPECIFYING TESTS / SELECTING TESTS
Several test run options:
py.test test_mod.py # run tests in module
py.test somepath # run all tests below path
py.test -k string # only run tests whose names contain a string
Import 'pkg' and use its filesystem location to find and run tests:
py.test --pyargs pkg # run all tests found below directory of pypkg
MODIFYING PYTHON TRACEBACK PRINTING
Examples for modifying traceback printing:
py.test --showlocals # show local variables in tracebacks
py.test -l # show local variables (shortcut)
py.test --tb=long # the default informative traceback formatting
py.test --tb=native # the Python standard library formatting
py.test --tb=short # a shorter traceback format
py.test --tb=line # only one line per failure
DROPPING TO PDB (PYTHON DEBUGGER) ON FAILURES
Python comes with a builtin Python debugger called PDB. py.test allows one to drop into the PDB prompt via a command line option:
py.test --pdb
This will invoke the Python debugger on every failure. Often you might only want to do this for the first failing test to understand a
certain failure situation:
py.test -x --pdb # drop to PDB on first failure, then end test session
py.test --pdb --maxfail=3 # drop to PDB for the first three failures
SETTING A BREAKPOINT / AKA SET_TRACE()
If you want to set a breakpoint and enter the pdb.set_trace() you can use a helper:
import pytest
def test_function():
...
pytest.set_trace() # invoke PDB debugger and tracing
In previous versions you could only enter PDB tracing if you disabled capturing on the command line via py.test -s.
PROFILING TEST EXECUTION DURATION
To get a list of the slowest 10 test durations:
py.test --durations=10
CREATING JUNITXML FORMAT FILES
To create result files which can be read by Hudson or other Continuous integration servers, use this invocation:
py.test --junitxml=path
to create an XML file at path.
CREATING RESULTLOG FORMAT FILES
To create plain-text machine-readable result files you can issue:
py.test --resultlog=path
and look at the content at the path location. Such files are used e.g. by the PyPy-test web page to show test results over several revi-
sions.
SENDING TEST REPORT TO POCOO PASTEBIN SERVICE
Creating a URL for each test failure:
py.test --pastebin=failed
This will submit test run information to a remote Paste service and provide a URL for each failure. You may select tests as usual or add
for example -x if you only want to send one particular failure.
Creating a URL for a whole test session log:
py.test --pastebin=all
Currently only pasting to the http://paste.pocoo.org service is implemented.
CALLING PY.TEST FROM PYTHON CODE
New in version 2.0.
You can invoke py.test from Python code directly:
pytest.main()
this acts as if you would call "py.test" from the command line. It will not raise SystemExit but return the exitcode instead. You can
pass in options and arguments:
pytest.main(['x', 'mytestdir'])
or pass in a string:
pytest.main("-x mytestdir")
You can specify additional plugins to pytest.main:
# content of myinvoke.py
import pytest
class MyPlugin:
def pytest_addoption(self, parser):
raise pytest.UsageError("hi from our plugin")
pytest.main(plugins=[MyPlugin()])
Running it will exit quickly:
$ python myinvoke.py
ERROR: hi from our plugin
AUTHOR
holger krekel at merlinux eu
COPYRIGHT
2011, holger krekel et alii
2.2 June 24, 2012 PY.TEST(1)