[screen-devel] [bug #48624] Screen is not properly displaying the window title

[Josef Ridky]

URL:
  

 Summary: Screen is not properly displaying the window title
 Project: GNU Screen
Submitted by: jridky
Submitted on: Mon 25 Jul 2016 12:39:05 PM GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
 Release: 4.0.3
   Fixed Release: None
 Planned Release: None
   Work Required: None

___

Details:

Description of problem:
After upgrading to screen-4.0.3 the screen window title (in gnome-terminal) is
not displayed anymore.

Version-Release number of selected component (if applicable):
screen-4.0.3
Steps to Reproduce:
1. open gnome-terminal
2. start an ssh connection to a machine with screen-4.0.3
3. run screen and create multiple screens

Actual results:
The gnome-terminal title doesn't change to the usual "[screen 1: bash]".

Expected results:
The gnome-terminal title should change to the usual "[screen 1: bash]".

Does anybody know how to solve this?
Tested on Fedora OS.

Thanks
Josef




___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] [bug #48570] set the session name with 'sessionname' on configuration file lock the terminal resizing

[Josef Ridky]

Follow-up Comment #1, bug #48570 (project screen):

I apologise, I forget to login before bug submition.

Feel free to contact me (add comment to this bug) if you have its solution.

Regards 
Josef
jri...@redhat.com

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] Ignoring logfile from .screenrc

[Josef Ridky]

Hi folks,

I have question about $SUBJ. I am not sure, if is it bug, or just PEBCAK.

version of screen: 4.5.0

If I try to do this:

1.echo 'logfile ~/screenlog.%n' > ~/.screenrc
2.screen -L
3.look for log file in home directory

Actual results:
log file is missing

When I use 

screen -L screenlog.%n (but before I have to remove logfile line from .screenrc 
file)

it will create 2 files: 
  screenlog.%n which is empty (created by checking procedure) and file 
screenlog.0 with log.

So question is, is value for logfile from .screenrc file ignored right now?

Regards

Josef Ridky
Associate Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

[screen-devel] [bug #48848] ignoring -T parameter

[Josef Ridky]

URL:
  

 Summary: ignoring -T parameter
 Project: GNU Screen
Submitted by: jridky
Submitted on: Mon 22 Aug 2016 07:16:38 AM GMT
Category: None
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
 Release: 4.4.0
   Fixed Release: None
 Planned Release: None
   Work Required: None

___

Details:

screen ignores the terminal type setting, either via the command line option
-T or via the .screenrc setting "term".  It always sets
TERM=screen.xterm-256color, but this is incompatible when SSH-ing into older
systems that don't have that terminal type defined.

Version-Release number of selected component (if applicable):
screen-4.4.0

How reproducible:
always

Steps to Reproduce:
1. screen -T screen
2. edit .screenrc, set "term screen"
3.

Actual results:
>env|grep TERM
TERM=screen.xterm-256color

Expected results:
>env|grep TERM
TERM=screen





___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] [bug #48848] ignoring -T parameter

[Josef Ridky]

Follow-up Comment #2, bug #48848 (project screen):

Hi,

I am using Fedora 24 64-bit, but unfortunately, this is my current output:

~$ echo $TERM
xterm-256color
~$ screen -T "screen"
~$ echo $TERM
xterm-256color

Second echo is used in screen window.

I will try it in git-master version of screen and I will let you know.

Regards
Josef

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] [bug #48848] ignoring -T parameter

[Josef Ridky]

Follow-up Comment #3, bug #48848 (project screen):

Hi again,

I have tried the screen version from git master branch.
Unfortunately, described problem persists for me.

I will compare screen package from Fedora with upstream version (4.4.0), just
to find, if there wasn't problem with upgrade in Fedora.

If anybody have idea, where I should start, please leave comment here.

Thanks

Josef


___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] [bug #48848] ignoring -T parameter

[Josef Ridky]

Follow-up Comment #4, bug #48848 (project screen):

Hi,

I have found something interesting,
in Fedora (but I don't know, if only there or if is this presented even on
other OS) we are not able to set terminal type to 'screen' only using -T
parameter. Any other terminal value can be set without any problems. 

Unfortunately, there is probably presented some heuristic (that is used for
setting vt100 terminal type in case of nonsense terminal type is setted as -T
parameter), which caused this issue. I am just don't know, if this heuristic
is done by screen package or any other system service.

Any ideas?

Regards
Josef

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] Screen caused buffer owerflow?

[Josef Ridky]

Hi folks,

I have been requested to solve following problem with screen, but I am confuse, 
because, I am not able to reproduce it anyhow.
For more information see https://bugzilla.redhat.com/show_bug.cgi?id=1350549.

Can anyone help me, how to solve this? Where can be the issue?

Thanks

Regards

Josef Ridky
Associate Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

Re: [screen-devel] Screen caused buffer owerflow?

[Josef Ridky]

Hi Axel,

thank you very much for your reply,
 
| What is strange and confusing in that bug report is that the original
| reporter says he got the error message "terminal name too long. (max.
| 20 char)". But at least Screen 4.4.0 has MAXTERMLEN set to 32 in os.h.
| (So unless Fedora patches that value as we do in Debian for backwards
| compatibility, it's not Screen 4.4.0 issuing that error message.)

in the latest version of screen in Fedora (screen-4.4.0) is this change 
applied, 
but unfortunately, in the error message is still presented wrong number of 
characters 
of terminal name (but in this case the error message isn't shown anymore).
 
| So for me it's likely that the issue is in an older version of screen.
| The original reporter also wrote something about a pending upgrade. So
| I assume that the version number in the report is moot.

I have asked him to upgrade/reinstall screen package to the newest version, 
but he has still the same issue even with actual screen version. That's strange.

Regards

Josef

[screen-devel] [bug #48848] ignoring -T parameter

[Josef Ridky]

Follow-up Comment #6, bug #48848 (project screen):

Hi,

thanks for recommendations.

I have compared termcap.c file from git and from Fedora package and they are
identical. I have tried even copy termfiles to ~/.terminfo folder (as you
wrote in previous comment) but even now I am not able to set 'screen' string
as term variable (so in screen will have TERM variable value 'screen').

I am really confused. Is there some way how to get some debug information?

Thanks
Josef

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] Reverting schemes

[Josef Ridky]

Hi,

I would like to ask for git commit, which solves following problem because I 
cannot upgrade screen to the newest version yet
(this issue was reported from older version of screen, new version do not 
contain this issue):

 DESCRIPTION 

'screen' terminal configuration is not reverted to when quitting vim sessions 
which use colour schemes.

Version-Release number of selected component (if applicable):

* screen-4.1.0
* vim-enhanced-7.4

Steps to Reproduce:
1. Include the following alias configured within ~/.bashrc:

---
# alias | grep -is 'avim'
alias avim='vim +"color murphy"'
---

2. Initiate a screen session:

  screen

3. Open a text file using the 'avim' alias detailed above and notice that the 
'murphy' vim colour scheme is now in use. Then quit from the session without 
saving (I.E. ':q!'):

  avim /var/tmp/test.sh
  :q!

When quitting from the session without saving, the original 'screen' terminal 
colour scheme is not reverted back to. 

4. Try the test again, this time write-quitting (I.E. ':wq!') from the 'avim' 
session and notice that the colour scheme is reverted back to correctly.

Actual results:

When quitting from the aliased vim session, the original screen colour 
configuration is not reverted back to. The vim colour scheme is still in place, 
which is not expected.

Expected results:

For the original 'screen' colour scheme to be reverted back to when ':q' from a 
document.

 END OF DESCRIPTION 

In the newest version of screen is not this issue presented (so I expect that 
is solved).
Or just write me, which file is responsible for color scheme changing/reverting.

Thanks for your help.

Regards

Josef Ridky
Associate Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

Re: [screen-devel] screen + tcsh

[Josef Ridky]

Sure, I have already asked about this (here, in -users mail list or in bug 
report on gnu.org, just can't remember where)

There is text of bug report with removing lines issue:

--
When running vim inside screen pressing ctrl+arrow_left or ctrl+arrow_right 
simultaneously deletes several lines of text. This does not happen when running 
vim directly in xterm for example. A workaround seems to be to add "set 
term=xterm" in .vimrc, but that may have various side effects.

Steps to Reproduce:
1. # screen
2. # vim /etc/resolv.conf
3. hit ctrl + arrow_right

Actual results:
multiple lines of text get deleted

Expected results:
nothing happens

--

I am not sure, if this issue was even correctly reported to screen, or if it is 
problem of vim or anything else.

Josef

- Original Message -
| From: "Amadeusz Sławiński" <am...@asmblr.net>
| To: screen-devel@gnu.org
| Sent: Wednesday, October 19, 2016 5:23:54 PM
| Subject: Re: [screen-devel] screen + tcsh
| 
| On Wed, 19 Oct 2016 10:47:12 -0400 (EDT)
| Josef Ridky <jri...@redhat.com> wrote:
| 
| > term=xterm is used for avoiding to remove lines in vim when is
| > pressed some specific key combination.
| > 
| 
| Do you have any example of such combination?
| 
| 
| Amadeusz
| 
| 

[screen-devel] screen + tcsh

[Josef Ridky]

Hi, 

I would like to ask for one thing about keybinding in screen.
Following problem is the reason, why am I asking:

---
Description of problem:
The home and end keys no longer work in screen when using tcsh as shell.

Steps to Reproduce:
1. start screen:
$ screen

2. start tcsh
$ tcsh

3. make sure home and end are bound:
$ bindkey | egrep '^(home|end)'
home   -> beginning-of-line
end-> end-of-line

4. press home or end

Actual results:
pressing "home" and "end" prints a "~".

Expected results:
cursor jumps to the beginning or end of the line.
---

I think, that this behavior is caused by using 'term=xterm' in config file.
Problem is, that this line has to be in the config file, because it solves 
other, much worse problem.

Does anyone know, how to solve this without removing term=xterm?
Thanks for your ideas.

Regards

Josef Ridky
Associate Software Engineer
Core Services Team
Red Hat Czech, s.r.o.

[screen-devel] [bug #50440] -L command line option decoding is broken

[Josef Ridky]

Follow-up Comment #1, bug #50440 (project screen):

This should be fixed in screen 4.5.1. This version is already in Fedora 25.

use: sudo dnf --enablerepo=updates-testing upgrade screen

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] [bug #48570] set the session name with 'sessionname' on configuration file lock the terminal resizing

[Josef Ridky]

Follow-up Comment #3, bug #48570 (project screen):

Do you have some idea about solution of this issue? 
Is it screen or perhaps terminal related issue?

___

Reply to this item at:

  

___
  Message sent via/by Savannah
  http://savannah.gnu.org/

[screen-devel] [bug #61103] Unable to build with autoconf 2.71

[Josef Ridky]

URL:
  

 Summary: Unable to build with autoconf 2.71
 Project: GNU Screen
Submitted by: jridky
Submitted on: Wed 01 Sep 2021 01:56:05 PM UTC
Category: Build/Install
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Release: 4.8.0
 Discussion Lock: Any
   Fixed Release: None
 Planned Release: None
   Work Required: None

___

Details:

When tried to build the screen with autoconf 2.71, following output is
printed:

```
configure.ac:10: warning: The macro `AC_CONFIG_HEADER' is obsolete.
configure.ac:10: You should run autoupdate.
./lib/autoconf/status.m4:719: AC_CONFIG_HEADER is expanded from...
configure.ac:10: the top level
configure.ac:39: warning: The macro `AC_FD_MSG' is obsolete.
configure.ac:39: You should run autoupdate.
./lib/autoconf/general.m4:400: AC_FD_MSG is expanded from...
configure.ac:39: the top level
configure.ac:48: warning: The macro `AC_ISC_POSIX' is obsolete.
configure.ac:48: You should run autoupdate.
./lib/autoconf/specific.m4:550: AC_ISC_POSIX is expanded from...
configure.ac:48: the top level
configure.ac:49: warning: AC_LINK_IFELSE was called before
AC_USE_SYSTEM_EXTENSIONS
./lib/autoconf/specific.m4:364: AC_USE_SYSTEM_EXTENSIONS is expanded from...
configure.ac:49: the top level
configure.ac:56: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:56: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:56: the top level
configure.ac:57: warning: The macro `AC_FD_MSG' is obsolete.
configure.ac:57: You should run autoupdate.
./lib/autoconf/general.m4:400: AC_FD_MSG is expanded from...
configure.ac:57: the top level
configure.ac:104: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:104: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:104: the top level
configure.ac:109: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:109: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:109: the top level
configure.ac:110: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:110: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.ac:110: the top level
configure.ac:115: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:115: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:115: the top level
configure.ac:117: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:117: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:117: the top level
configure.ac:118: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:118: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.ac:118: the top level
configure.ac:116: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:116: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.ac:116: the top level
configure.ac:130: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:130: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:130: the top level
configure.ac:140: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:140: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:140: the top level
configure.ac:141: warning: The macro `AC_TRY_LINK' is obsolete.
configure.ac:141: You should run autoupdate.
./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
configure.ac:141: the top level
configure.ac:147: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:147: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:147: the top level
configure.ac:158: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:158: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:158: the top level
configure.ac:166: warning: The macro `AC_FD_MSG' is obsolete.
configure.ac:166: You should run autoupdate.
./lib/autoconf/general.m4:400: AC_FD_MSG is expanded from...
configure.ac:166: the top level
configure.ac:169: warning: The macro `AC_CHECKING' is obsolete.
configure.ac:169: You should run autoupdate.
./lib/autoconf/general.m4:2499: AC_CHECKING is expanded from...
configure.ac:169: the top level
configure.ac:170: warning: The macro `AC_TRY_COMPILE' is obsolete.
configure.ac:170: You should run autoupdate.
./lib/autoconf/general.m4:2847: 

[screen-devel] [bug #62155] Typo in braille_tsi.c

[Josef Ridky]

URL:
  

 Summary: Typo in braille_tsi.c
 Project: GNU Screen
Submitted by: jridky
Submitted on: Tue 08 Mar 2022 12:38:35 PM UTC
Category: Build/Install
Severity: 3 - Normal
Priority: 5 - Normal
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Release: 4.9.0
 Discussion Lock: Any
   Fixed Release: None
 Planned Release: 4.9.1
   Work Required: None

___

Details:

There is typo available in the source code in file braille_tsi.c

See attached patch with fix available.



___

File Attachments:


---
Date: Tue 08 Mar 2022 12:38:35 PM UTC  Name: screen-4.9.0-braille.patch  Size:
574B   By: jridky
Patch fix.


___

Reply to this item at:

  

___
  Message sent via Savannah
  https://savannah.gnu.org/