[Konsole-devel] [Bug 139202] New: terminal properties queried during early stages of session restoring wrong? or missing?

[Roland Eggner]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=139202         
           Summary: terminal properties queried during early stages of
                    session restoring wrong? or missing?
           Product: konsole
           Version: unspecified
          Platform: Debian testing
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konsole-devel kde org
        ReportedBy: roland.eggner edu uni-graz at


Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

My most enjoyed features of KDE are
- ALL keybindings user configurable
- klipper remembering all old clipboard entries even from previous KDE sessions, limited only by hd-space, WITH incremental search
- powerful session restoring

Want to contribute an issue for even further improvement:
In most (all?) cases
(1) restored mc-sessions lack subshell as if launched by "mc -u" - VERY ANNOYING
(2) restored shell sessions of type "tail -F -n 200 /var/log/xxx" lack actual COLUMNS-value = 201 in my case, lines are wrapped to 80 columns leaving more than right hand half of screen empty - less annoying because concerns only "old" content of logfile I want to follow

I suppose the two problems share the same reason, namely terminal properties queried during early stages of session restoring are wrong or missing.

I am using this NOT always but mostly successful workaround:
konsole - settings - sessions:
name: mc
command: /bin/sh /usr/local/bin/WaitCpuLoad.sh; mc -c

with this WaitCpuLoad.sh:
#!/bin/sh
until (( "$(sed -re 's,^0?([0-9]*)\.([0-9]).*$,\1\2,' /proc/loadavg)" < 16 )) ; do
        sleep 10
done

Wish: workaround is a mess, konsole should manage the necessary delay itself until KDE is up and settled, should not try to stay ready even prior to KDE.