Sponsored Content
Full Discussion: global substitution in VI
Top Forums UNIX for Advanced & Expert Users global substitution in VI Post 302165825 by OLweiser on Saturday 9th of February 2008 06:41:04 AM
Old 02-09-2008
global substitution in VI

Hi All,
I'm trying to add a carriage return to the end of my lines in a text file using substitution, but I havent found a way as yet.

Can anyone help?

something along the lines of:
:%s/<^A/^M/g obviously, this doesnt work.

Many thanks.
 

10 More Discussions You Might Find Interesting

1. Solaris

How to know the global zonename from non-global zone?

It is easy to list all zones from global zones, but how to find out the global zone name from non-global zone? thx (11 Replies)
Discussion started by: honglus
11 Replies

2. Shell Programming and Scripting

sed global substitution for ' character

Hi all, I have a text file containing sql commands. I want to use sed to replace the " character with the ' character. But when i run the command below it just replaces it with a space? Do i have the escape the ' character if i want to use it? cat sql.txt update customer set custid =... (1 Reply)
Discussion started by: borderblaster
1 Replies

3. Solaris

How can we copy a directory from Global to Non-global zone?

Hi All, How can we copy a directory from global zone to non-global zone using SCP command? (8 Replies)
Discussion started by: vijaysachin
8 Replies

4. Solaris

Is there two different kernel`s running in global and non global zone?

Hi All, I want to know for non global zone there will be different kernal running? (1 Reply)
Discussion started by: vijaysachin
1 Replies

5. Solaris

How to access ENV variables of non global zones in global zone???

Hi Guys, My requirement is I have file called /opt/orahome/.profile in non global zone. PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:. export PATH PS1="\${ORACLE_SID}:`hostname`:\$PWD$ " export PS1 EDITOR=vi export EDITOR ENV=/opt/orahome/.kshrc export ENV... (1 Reply)
Discussion started by: vijaysachin
1 Replies

6. Solaris

How to see global hostname by logging in non global zones?

Hi guru Could any one help me by letting me know, how to see global hostname by logging in non global zones Regards (2 Replies)
Discussion started by: girish.batra
2 Replies

7. Solaris

How to identify a global or non-global Solaris server?

Hi, I have Solaris zone configured with Solaris 9 and 10. In Solaris 10(non global), I use the command “zonename” to get whether it is global or non-global server. For Solaris 9, what command I can use to get whether it is global or non-global server. Regards, Kalai :confused: (25 Replies)
Discussion started by: kalpeer
25 Replies

8. Shell Programming and Scripting

Why global var is not global with export

Hi, I try to define global var assuming that I can acces it from multiple sessions/terminal windows, but I can't do this with either comand line or script delcaratino/export. I'm not a root user doing this, but is this should not be matter. Even if I do this lines below in script, being in the... (3 Replies)
Discussion started by: trento17
3 Replies

9. Solaris

Global and non-global zone resource sharing - tricky

hi all, Just a simple question but i cant get the answers in the book - In my globalzone , assuming i have 4 cpus (psrinfo -pv = 0-3), if i set dedicated-cpu (ncpus=2) for my local zone Is my globalzone left with 2 cpus or still 4 cpus ? Does localzone "resource reservation.e.g. cpu in... (6 Replies)
Discussion started by: javanoob
6 Replies

10. Solaris

Date and time change in global and non global zone

Hi, If I change date and time in global zone, then it will affect in non global zones. During this process what files will get affect in non global zones and which mechanism it's using to change. gloabl zone:Solaris 11.3 X86 TIA (1 Reply)
Discussion started by: Sumanthsv
1 Replies
deb-substvars(5)						    dpkg suite							  deb-substvars(5)

NAME
       deb-substvars - Debian source substitution variables

SYNOPSIS
       substvars

DESCRIPTION
       Before  dpkg-source,  dpkg-gencontrol  and dpkg-genchanges write their control information (to the source control file .dsc for dpkg-source
       and to standard output for dpkg-gencontrol and dpkg-genchanges) they perform some variable substitutions on the output file.

       A variable substitution has the form ${variable-name}.  Variable names consist of alphanumerics, hyphens  and  colons  and  start  with	an
       alphanumeric.  Variable	substitutions  are  performed repeatedly until none are left; the full text of the field after the substitution is
       rescanned to look for more substitutions.

       After all the substitutions have been done each occurrence of the string ${} (which is not a legal substitution) is replaced with a $ sign.

       While variable substitution is done on all control fields, some of those fields are used and needed during the build when the  substitution
       did not yet occur. That's why you can't use variables in the Package, Source and Architecture fields.

       Variable substitution happens on the content of the fields after they have been parsed, thus if you want a variable to expand over multiple
       lines you do not have to include a space after the newline. This is done implicitly when the field is output. For example, if the  variable
       ${Description} is set to "foo is bar.${Newline}foo is great." and if you have the following field:

	Description: foo application
	 ${Description}
	 .
	 More text.

       It will result in:

	Description: foo application
	 foo is bar.
	 foo is great.
	 .
	 More text.

       Variables  can  be  set	using  the  -V	common	option. They can be also specified in the file debian/substvars (or whatever other file is
       specified using the -T option). This file consists of lines of the form name=value.  Trailing whitespace on each  line,	blank  lines,  and
       lines starting with a # symbol (comments) are ignored.

       Additionally, the following standard variables are available:

       Arch   The current host architecture (i.e. the architecture the package is being built for, the equivalent of DEB_HOST_ARCH).

       source:Version
	      The source package version (since dpkg 1.13.19).

       source:Upstream-Version
	      The upstream source package version, including the Debian version epoch if any (since dpkg 1.13.19).

       binary:Version
	      The binary package version (which may differ from source:Version in a binNMU for example; since dpkg 1.13.19).

       Source-Version
	      The  source  package version (from the changelog file). This variable is now obsolete and emits an error when used as its meaning is
	      different from its function, please use the source:Version or binary:Version as appropriate.

       source:Synopsis
	      The source package synopsis, extracted from the source stanza Description field, if it exists (since dpkg 1.19.0).

       source:Extended-Description
	      The source package extended description, extracted from the source stanza Description field, if it exists (since dpkg 1.19.0).

       Installed-Size
	      The approximate total size of the package's installed files. This value is copied into the corresponding control file field; setting
	      it  will	modify the value of that field. If this variable is not set dpkg-gencontrol will compute the default value by accumulating
	      the size of each regular file and symlink rounded to 1 KiB used units, and a baseline of 1 KiB for any other filesystem object type.

	      Note: Take into account that this can only ever be an approximation, as the actual size used on the  installed  system  will  depend
	      greatly  on  the	filesystem  used and its parameters, which might end up using either more or less space than the specified in this
	      field.

       Extra-Size
	      Additional disk space used when the package is installed. If this variable is set its value is added to that of  the  Installed-Size
	      variable (whether set explicitly or using the default value) before it is copied into the Installed-Size control file field.

       S:fieldname
	      The  value  of the source stanza field fieldname (which must be given in the canonical capitalisation; since dpkg 1.18.11).  Setting
	      these variables has no effect other than on places where they are expanded explicitly.  These  variables	are  only  available  when
	      generating binary control files.

       F:fieldname
	      The value of the output field fieldname (which must be given in the canonical capitalisation). Setting these variables has no effect
	      other than on places where they are expanded explicitly.

       Format The .changes file format version generated by this version of the source packaging scripts. If you set this variable the contents of
	      the Format field in the .changes file will change too.

       Newline, Space, Tab
	      These variables each hold the corresponding character.

       shlibs:dependencyfield
	      Variable settings with names of this form are generated by dpkg-shlibdeps.

       dpkg:Upstream-Version
	      The upstream version of dpkg (since dpkg 1.13.19).

       dpkg:Version
	      The full version of dpkg (since dpkg 1.13.19).

       If a variable is referred to but not defined it generates a warning and an empty value is assumed.

FILES
       debian/substvars
	      List of substitution variables and values.

SEE ALSO
       dpkg(1), dpkg-genchanges(1), dpkg-gencontrol(1), dpkg-shlibdeps(1), dpkg-source(1).

1.19.0.5							    2018-04-16							  deb-substvars(5)
All times are GMT -4. The time now is 06:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy