06-07-2012
Hello, please edit your post above and change the all caps.
In case you forgot to read
the forum rules, here is quick copy.
Quote:
RULES OF THE UNIX AND LINUX FORUMS
(1) No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts.
(2) No negative comments about others or impolite remarks. Be patient.
(3) Refrain from idle chatter that does not contribute to the knowledge base. This does not apply to the forums in The Unix Lounge which are for off-topic discussions.
(4) Do not 'bump up' questions if they are not answered promptly. No duplicate or cross-posting and do not report a post or send a private message where your goal is to get an answer more quickly.
(5) Search the forums database with your keywords before asking.
(6) Do not post classroom or homework problems.
(7) No job postings from headhunters or recruiters except in The Unix Forums Job Board. See How to Post to The UNIX Forums Job Board for information on using the Job Board.
(8) No BSD vs. Linux vs. Windows or similar threads.
(9) Edit your posts if you see spelling or grammar errors (don't write in cyberchat or cyberpunk style). English only.
(10) Don't post your email address and ask for an email reply. Don't send a private message with a technical question. The forums are for the benefit of all, so all Q&A should take place in the forums.
(11) Post questions with descriptive subjects. For example, do not post questions with subjects like "Help Me!", "Urgent!!" or "Doubt". Post subjects like "Execution Problems with Cron" or "Help with Backup Shell Script".
(12) These are not hacker boards so hacker related posts will be promptly deleted or moderated.
(13) The forum administrators reserve the right to prune, move or edit posts that do not adhere to the rules or are technically inaccurate.
(14) The forum administrators reserve the right to remove users or change their posting status to read only without notice if any rules are not followed.
(15) No smoking in the forums.
Cheers.
The UNIX and Linux Forums
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
I'm rather new to the world of regular expressions and sed, though am excited by its possibilities. I have a particular task I'd like to achieve, and have googled the topic quite a bit. However, having found some codes that perform a task very similar to what I'd like to do, I can't for... (2 Replies)
Discussion started by: redseventyseven
2 Replies
2. Shell Programming and Scripting
Greetings,
I am very new to the UNIX shell scripting and would like to learn. However, I am currently stuck on how to process the below sample :
Filename : DOCabcdef24387987ab90d.xml
Pattern "DOC"+any character using and +".xml"
And i want to change the second part of that file (any... (20 Replies)
Discussion started by: fanny_tirtasari
20 Replies
3. UNIX for Dummies Questions & Answers
I have gotten myself totally lost trying to sort this out and just need some help please..
I will have a multiple directories using the following naming convention with an undetermined number of files in each directory.
9780743582094_05of5_Accountable.wav
I need to batch rename all files... (5 Replies)
Discussion started by: glev2005
5 Replies
4. Shell Programming and Scripting
hi gooday
I need some help with a rename I am attempting.
I'd like to rename a bunch of files in a folder
example
list.dat.old to list_N.dat
query.dat.old to query_N.dat
note the two periods in (.dat.old) to become _N.dat
I tried using sed like this
ls *.dat.old | sed... (3 Replies)
Discussion started by: johnstrong
3 Replies
5. Shell Programming and Scripting
Hello,
I am new to shell scripting and stuck on renaming files in a folder. The files have the format
chp01_00001.wav
chp01_00002.wav
....
chp02_00001.wav
chp02_00002.wav
....
but I want them to have the following names:
chp_bloomy_00001.wav
chp_bloomy_00002.wav
chp_bloomy_00003.wav... (8 Replies)
Discussion started by: Bloomy
8 Replies
6. Shell Programming and Scripting
Ubuntu -very new to shell scripts/Linux
I have many pictures with "FAMILY", "family" mixed in the file name and not all in the same directory;
I want to remove "family" case insensitive from the filenames;
find /media/Rock/pics/pics_bak/ -type f "*family*" | sed 's#family##gI'
# works for... (2 Replies)
Discussion started by: jennyjones
2 Replies
7. UNIX for Dummies Questions & Answers
Morning all
I've got loads of scripts but the names are too long! I've stuck the list in a flat file (names) and I'm trying to read that in line by line and create the new names (in to directory new) from the list. It looks like this:
xargs -n1 -I{} <names cat {} | sed... (1 Reply)
Discussion started by: Grueben
1 Replies
8. UNIX for Dummies Questions & Answers
I have one input file ABC.txt and one output DEF.txt. After the ABC is processed and created output, I want to rename ABC.txt to ABC.orig and DEF to ABC.txt. Currently when I am doing this, it does not process the input file as it cannot read and write to the same file. How can I achieve this?
... (12 Replies)
Discussion started by: High-T
12 Replies
9. Shell Programming and Scripting
Hello,
I'm using Windows 7 ; sed, awk and gnuwin32 are installed.
I have a big text file I need to manipulate.
In short, I will have to split it in thousands of short files, then rename and save in a folder which name is based upon filename.
Here is a snippet of my big input.txt file (this... (4 Replies)
Discussion started by: sellig
4 Replies
10. UNIX for Dummies Questions & Answers
Have a file in this format This is line one ; line_one
This is line two ; line_two
This is line three ; line_three
This is line four ; line four. I'm trying to make each line a new file called line_one
line_two
line_three
line_four. Tried using split -1 but then I'm back needing to rename... (3 Replies)
Discussion started by: jimmyf
3 Replies
LEARN ABOUT DEBIAN
blaze-edit
BLAZE-EDIT(1) BlazeBlogger Documentation BLAZE-EDIT(1)
NAME
blaze-edit - edits a blog post or a page in the BlazeBlogger repository
SYNOPSIS
blaze-edit [-fpqCPV] [-b directory] [-E editor] id
blaze-edit -h|-v
DESCRIPTION
blaze-edit opens an existing blog post or a page with the specified id in an external text editor. Note that there are several special
forms and placeholders that can be used in the text, and that will be replaced with a proper data when the blog is generated.
Special Forms
<!-- break -->
A mark to delimit a blog post synopsis.
Placeholders
%root%
A relative path to the root directory of the blog.
%home%
A relative path to the index page of the blog.
%page[id]%
A relative path to a page with the supplied id.
%post[id]%
A relative path to a blog post with the supplied id.
%tag[name]%
A relative path to a tag with the supplied name.
OPTIONS
-b directory, --blogdir directory
Allows you to specify a directory in which the BlazeBlogger repository is placed. The default option is a current working directory.
-E editor, --editor editor
Allows you to specify an external text editor. When supplied, this option overrides the relevant configuration option.
-p, --page
Tells blaze-edit to edit a page or pages.
-P, --post
Tells blaze-edit to edit a blog post or blog posts. This is the default option.
-f, --force
Tells blaze-edit to create an empty source file in case it does not already exist. If the core.processor option is enabled, this file
is used as the input to be processed by the selected application.
-C, --no-processor
Disables processing a blog post or page with an external application.
-q, --quiet
Disables displaying of unnecessary messages.
-V, --verbose
Enables displaying of all messages. This is the default option.
-h, --help
Displays usage information and exits.
-v, --version
Displays version information and exits.
ENVIRONMENT
EDITOR
Unless the core.editor option is set, BlazeBlogger tries to use system-wide settings to decide which editor to use.
EXAMPLE USAGE
Edit a blog post in an external text editor:
~]$ blaze-edit 10
Edit a page in an external text editor:
~]$ blaze-edit -p 4
Edit a page in nano:
~]$ blaze-edit -p 2 -E nano
SEE ALSO
blaze-config(1), blaze-add(1), blaze-list(1)
BUGS
To report a bug or to send a patch, please, add a new issue to the bug tracker at <http://code.google.com/p/blazeblogger/issues/>, or visit
the discussion group at <http://groups.google.com/group/blazeblogger/>.
COPYRIGHT
Copyright (C) 2008-2011 Jaromir Hradilek
This program is free software; see the source for copying conditions. It is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Version 1.2.0 2012-03-05 BLAZE-EDIT(1)