Dnia 2013-09-04, o godz. 23:45:44
Kent Fredric napisał(a):
> On 4 September 2013 21:59, Michał Górny wrote:
>
> > And how are you going to implement this? I doubt that fd/vt input has
> > any sort of 'writing process id' indicator.
> >
>
>
> Though granted, my other post is not going to be us
On 4 September 2013 21:59, Michał Górny wrote:
> And how are you going to implement this? I doubt that fd/vt input has
> any sort of 'writing process id' indicator.
>
Though granted, my other post is not going to be useful on a line-by-line
basis.
The obvious easy approach is have an exec laun
On 4 September 2013 21:59, Michał Górny wrote:
> And how are you going to implement this? I doubt that fd/vt input has
> any sort of 'writing process id' indicator.
>
In one terminal:
cat -vET
In another:
pgrep -x cat # 199935
ls -la /proc/199935/fd/
dr-x-- 2 kent kent 0 Sep 4 23:29
On Wed, 4 Sep 2013 11:59:37 +0200
Michał Górny wrote:
> And how are you going to implement this? I doubt that fd/vt input has
> any sort of 'writing process id' indicator.
Yeah, will require some inspection into how this works and what
information we have available; if that indicator isn't prese
Dnia 2013-09-04, o godz. 11:24:22
Tom Wijsman napisał(a):
> On Wed, 4 Sep 2013 09:17:11 +0200
> Michał Górny wrote:
>
> > Dnia 2013-09-03, o godz. 18:57:12
> > "Walter Dnes" napisał(a):
> >
> > > On Tue, Sep 03, 2013 at 10:15:39PM +0200, Tom Wijsman wrote
> > >
> > > > That is not what this
On Wed, 4 Sep 2013 09:17:11 +0200
Michał Górny wrote:
> Dnia 2013-09-03, o godz. 18:57:12
> "Walter Dnes" napisał(a):
>
> > On Tue, Sep 03, 2013 at 10:15:39PM +0200, Tom Wijsman wrote
> >
> > > That is not what this is about, this is about having escape
> > > sequences in build logs obtained f
On Wed, 4 Sep 2013 18:03:14 +1200
Kent Fredric wrote:
> On 4 September 2013 08:11, Tom Wijsman wrote:
>
> > And then I asked the questions that I'd like to see answered:
> >
> >
> > Why do they not belong there? What do people have to do who want
> > them?
> >
>
> If anyone needs a poster chil
Dnia 2013-09-03, o godz. 18:57:12
"Walter Dnes" napisał(a):
> On Tue, Sep 03, 2013 at 10:15:39PM +0200, Tom Wijsman wrote
>
> > That is not what this is about, this is about having escape sequences
> > in build logs obtained from Bugzilla; because, they aid in skimming
> > through logs (until we
On 4 September 2013 08:11, Tom Wijsman wrote:
> And then I asked the questions that I'd like to see answered:
>
>
> Why do they not belong there? What do people have to do who want them?
>
If anyone needs a poster child for the sort of escape sequence outputs that
most definitely are of no valu
On Tue, Sep 03, 2013 at 10:15:39PM +0200, Tom Wijsman wrote
> That is not what this is about, this is about having escape sequences
> in build logs obtained from Bugzilla; because, they aid in skimming
> through logs (until we implement the feature I asked for in subject).
"The road to binary s
On Tue, 3 Sep 2013 15:43:44 -0400
"Walter Dnes" wrote:
> Similar to...
>
> USE="foo bar" emerge blah blah blah
>
> ...can the average user do something like...
>
> TERM="dumb" emerge blah blah blah
That sounds like a very rare occasion, from all the bugs I have dealt
with I have not seen an
On Tue, 3 Sep 2013 14:03:14 -0500
William Hubbs wrote:
> On Tue, Sep 03, 2013 at 10:25:19AM +0200, Ulrich Mueller wrote:
> > > On Tue, 3 Sep 2013, Tom Wijsman wrote:
> >
> > > On Mon, 2 Sep 2013 14:21:52 -0500
> > > William Hubbs wrote:
> >
> > >> I can see why someone might want to use es
On Tue, Sep 03, 2013 at 10:25:19AM +0200, Ulrich Mueller wrote
> Escape sequences have been designed for communication with peripheral
> devices, not for markup or as a storage format.
>
> Also "future colorful display" generally won't be portabe because
> escape sequences depend on the setting o
On Tue, Sep 03, 2013 at 10:25:19AM +0200, Ulrich Mueller wrote:
> > On Tue, 3 Sep 2013, Tom Wijsman wrote:
>
> > On Mon, 2 Sep 2013 14:21:52 -0500
> > William Hubbs wrote:
>
> >> I can see why someone might want to use escape codes for color
> >> displays, etc. However, imo, escape codes do
> On Tue, 3 Sep 2013, Tobias Klausmann wrote:
> My two cents for viewing-logs-in-vim (which is a use case for me):
> $ eix ansiesc
> * app-vim/ansiesc
> Available versions: (~)12
> Homepage:http://www.vim.org/scripts/script.php?script_id=302
> Description:
> On Tue, 3 Sep 2013, Tom Wijsman wrote:
> On Mon, 2 Sep 2013 14:21:52 -0500
> William Hubbs wrote:
>> I can see why someone might want to use escape codes for color
>> displays, etc. However, imo, escape codes do not belong in log files.
> They belong there so future display can remain col
On Mon, Sep 2, 2013 at 8:21 PM, William Hubbs wrote:
>
> mgorny says many people benefit from having escape codes in log
> files, but I see no benefit from it, and I don't like going through
> build.log because of them. If you load a build.log into an editor, the
> escape sequences are basically
Hi!
My two cents for viewing-logs-in-vim (which is a use case for
me):
$ eix ansiesc
* app-vim/ansiesc
Available versions: (~)12
Homepage:http://www.vim.org/scripts/script.php?script_id=302
Description: vim plugin: ansi escape sequences concealed, but
highl
On 3 September 2013 16:17, Richard Yao wrote:
> I admit that it is annoying
> to view them in a web browser where the escape characters are not
> parsed, but that is easily resolved at the terminal
>
You could plausibly also have a filter in bugzilla that detects escape
codes in the log, and ad
On 09/02/2013 03:21 PM, William Hubbs wrote:
> All,
>
> I'm starting a new thread on this, because I think it might warrant some
> discussion.
>
> I can see why someone might want to use escape codes for color displays,
> etc. However, imo, escape codes do not belong in log files.
>
> mgorny say
On 09/02/2013 01:29 PM, William Hubbs wrote:
> On Mon, Sep 02, 2013 at 09:41:28PM +0200, Michał Górny wrote:
>> Dnia 2013-09-02, o godz. 14:21:52
>> William Hubbs napisał(a):
>>
>>> On Mon, Sep 02, 2013 at 01:33:19PM +0200, Michał Górny wrote:
Dnia 2013-09-01, o godz. 16:49:34
William Hu
On Mon, 2 Sep 2013 14:21:52 -0500
William Hubbs wrote:
> I can see why someone might want to use escape codes for color
> displays, etc. However, imo, escape codes do not belong in log files.
They belong there so future display can remain colorful.
Why do they not belong there? What do people h
On 3 September 2013 09:22, Ulrich Mueller wrote:
> I'd consider any tool as broken if it outputs escape sequences when
> the output doesn't go to a terminal. (Unless such output was
> explicitly asked for.)
>
However, what about when output is going to a terminal *and* a log file?
It seems sma
> On Mon, 2 Sep 2013, William Hubbs wrote:
> I can see why someone might want to use escape codes for color
> displays, etc. However, imo, escape codes do not belong in log
> files.
> mgorny says many people benefit from having escape codes in log
> files, but I see no benefit from it, and I
On Mon, Sep 02, 2013 at 09:41:28PM +0200, Michał Górny wrote:
> Dnia 2013-09-02, o godz. 14:21:52
> William Hubbs napisał(a):
>
> > On Mon, Sep 02, 2013 at 01:33:19PM +0200, Michał Górny wrote:
> > > Dnia 2013-09-01, o godz. 16:49:34
> > > William Hubbs napisał(a):
> > >
> > > > On Sat, Aug 31,
Dnia 2013-09-02, o godz. 14:21:52
William Hubbs napisał(a):
> On Mon, Sep 02, 2013 at 01:33:19PM +0200, Michał Górny wrote:
> > Dnia 2013-09-01, o godz. 16:49:34
> > William Hubbs napisał(a):
> >
> > > On Sat, Aug 31, 2013 at 10:48:32PM +0200, Michał Górny wrote:
> > > > Dnia 2013-08-31, o godz
On Mon, Sep 02, 2013 at 01:33:19PM +0200, Michał Górny wrote:
> Dnia 2013-09-01, o godz. 16:49:34
> William Hubbs napisał(a):
>
> > On Sat, Aug 31, 2013 at 10:48:32PM +0200, Michał Górny wrote:
> > > Dnia 2013-08-31, o godz. 11:26:30
> > > Ulrich Mueller napisał(a):
> > >
> > > > > On Sat,
27 matches
Mail list logo
