Hi List,
Let me repost this request for help/support to give it some broader visibility
(and shamelessly plug my pet Easy Hack) as I really dont know too much about
ttyrec.
Best,
Bjoern
----- Forwarded message from bugzilla-daemon@freedesktop.org -----
Date: Sat, 17 Dec 2011 06:04:39 +0000
From: bugzilla-daemon@freedesktop.org
To: bjoern.michaelsen@canonical.com
Subject: [Bug 41291] [EasyHack] Create a Libreoffice build session with playterm to help new
developers
https://bugs.freedesktop.org/show_bug.cgi?id=41291
--- Comment #1 from James <arthuripswichdent@hotmail.com> 2011-12-17 07:04:39 CET ---
I've thought about this EasyHack.
I am untidy in the terminal, and pause a lot.
To take this on, I would have to be able to edit the ttyrec output that is the
immediate product of doing the build.
This appears to be possible; there are edits in this example:
http://playterm.org/r/grep-with-finds-exec-option-1317222810
but I don't know how it's done.
Advice from an experienced ttyrec user, for the benefit of the next person who
considers this bug, is welcome, but I will have finished my introductory builds
and moved on.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.
----- End forwarded message -----
Context
- [Libreoffice] Fwd: [Bug 41291] [EasyHack] Create a Libreoffice build session with playterm to help new developers · Bjoern Michaelsen
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.