public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Stephen Cuka <stephen@firemypi.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Remove space after every 80 characters in WebGUI "Logs/System Logs".
Date: Mon, 05 Aug 2024 18:47:53 +0000	[thread overview]
Message-ID: <172288367319.1831417.3462292333355828565@mail02.haj.ipfire.org> (raw)
In-Reply-To: <8c2b7c07-d2ec-4b43-a852-b606759d34bc@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]

Hi Adolf,

Thanks for your help on this.

I left the original code lines in place for context.  They're not really necessary.  If it's better, I can remove them and resubmit the patch.

For the 

my $d = $2.': '.$data;

suggestion, there is some special processing for the display for the RED section logs.

        # correct the cut position, just when section=RED
        if (($cgiparams{'SECTION'} eq 'red' ) && ($sec =~ /(kernel:)(.*)/)) {
            $sec = 'kernel';
            $data = $2.': '.$data;
        }

Using 'my $d = $2. ': ' .$data;' for everything would add the timestamp to the front of the log text displayed for all sections.

I'm not sure if the special processing for $data for RED is necessary.  I think that the point of the 'if' statement is to clean up the Section display for entries from 'kernel: ippp\d' and 'kernel: isdn.*' matches for RED, but I don't know why adding the timestamp to the front of data would be desirable in that specific case.  I don't have any log entries to reference for that though.

Thanks,
Stephen

  reply	other threads:[~2024-08-05 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-03 22:36 Stephen Cuka
2024-08-04 10:50 ` Bernhard Bitsch
2024-08-05  8:01 ` Adolf Belka
2024-08-05 18:47   ` Stephen Cuka [this message]
2024-08-05 20:40     ` Adolf Belka
2024-08-06 15:59     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=172288367319.1831417.3462292333355828565@mail02.haj.ipfire.org \
    --to=stephen@firemypi.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox