09-14-2006
Well, silly me..
I musta been going aboot it the wrong way..
Just went to 'Software' via Yast & it asked for CD#3...
man, what was I thunkin....
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello everybody,
My question is: how to add /tmp/work at the end of line in vi editor.
my file looks like:
cp file1
cp file2
cp file3
****
I need to add " /tmp/work" at the end of each line.
I tried this
:%s/$/" /tmp/work"
and this
:%s/$/\ /tmp/work\/
but it does not work. (2 Replies)
Discussion started by: billy5
2 Replies
2. HP-UX
I'd like to find some editor for HP-UX, something like notepad, but not VI editor. Can someone have some ideas which one?
thx (6 Replies)
Discussion started by: diamond
6 Replies
3. UNIX for Advanced & Expert Users
Hi,
how can I add at the begining and at the end of all of the lines of my text file in VI editor ? Many thanks before.
for exemple if in my file i have
line 1
line 2
I want to have :
start line 1 end
start line 2 end (3 Replies)
Discussion started by: alain123456
3 Replies
4. UNIX Desktop Questions & Answers
We work on AIX 5L
We use vi as text editor (only scripts to create and modifiy).
What do you think of emacs ? Where can I find it ?
Do you know better text editor for scripts ?
Thank you for all answers. (1 Reply)
Discussion started by: annemar
1 Replies
5. HP-UX
I am new in hp ux and I want work with vi editor, but in hp ux vi editor the backspaes and del keys doesn't work.
how can I enable them.
thanks (3 Replies)
Discussion started by: hkoolivand
3 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I knw its a silly question, but am a newbie to 'vi' editor. I'm forced to use this, hence kindly help me with this question.
How can i paste a chunk 'copied from' a different editor(gedit) in 'vi editor'?
As i see, p & P options does work only within 'vi'. (10 Replies)
Discussion started by: harishmitty
10 Replies
7. Shell Programming and Scripting
Hi All,
I am running a script , working very fine on cmd prompt. The problem is that when I open do crontab -e even after setting editor to vi by
set EDITOR=vi it does not open a vi editor , rather it do as below.....
/////////////////////////////////////////////////////
$ set... (6 Replies)
Discussion started by: aarora_98
6 Replies
8. Solaris
Epic Editor was not able to obtain a license for your use. Feature Epic Editor :License server is down (1 Reply)
Discussion started by: durgaprasadr13
1 Replies
9. Shell Programming and Scripting
How can ` character be printed on vi editor ?
empl_id=`echo $line | awk ' { print $1; } '` (2 Replies)
Discussion started by: senem
2 Replies
10. Shell Programming and Scripting
Hello All,
Need one Help for one issue.
I am using a French Keyboard, so @ sign is on key 0 and i have to use right Alt + 0 to print it.
It is working everywhere but not inside Vi editor. I can type @ in shell, in notepad. But inside Vi editor it is not working, another problem is that if... (2 Replies)
Discussion started by: yadavricky
2 Replies
LEARN ABOUT DEBIAN
docbook2man-spec.pl
DOCBOOK2MAN-SPEC.PL(1) DOCBOOK2MAN-SPEC.PL(1)
NAME
docbook2man-spec.pl - convert DocBook RefEntries to man pages
SYNOPSIS
sgmlspl docbook2man-spec.pl
nsgmls [ sgml document ]| sgmlspl docbook2man-spec.pl
DESCRIPTION
docbook2man is a sgmlspl spec file that produced man pages (using the -man macros) from DocBook RefEntry markup.
The program reads ESIS produced by nsgmls (or other SGML parsers) from standard input. Markup not found in RefEntry is discarded.
Its output, the converted man pages, are written to the current directory. If RefMeta information is not specified in a RefEntry, then the
man page will be written to standard output.
The file manpage.links will also be created, which contains any aliases of the manpages generated. This file is in the format:
<man page> <alias
manpage>
The manpage.refs file keeps track of XRef references. Note that if the input document has any forward references, then docbook2man may
have to be invoked twice (the first time updating manpage.refs) to resolve them.
REQUIREMENTS
The SGMLSpm package from CPAN. This package includes the sgmlspl script that is also needed.
LIMITATIONS
Trying docbook2man on non-DocBook or non-conformant SGML results in undefined behavior. :-)
This program is a slow, dodgy Perl script.
This program does not come close to supporting all the possible markup in DocBook, and may produce wrong output in some cases with sup-
ported markup.
TO DO
Obvious stuff:
o Fix docbook2man breakages found in the test documents, especially weird.sgml.
o Add new element handling and fix existing handling. Be robust.
o Produce cleanest, readable man output as possible (unlike some other converters). Follow Linux man(7) convention. As conversion to man
pages is usually not done very often, it is better to be slower/more complicated than to produce wrong output. Also if someone wants to
give up using DocBook for whatever reason, the last-converted man pages can then be maintained manually.
o Make it faster. I think most of the speed problems so far is with parsing ESIS. Rewrite SGMLS.pm with C and/or get input directly from
SP.
o Support other (human) languages. But what to do with non-ASCII charsets? SGMLSpm doesn't report them and roff does not grok them.
[Comment: text after enclosed lists (and SS blocks) will break docbook2man] If we do this, more people can use DocBook.
COPYRIGHT
Copyright (C) 1998-1999 Steve Cheng <steve@ggi-project.org>
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2, or (at your option) any later version.
You should have received a copy of the GNU General Public License along with this program; see the file COPYING. If not, please write to
the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA.
12 September 2012 DOCBOOK2MAN-SPEC.PL(1)