1 Year pack of guaranteed errection - $ 399.95
Only $1.99 daily per dose!
Worlldwide shop
The greatest failure is a person who never admits that he can be a failure.
___
Bug-groff mailing list
Bug-groff@gnu.org
Вы решили дать свою рекламу при
помощи электронной рассылки, но хотелось бы узнать больше подробностей, почему
это работает? Почему 85% клиентов один раз обратившись к
профессионалам, и дальше продолжают пользоваться этим видом
рекламы?
ОСТЕРЕГАЙТЕСЬ
ПОДДЕЛОК))!!!
I. Эффективно.
Ваше
seminar®
МЕЖДУНАРОДНЫЙ ИНФОРМАЦИОННЫЙ КОНСАЛТИНГОВЫЙ ЦЕНТР
КИЕВ, УКРАИНА
+38 (044) 455^99^99
Приглашаем посетить семинары в октябре-ноябре 2005 года
Информация на сайте:www
УПРАВЛЕНИЕ ОБОРОТНЫМИ СРЕДСТВАМИ И ДЕНЕЖНЫМИ ПОТОКАМИ ПРЕДПРИЯТИЯ:
АНАЛИЗ, КОНТРОЛЬ, НОРМИРОВАНИЕ,
Thanks to all who responded to my question about building a
presentation using groff instead of PowerPoint. The ideas were
very good, and I may still pursue them. As for now, I was looking
for a way to do what I needed to do using groff, going to PS or
PDF.
I discovered a way to create a
On 22/10/2005, at 4:21 PM, Clarke Echols wrote:
Thanks to all who responded to my question about building a
presentation using groff instead of PowerPoint. The ideas were
very good, and I may still pursue them. As for now, I was looking
for a way to do what I needed to do using groff, going
. Documentation of GNU projects should be in texinfo format.
Err, there are lots of so-called GNU projects that aren't documented
in texinfo.
This is true but very unfortunate IMHO. It isn't very difficult to
write a texinfo file, and there are many benefits to do that.
Werner
This is true but very unfortunate IMHO. It isn't very difficult
to write a texinfo file, and there are many benefits to do that.
However, I have always regretted, even resented, GNU's transition
from man to info for basic reference.
I *fully* agree. It seems that you've got the wrong
On 22-Oct-05 Werner LEMBERG wrote:
This is true but very unfortunate IMHO. It isn't very difficult
to write a texinfo file, and there are many benefits to do that.
However, I have always regretted, even resented, GNU's transition
from man to info for basic reference.
I *fully* agree.
(Ted Harding) wrote:
On 22-Oct-05 Werner LEMBERG wrote:
. Documentation of GNU projects should be in texinfo format.
Err, there are lots of so-called GNU projects that aren't documented
in texinfo.
This is true but very unfortunate IMHO. It isn't very difficult to
write a texinfo file,
I won't give up on groff.texinfo. This consequently means that we
need a groff2texinfo converter (or groff2info to get the more
important info files) in case the source files are in groff
format. Personally, I *really* like the indexing features of
`info' which are quite
I don't -- and won't -- use EMACS: I can't stand it! I do, and
want to, use vim. I like, and want to have, good man pages which
list all the essentials of the behaviour of commands. I rarely
want to get into the labyrinth of a texinfo document (though I'm
pleased it's there I need
Ted Harding wrote:
This is true but very unfortunate IMHO. It isn't very difficult to
write a texinfo file, and there are many benefits to do that.
I would like to dissent (partially) from this.
Me too.
However, I have always regretted, even resented, GNU's transition
from man to info
Zvezdan Petkovic wrote:
And people who tell me that I should use a graphical front-end for XML
mark-up are equally clueless. It's not faster at all to move my hand
towards the mouse, find the menu, and choose one of 200 DocBook
elements
just to put a word in constant-width font (as it turns
How about using vi/vim non-interactively inside a shell script
(redirect keyboard input to vi/vim from a file), then in the
vi/vim commands file, use the editor's ability to pipe the
buffer through an external command (utility) such as sed or awk?
I used vi and sed that way to overhaul the
On Sat, Oct 22, 2005 at 03:47:19PM -0400, Larry Kollar wrote:
I use structured FrameMaker at work to write documentation, and one of
the easier ways I've found to get text into it is to paste it into
Vim then pipe lines through scripts that wrap blocks of text in tags
(lists, sections, and so
On Sat, Oct 22, 2005 at 02:40:10PM +0100, Ted Harding wrote:
Basically the repertoire of keystrokes, which seem to resemble
EMACS ones; OK if you remember them, which I don't (apart from
SPACE and BS). However, to be fair, it does seem that 'info' has
become more transparent over the last year
On 22-Oct-05 Zvezdan Petkovic wrote:
[...]
That's also a nice example of how painful is writing in XML.
You use a totally different tool (Vim) to help another tool that's
supposedly made to help you with XML (FrameMaker).
Also, sections and lists are the least of my issues with XML.
17 matches
Mail list logo
