Sponsored Content
Top Forums UNIX for Dummies Questions & Answers how much we can pipe in shell prompt ? Post 302354659 by methyl on Saturday 19th of September 2009 07:06:38 AM
Old 09-19-2009
Remember to use the syntax ${1} and ${11} rather than $1 and $11 when composing strings.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

No shell prompt?

When I login to a specific machine (running Solaris 2.8; actually serveral machines behave this way), with a known good account, I don't get any shell prompt, and no screen responses to various commands such as ID and PWD. Any ideas on what is causing this, and how to change this behavior? (2 Replies)
Discussion started by: Mufasa
2 Replies

2. UNIX for Dummies Questions & Answers

prompt in sh shell

Hi, I´m using SCO Unix 5.0.5 and I want to configure de variable PS1, so when I type the command: cd /etc/ the prompt shows /etc/_> Is that possible with sh shell? I´ll appreciate your help. Thanks, a Happy New Year! (1 Reply)
Discussion started by: diegoe
1 Replies

3. UNIX for Dummies Questions & Answers

shell specific prompt

currently, I set my prompt in my .cshrc file as: set prompt = "%B%h %m %P %/ \n% " I have to use certain shells for some specific tasks and would like to set different prompts depending on the type of shell that I am using. Any advice? Thanks (3 Replies)
Discussion started by: dranNfly
3 Replies

4. UNIX for Advanced & Expert Users

Weird in Shell Prompt

Hi, I saw something in weird in Shell prompt. I did the following steps 1) Typed ls -l and pressed ESC without entering 2) Typed "v" (please notice that I did not type "i" after "v"), which opened vi editor 3) I see the "ls -l" command that I typed in shell prompt 4) Without modifying... (6 Replies)
Discussion started by: bobbygsk
6 Replies

5. Shell Programming and Scripting

Interactive shell through a pipe

I'm new to working with pipes, so I don't know whether the following is expected behaviour or a bug on the part of an application. Since Version 0.47, Inkscape provides a non-GUI interactive shell mode of operation. I am trying to time the program's performance in converting SVG files to PNG... (1 Reply)
Discussion started by: ccprog
1 Replies

6. Shell Programming and Scripting

Changing the shell prompt

Hi, I want to change the shell prompt, using the cd command. I have a shell prompt like this - p78-mfx(dgaw1078/9781)$ Now i do this - p78-mfx(dgaw1078/9781)$ cd log4j here the shell prompt should change like this - p78-mfx(dgaw1078/9781)log4j$ (6 Replies)
Discussion started by: arunkumarmc
6 Replies

7. AIX

Shell Scripting (prompt off)

Dear all experts, I have a script written to compress a list of files, during compressing, some of the files are having same name. When the compressing started, the same name file will be prompted with message whether to overwrite the old file. I need to enter "y" to continue. Is there any way I... (7 Replies)
Discussion started by: kwliew999
7 Replies

8. Shell Programming and Scripting

RFC - Korn shell prompt

Hi, I am learning shell scripting for the first time. I use AT&T Korn Shell, Version AJM 93u+ 2012-08-01, compiled from source on NetBSD. So far I have managed to set up what I think is a useful and pleasing shell prompt, which can be seen in the image attached to this post. The prompt is... (2 Replies)
Discussion started by: gezley
2 Replies

9. Homework & Coursework Questions

How to create one's own pipe in one's own shell?

Good evening, I'm trying to do my own shell and I encountered some issues while creating it. Indeed when I try such a command I have DAUPHINE> DAUPHINE> ls -l | grep terminal > fichier DAUPHINE> cat fichier My shell is named DAUPHINE Whereas I should have: Code: ... (0 Replies)
Discussion started by: AntoineCompagni
0 Replies
vim-addon-manager(1)					      General Commands Manual					      vim-addon-manager(1)

   ["NAME"]
       vim-addon-manager - command line manager of Vim add-ons

   ["SYNOPSIS"]
       vim-addons [OPTION ...] [COMMAND [ADDON ...]]

   ["DESCRIPTION"]
       Manage Vim addons installed system-wide, enabling on a per-user basis their installation, removal, ...

       vim-addons  is  capable	of  managing  all Vim addons registered in the system-wide registry of Vim addons (see vim-registry(5)). Each sys-
       tem-wide addon can be, with respect to a user Vim configuration, in one of the following states:

       ["installed"]
	      all of the files composing the addon are installed (i.e. symlinked) to their respective places under the target directory. The addon
	      is fully functional for the current user

       ["removed"]
	      the  files  composing the addon are not installed under the target directory.  The addon might still be working for the current user
	      if it is installed system-wide by the local administrator

       ["disabled"]
	      the files composing the addon are not installed under the target directory, but the addon is  installed  system-wide.  However,  the
	      addon has been disabled for the current user explicitly via some configuration line in plugin/vim-addons.vim under the target direc-
	      tory. The addon is not working for the current user

       ["broken"]
	      only some of the files composing the addon are installed under the target directory. The addon is probably not working for the  cur-
	      rent user

       ["unavailable"]
	      some (or all) of the files composing the addon are missing from the source directory

   ["COMMANDS"]
       A  number  of  commands	can  be  given to vim-addons to inspect or alter the status of the addons: list, status, install, remove, disable,
       amend, files, show.

       A description of the semantics of each command is reported below.

       ["list"]
	      list, one per line, the names of the addons available in the system (i.e. of all the addons mentioned in the registry, not necessar-
	      ily of all enabled addons)

       ["status"]
	      show,  one  per  line,  the status of the addons available in the system. If one or more addon arguments are specified only show the
	      status of those addons.  This is the default command if nothing is specified.

       ["install"]
	      install one or more addons under the target directory. Requires at least one addon argument

       ["remove"]
	      remove one or more addons from the target directory. Requires at least one addon argument

       ["disable"]
	      disable one or more addons to be used by the current user. Usually used for addons which are system-wide enabled by the local admin-
	      istrator	but  that  the	current  user  does not want to be used. Using this command will automatically change the content of plug-
	      in/vim-addons.vim under the target directory, probably adding ":let" commands which will inhibit the given addon	from  being  used.
	      Requires at least one addon argument

       ["enable"]
	      undo the effects of a previous disable command. Requires at least one addon argument

       ["files"]
	      list,  one  per  line, the files composing the specified addons. Files are listed relative to components of the Vim runtimepath (see
	      'runtimepath' in the Vim help). Requires at least one addon argument

       ["show"]
	      displays detailed information about the specified addons

   ["OPTIONS"]
       All commands accept the following options:

       ["-h, --help"]
	      show this usage message and exit

       ["-q, --query"]
	      be quiet and make the output more parseable (for "status")

       ["-r, --registry-dir"]
	      set the registry directory (default: /usr/share/vim/registry)

       ["-s, --source-dir"]
	      set the addons source directory (default: /usr/share/vim/addons)

       ["-t, --target-dir"]
	      set the addons target directory (default: $HOME/.vim)

       ["-v, --verbose"]
	      increase verbosity level

       ["-z, --silent"]
	      silent mode: supress most of the output

       ["-y, --system-dir"]
	      set the system-wide target directory (default: /var/lib/vim/addons)

       ["-w, --system-wide"]
	      set the addons target directory to the system-wide target directory, possibly overriding the -t option

   ["AUTHOR"]
       Stefano Zacchiroli <zack@debian.org> James Vega <jamessan@debian.org>

   ["SEE ALSO"]
       vim(1), vim-registry(5)

   ["COPYRIGHT"]
       Copyright (C) 2007 Stefano Zacchiroli Copyright (C) 2009 James Vega

       This program is free software, you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as pub-
       lished by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

								   October 2012 					      vim-addon-manager(1)
All times are GMT -4. The time now is 06:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy