I am taking a class in UNIX and have written a script that needs to countdown from a number that is read in from the keyboard to zero. If no number is given the start of the countdown should default to 10.
I can't get this to do the default
#! /bin/sh
echo Enter a number here to countdown... (2 Replies)
Hello there,
As a newbie:
The directories in PATH can be hard to distinguish when printed out as
one line with colon .Please, can i have a sample script to display
them,one to a line.
Thank you. (1 Reply)
Hey everyone, I'm fairly new to both unix and shell scripts. Right now I have a script that I can run in one folder (if a certain text file is there, do one thing, if it's not, do something else). I want to modify this to run in multiple directories. My setup is: a company directory, and within it... (2 Replies)
Hi guys, I've found two nifty little scripts on these forums one which detects if the F5 key has been pressed:
#/bin/sh
_key()
{
local kp
ESC=$'\e'
_KEY=
read -d '' -sn1 _KEY
case $_KEY in
"$ESC")
while read -d '' -sn1 -t1 kp
do
_KEY=$_KEY$kp
... (0 Replies)
Hi everyone, I'm trying to write a script to format a file using unix2dos. I want to output all but the first 14 lines in a file. Then I want to pipe this to unix2dos to convert the output to a file that's easily readable on windows. Here's what I have:
export Lines=`wc -l < $1`
export... (11 Replies)
Hi all,
Does anyone know of any FUN countdown script that I can use for my script? At the moment, am just using sleep 10 or more and then print stuff into the screen to allow more time for the user to decide whether they want to continue running the script or abort?
Just thought of wanting... (3 Replies)
Hi folks ,
I need to display a message graphically using a messagebox or textbox through bash script. However the message should be keep changing every 4 secs . I input the message from a file and use "gxmessage" to display it .
gxmessage -nofocus -center -title "Welcome screen" -geometry... (3 Replies)
Hello, I have another problem with my script - I would like to have a countdown timer visible on the screen, and at the same time, I want te be able to do something else. And when the time runs out, I need to know about that inside the script somehow and do some action. I guess that would require 2... (3 Replies)
My script gives the following result. Is it possible to display the same in table format ?
1.
rex_best
Latest feeds are not avaialable. The last feed was generated on 2012-05-17
File Name = ekb_best_20120517_010949_665.tar.gz
The Number of entry elements = 4209539
2.
rex_genre
Latest... (2 Replies)
In the below bash when the perl is it possible to hide the commands from running on screen and display a process countdown?
For example, on the cygwin screen now the user sees each process in the command running as running protocol refGene, running protocol popfreq_all, etc... Could a... (0 Replies)
Discussion started by: cmccabe
0 Replies
LEARN ABOUT CENTOS
git-annotate
GIT-ANNOTATE(1) Git Manual GIT-ANNOTATE(1)NAME
git-annotate - Annotate file lines with commit information
SYNOPSIS
git annotate [options] file [revision]
DESCRIPTION
Annotates each line in the given file with information from the commit which introduced the line. Optionally annotates from a given
revision.
The only difference between this command and git-blame(1) is that they use slightly different output formats, and this command exists only
for backward compatibility to support existing scripts, and provide a more familiar command name for people coming from other SCM systems.
OPTIONS -b
Show blank SHA-1 for boundary commits. This can also be controlled via the blame.blankboundary config option.
--root
Do not treat root commits as boundaries. This can also be controlled via the blame.showroot config option.
--show-stats
Include additional statistics at the end of blame output.
-L <start>,<end>
Annotate only the given line range. <start> and <end> can take one of these forms:
o number
If <start> or <end> is a number, it specifies an absolute line number (lines count from 1).
o /regex/
This form will use the first line matching the given POSIX regex. If <end> is a regex, it will search starting at the line given by
<start>.
o +offset or -offset
This is only valid for <end> and will specify a number of lines before or after the line given by <start>.
-l
Show long rev (Default: off).
-t
Show raw timestamp (Default: off).
-S <revs-file>
Use revisions from revs-file instead of calling git-rev-list(1).
--reverse
Walk history forward instead of backward. Instead of showing the revision in which a line appeared, this shows the last revision in
which a line has existed. This requires a range of revision like START..END where the path to blame exists in START.
-p, --porcelain
Show in a format designed for machine consumption.
--line-porcelain
Show the porcelain format, but output commit information for each line, not just the first time a commit is referenced. Implies
--porcelain.
--incremental
Show the result incrementally in a format designed for machine consumption.
--encoding=<encoding>
Specifies the encoding used to output author names and commit summaries. Setting it to none makes blame output unconverted data. For
more information see the discussion about encoding in the git-log(1) manual page.
--contents <file>
When <rev> is not specified, the command annotates the changes starting backwards from the working tree copy. This flag makes the
command pretend as if the working tree copy has the contents of the named file (specify - to make the command read from the standard
input).
--date <format>
The value is one of the following alternatives: {relative,local,default,iso,rfc,short}. If --date is not provided, the value of the
blame.date config variable is used. If the blame.date config variable is also not set, the iso format is used. For more information,
See the discussion of the --date option at git-log(1).
-M|<num>|
Detect moved or copied lines within a file. When a commit moves or copies a block of lines (e.g. the original file has A and then B,
and the commit changes it to B and then A), the traditional blame algorithm notices only half of the movement and typically blames the
lines that were moved up (i.e. B) to the parent and assigns blame to the lines that were moved down (i.e. A) to the child commit. With
this option, both groups of lines are blamed on the parent by running extra passes of inspection.
<num> is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as moving/copying within a
file for it to associate those lines with the parent commit. The default value is 20.
-C|<num>|
In addition to -M, detect lines moved or copied from other files that were modified in the same commit. This is useful when you
reorganize your program and move code around across files. When this option is given twice, the command additionally looks for copies
from other files in the commit that creates the file. When this option is given three times, the command additionally looks for copies
from other files in any commit.
<num> is optional but it is the lower bound on the number of alphanumeric characters that Git must detect as moving/copying between
files for it to associate those lines with the parent commit. And the default value is 40. If there are more than one -C options given,
the <num> argument of the last -C will take effect.
-h
Show help message.
SEE ALSO git-blame(1)GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-ANNOTATE(1)