12-08-2011
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
:) as soon as i installed my software a couple of weeks ago..
(fedora core 2 vs, 2.6.8-1.521) i decided to switch the shell to sh shell and i know that .bashrc is the bash profile file(???) i want to use the sh version of the same file and make it the main profile file.. how can I switch it and... (3 Replies)
Discussion started by: moxxx68
3 Replies
2. Shell Programming and Scripting
I need some help making this script... I guess I'm having trouble even interpretating what to even get started on...
I need to create a script that will search a given directory (typically a user's home directory, but not necessarily) as provided on the command line and any sub-directors for... (2 Replies)
Discussion started by: Jukai
2 Replies
3. Shell Programming and Scripting
Hi There, :)
I Need to put the following command in the vimrc for the execution of ECLIPSE
so I have written smthing like as follows,
export PATH=$PATH:/JVM location
after this i go to my eclipse folder and when I execute STILL it is not getting opened.....
Any Help that makes my... (6 Replies)
Discussion started by: gk_linux
6 Replies
4. Shell Programming and Scripting
i have made a few changes to my bashrc file...have set a few environmental variable that my shell scripts use. Is there any way that these changes can reflect in evryone else's bashrc who are in the network or do all of them have to copy those changes to their own bashrc file. (2 Replies)
Discussion started by: lassimanji
2 Replies
5. Solaris
Hi
since we migrated from Solaris 8 to Solaris 10 I do miss a nice feature when editing crontab with vim editor: no more color highlighting after starting to edit. Well there is a hack, see below.
I did define:
export EDITOR='vim -c ":source /export/home/duc904/.vimrc"'
Under Sol8 when... (2 Replies)
Discussion started by: duc904
2 Replies
6. UNIX for Advanced & Expert Users
I was reading this and thought I could put this in my vimrc and it would convert the line endings to unix. Am I doing something wrong or am I missing something?
set ff=unixManaging/Munging Line-Endings with Vi/Vim | Jeet Sukumaran
I used this command and it confirms that my global option is... (2 Replies)
Discussion started by: cokedude
2 Replies
7. Shell Programming and Scripting
What is the difference between .vimrc and .exrc? I google it but didn't find the brief explanation?
Regards
ADI (2 Replies)
Discussion started by: adisky123
2 Replies
8. Shell Programming and Scripting
Dear All,
We run backup script to update backup file every hour.
I want to create a script, which transfer these files in another server using ftp as new backup file created every hour. Files should be stored with a unique name for every hour(e.g 20130708_13:00 , 20130708_14:00 and so on) and... (13 Replies)
Discussion started by: Preeti Saini
13 Replies
9. UNIX for Advanced & Expert Users
I'm having trouble getting my vimrc to work the way I want it. For some reason after I hit enter it is creating tabs instead of spaces like I would expect. Here is an example of what I am talking about. $ = newline, ^I = tab. On the line of struct EDGETAG* q; I hit enter and it created a tab... (2 Replies)
Discussion started by: cokedude
2 Replies
10. Shell Programming and Scripting
Hi,
1. I'm using tcsh and I use a .gvimrc file which was working fine with my previous ksh shell. But while sourcing, I'm getting messages like 'Unmatched " '. I'm not trying anything fancy but just using " for commenting in the very first line and I see the error is thrown right there.
2.... (2 Replies)
Discussion started by: rishikpillai90
2 Replies
LEARN ABOUT LINUX
git-fetch-pack
GIT-FETCH-PACK(1) Git Manual GIT-FETCH-PACK(1)
NAME
git-fetch-pack - Receive missing objects from another repository
SYNOPSIS
git fetch-pack [--all] [--quiet|-q] [--keep|-k] [--thin] [--include-tag]
[--upload-pack=<git-upload-pack>]
[--depth=<n>] [--no-progress]
[-v] <repository> [<refs>...]
DESCRIPTION
Usually you would want to use git fetch, which is a higher level wrapper of this command, instead.
Invokes git-upload-pack on a possibly remote repository and asks it to send objects missing from this repository, to update the named
heads. The list of commits available locally is found out by scanning the local refs/ hierarchy and sent to git-upload-pack running on the
other end.
This command degenerates to download everything to complete the asked refs from the remote side when the local side does not have a common
ancestor commit.
OPTIONS
--all
Fetch all remote refs.
--stdin
Take the list of refs from stdin, one per line. If there are refs specified on the command line in addition to this option, then the
refs from stdin are processed after those on the command line.
If --stateless-rpc is specified together with this option then the list of refs must be in packet format (pkt-line). Each ref must be
in a separate packet, and the list must end with a flush packet.
-q, --quiet
Pass -q flag to git unpack-objects; this makes the cloning process less verbose.
-k, --keep
Do not invoke git unpack-objects on received data, but create a single packfile out of it instead, and store it in the object database.
If provided twice then the pack is locked against repacking.
--thin
Fetch a "thin" pack, which records objects in deltified form based on objects not included in the pack to reduce network traffic.
--include-tag
If the remote side supports it, annotated tags objects will be downloaded on the same connection as the other objects if the object the
tag references is downloaded. The caller must otherwise determine the tags this option made available.
--upload-pack=<git-upload-pack>
Use this to specify the path to git-upload-pack on the remote side, if is not found on your $PATH. Installations of sshd ignores the
user's environment setup scripts for login shells (e.g. .bash_profile) and your privately installed git may not be found on the system
default $PATH. Another workaround suggested is to set up your $PATH in ".bashrc", but this flag is for people who do not want to pay
the overhead for non-interactive shells by having a lean .bashrc file (they set most of the things up in .bash_profile).
--exec=<git-upload-pack>
Same as --upload-pack=<git-upload-pack>.
--depth=<n>
Limit fetching to ancestor-chains not longer than n. git-upload-pack treats the special depth 2147483647 as infinite even if there is
an ancestor-chain that long.
--no-progress
Do not show the progress.
--check-self-contained-and-connected
Output "connectivity-ok" if the received pack is self-contained and connected.
-v
Run verbosely.
<repository>
The URL to the remote repository.
<refs>...
The remote heads to update from. This is relative to $GIT_DIR (e.g. "HEAD", "refs/heads/master"). When unspecified, update from all
heads the remote side has.
SEE ALSO
git-fetch(1)
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-FETCH-PACK(1)