Sponsored Content
Full Discussion: Wildcards in VI
Top Forums UNIX for Dummies Questions & Answers Wildcards in VI Post 12602 by auswipe on Thursday 3rd of January 2002 06:08:03 PM
Old 01-03-2002
D'oh!

I saw this message in another thread from J.P.:

Quote:
Originally posted by J.P
You can also use this command in Elvis, it should work in Vi too probably Smilie

:g/^$/d

This deletes all blank lines

/
JP Smilie
You can use :g/^S[0-9].*/d to perform the mass deletion in vi. I thought there was a way to do it but couldn't remember /g, only %s for mass subsitutions! Smilie
 

10 More Discussions You Might Find Interesting

1. Programming

Makefile wildcards

Using a makefile I want to compile all .c files in the current directory without specifying them directly and then link their associated .o files into a library. How do I do this ? Thanks. (1 Reply)
Discussion started by: rcscott
1 Replies

2. UNIX for Dummies Questions & Answers

wildcards

when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies

3. UNIX for Dummies Questions & Answers

ls with wildcards

ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this ls s*.dat > file_names.txt can't figure out whats wrong with that line, any ideas? thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies

4. UNIX for Dummies Questions & Answers

wildcards NOT

Hi All Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines. tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies

5. UNIX for Dummies Questions & Answers

SED and wildcards

I am using this code to locate and modify one particular ID in a file containing thousands of entries sed 's/^>OldID/>NewID/g' Infile > Outfile How can I modify the code so I can rename all old IDs to a new unique ID? I tried this sed 's/^>*/>NewID/g' Infile > Outfile but it did not... (10 Replies)
Discussion started by: Xterra
10 Replies

6. UNIX for Advanced & Expert Users

Wildcards

These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all. GNU/Linux Command-Line Tools Guide - Wildcards GREP (1 Reply)
Discussion started by: cokedude
1 Replies

7. UNIX for Advanced & Expert Users

ln -s accept wildcards?

Does ln -s accept wildcards? It doesn't seem like it is working when I use wildcards. (9 Replies)
Discussion started by: cokedude
9 Replies

8. UNIX for Dummies Questions & Answers

For loop with wildcards

Hi, I've got a ksh for loop with wildcards specified, and I want the wildcards to be preserved when inside the loop. Instead, it is expanding the wilcards and identifying filenames in the current directory #!/usr/bin/ksh list="a* b*" for i in ${list} do echo 'Loop value =' ${i} done... (2 Replies)
Discussion started by: nim
2 Replies

9. Shell Programming and Scripting

Using Wildcards in scp

to scp using windcards you use the following : scp 'hostname:/home/username/diff_201110*' . Enjoy ! (0 Replies)
Discussion started by: phpsnook
0 Replies

10. Shell Programming and Scripting

Wildcards and exceptions

Hello: I have a very basic question. I'd like to select all files except for one file. For example, say I want to move all of the files in my current directory to a subdirectory called archive, I would use mv ./* archive/ But what if I want to move all files except for README.txt? Is there an... (19 Replies)
Discussion started by: Danny.Boy
19 Replies
MASS-BUG(1)															       MASS-BUG(1)

NAME
mass-bug - mass-file a bug report against a list of packages SYNOPSIS
mass-bug [options] --subject="bug subject" template package-list DESCRIPTION
mass-bug assists in filing a mass bug report in the Debian BTS on a set of packages. For each package in the package-list file (which should list one package per line together with an optional version number separated from the package name by an underscore), it fills out the template, adds BTS pseudo-headers, and either displays or sends the bug report. Warning: Some care has been taken to avoid unpleasant and common mistakes, but this is still a power tool that can generate massive amounts of bug report mails. Use it with care, and read the documentation in the Developer's Reference about mass filing of bug reports first. TEMPLATE
The template file is the body of the message that will be sent for each bug report, excluding the BTS pseudo-headers. In the template, #PACKAGE# is replaced with the name of the package. If a version was specified for the package, #VERSION# will be replaced by that version. The components of the version number may be specified using #EPOCH#, #UPSTREAM_VERSION# and #REVISION#. #EPOCH# includes the trailing colon and #REVISION# the leading dash so that #EPOCH#UPSTREAM_VERSION##REVISION# is always the same as #VERSION#. Note that text in the template will be automatically word-wrapped to 70 columns, up to the start of a signature (indicated by '--' at the start of a line on its own). This is another reason to avoid including BTS pseudo-headers in your template. OPTIONS
mass-bug examines the devscripts configuration files as described below. Command line options override the configuration file settings, though. --severity=(wishlist|minor|normal|important|serious|grave|critical) Specify the severity with which bugs should be filed. Default is normal. --display Fill out the templates for each package and display them all for verification. This is the default behavior. --send Actually send the bug reports. --subject="bug subject" Specify the subject of the bug report. The subject will be automatically prefixed with the name of the package that the bug is filed against. --tags Set the BTS pseudo-header for tags. --user Set the BTS pseudo-header for a usertags' user. --usertags Set the BTS pseudo-header for usertags. --source Specify that package names refer to source packages rather than binary packages. --sendmail=SENDMAILCMD Specify the sendmail command. The command will be split on white space and will not be passed to a shell. Default is /usr/sbin/sendmail. --no-wrap Do not wrap the template to lines of 70 characters. --no-conf, --noconf Do not read any configuration files. This can only be used as the first option given on the command-line. --help Provide a usage message. --version Display version information. ENVIRONMENT
DEBEMAIL and EMAIL can be set in the environment to control the email address that the bugs are sent from. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. Command line options can be used to override configuration file settings. Environment variable settings are ignored for this purpose. The currently recognised variables are: BTS_SENDMAIL_COMMAND If this is set, specifies a sendmail command to use instead of /usr/sbin/sendmail. Same as the --sendmail command line option. COPYRIGHT
This program is Copyright (C) 2006 by Joey Hess <joeyh@debian.org>. It is licensed under the terms of the GPL, either version 2 of the License, or (at your option) any later version. AUTHOR
Joey Hess <joeyh@debian.org> Debian Utilities 2013-12-23 MASS-BUG(1)
All times are GMT -4. The time now is 02:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy