lding latest bash from source and see if it still happens?
Original message
From: Tim Visher
Date: 26/02/2014 01:43 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re: PS1 Not Wrapping
On Tue, Feb 25, 2014 at 5:25 PM, Nicholas Marriott
On Tue, Feb 25, 2014 at 5:25 PM, Nicholas Marriott
wrote:
> What shell are you using? Does this happen in other shells?
I use bash. From my (perhaps wrong) experimentation with it in ksh, it
appears _not_ to happen. If you could give me a recipe for testing it
in a way that would give you informa
What shell are you using? Does this happen in other shells?
This does happen outside tmux too, right?
What if you do "env -i bash --noprofile" or whatever equivalent to
--noprofile you get from your shell?
On Tue, Feb 25, 2014 at 10:11:03AM -0500, Tim Visher wrote:
> On Tue, Feb 25, 2014 at 10:
On Tue, Feb 25, 2014 at 10:00 AM, Nicholas Marriott
wrote:
> This is confusing, what is " do the same but just type a and so on until
> after it should have wrapped both for working and nonworking.
Attached.
> Also does the first line of "stty -a" match the actual rows an
This is confusing, what is " On Tue, Feb 25, 2014 at 9:36 AM, Nicholas Marriott
> wrote:
> > Can you do the same with a working TERM and show me that typescript file
> > too?
>
> Attached.
>
> [root@host ~]# TERM=screen
> [root@host ~]# script
> Script started, file is typescript
> [root@host ~]
On Tue, Feb 25, 2014 at 9:36 AM, Nicholas Marriott
wrote:
> Can you do the same with a working TERM and show me that typescript file
> too?
Attached.
[root@host ~]# TERM=screen
[root@host ~]# script
Script started, file is typescript
[root@host ~]# staho eustaeho usntaeho usntaeoh usntaeohu snae
Can you do the same with a working TERM and show me that typescript file
too?
On Tue, Feb 25, 2014 at 09:28:20AM -0500, Tim Visher wrote:
> On Tue, Feb 25, 2014 at 9:23 AM, Nicholas Marriott
> wrote:
> > if you run:
> >
> > eval `resize`
> >
> > in the shell does it help?
>
> # eval `resi
On Tue, Feb 25, 2014 at 9:23 AM, Nicholas Marriott
wrote:
> if you run:
>
> eval `resize`
>
> in the shell does it help?
# eval `resize`
bash: resize: command not found
> if not, please run "script" then type at the prompt until it should have
> wrapped and then hit enter, type "exit"
if you run:
eval `resize`
in the shell does it help?
if not, please run "script" then type at the prompt until it should have
wrapped and then hit enter, type "exit" and send me the "typescript"
file from the current dir
On Tue, Feb 25, 2014 at 09:15:16AM -0500, Tim Visher wrote:
> On Mon, F
On Mon, Feb 24, 2014 at 5:56 PM, Nicholas Marriott
wrote:
> So the problem is not that your PS1 doesn't wrap, it's that your typing
> into the shell prompt doesn't wrap.
I'm sorry. I thought that was clear but it clearly wasn't. :)
> Does it wrap if you type into "cat"?
Yes.
--
In Christ,
Ti
So the problem is not that your PS1 doesn't wrap, it's that your typing
into the shell prompt doesn't wrap.
Does it wrap if you type into "cat"?
On Mon, Feb 24, 2014 at 09:31:27AM -0500, Tim Visher wrote:
> On Sat, Feb 22, 2014 at 12:35 PM, Nicholas Marriott
> wrote:
> > Hmm. Are you starting a
On Sat, Feb 22, 2014 at 12:35 PM, Nicholas Marriott
wrote:
> Hmm. Are you starting a new terminal each time you test or logging in
> and out or what?
Testing procedure is:
1. Edit terminfo
2. tic -x terminfo
3. ntmux test
4. prefix-key 1
5. type a bunch until i get to the right edge of the scree
Hmm. Are you starting a new terminal each time you test or logging in
and out or what?
Can you show me the output of "set" in your shell?
On Fri, Feb 21, 2014 at 10:42:19AM -0500, Tim Visher wrote:
> On Fri, Feb 21, 2014 at 10:33 AM, Nicholas Marriott
> wrote:
> > You can just copy setaf and se
On Fri, Feb 21, 2014 at 10:33 AM, Nicholas Marriott
wrote:
> You can just copy setaf and setab, the idea is to leave everything except
> them and colors alone
# infocmp -x screen screen-256color
comparing screen to screen-256color.
comparing booleans.
comparing numbers.
colors: 8,
You can just copy setaf and setab, the idea is to leave everything except them
and colors alone
Original message
From: Tim Visher
Date: 21/02/2014 15:00 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re: PS1 Not Wrapping
On Fri, Feb
On Fri, Feb 21, 2014 at 3:01 AM, Nicholas Marriott
wrote:
> On Thu, Feb 20, 2014 at 07:25:31PM -0500, Tim Visher wrote:
>> On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
>> wrote:
>> > Did you try modifying a copy of screen terminfo from the running system
>> > instead of copying it from anot
On Fri, Feb 21, 2014 at 3:01 AM, Nicholas Marriott
wrote:
> On Thu, Feb 20, 2014 at 07:25:31PM -0500, Tim Visher wrote:
>> On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
>> wrote:
>> > Did you try modifying a copy of screen terminfo from the running system
>> > instead of copying it from anot
On Fri, Feb 21, 2014 at 3:00 AM, Nicholas Marriott
wrote:
> Easy way to test is to change screen) to screen*) in the file and logout
> and in again but I suspect you are right and it's something else.
Yep. Something else. :)
--
In Christ,
Timmy V.
http://blog.twonegatives.com/
http://five.sen
On Thu, Feb 20, 2014 at 07:25:31PM -0500, Tim Visher wrote:
> On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
> wrote:
> > Did you try modifying a copy of screen terminfo from the running system
> > instead of copying it from another? You only really need colors, setaf
> > and setab.
>
> How w
Easy way to test is to change screen) to screen*) in the file and logout
and in again but I suspect you are right and it's something else.
On Thu, Feb 20, 2014 at 08:44:38PM -0500, Tim Visher wrote:
> On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
> wrote:
> > Otherwise I suggest you also c
On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
wrote:
> Otherwise I suggest you also check the shell startup files (in /etc too)
> to see if there is anything that matches xterm and screen but not
> screen-*.
I did find something here but I'm unclear as to how to interpret it.
In the vanilla
On Thu, Feb 20, 2014 at 6:40 PM, Nicholas Marriott
wrote:
> Did you try modifying a copy of screen terminfo from the running system
> instead of copying it from another? You only really need colors, setaf
> and setab.
How would I go about doing that? All I find on my system are compiled
terminfo
Did you try modifying a copy of screen terminfo from the running system
instead of copying it from another? You only really need colors, setaf
and setab.
Otherwise I suggest you also check the shell startup files (in /etc too)
to see if there is anything that matches xterm and screen but not
scree
On Thu, Feb 20, 2014 at 3:44 PM, Nicholas Marriott
wrote:
> How long is it and how wide is your terminal when it doesn't wrap? Or do you
> mean it doesn't wrap when you type?
# echo '$copy-of-current-prompt' | wc -c
64
It never wraps. Size of terminal doesn't seem to make any difference.
Small o
How long is it and how wide is your terminal when it doesn't wrap? Or do you
mean it doesn't wrap when you type?
Original message
From: Tim Visher
Date: 20/02/2014 20:13 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re: PS1 No
On Thu, 20 Feb 2014, Tim Visher wrote:
> On Thu, Feb 20, 2014 at 3:25 AM, Nicholas Marriott
> wrote:
> > What's in your PS1?
>
\n\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\n\$
--
Managing the Perform
On Thu, Feb 20, 2014 at 3:25 AM, Nicholas Marriott
wrote:
> What's in your PS1?
# echo $PS1
[\u@\h \W]\$
--
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Commo
What's in your PS1?
Original message
From: Tim Visher
Date: 20/02/2014 01:36 (GMT+00:00)
To: Nicholas Marriott
Cc: tmux-users@lists.sourceforge.net
Subject: Re: PS1 Not Wrapping
On Wed, Feb 19, 2014 at 6:02 PM, Nicholas Marriott
wrote:
> Check what is d
On Wed, Feb 19, 2014 at 6:02 PM, Nicholas Marriott
wrote:
> Check what is different between your screen and screen-256color with
> infocmp, there should be very little:
>
> $ infocmp -x screen screen-256color
# infocmp -x screen screen-256color
comparing screen to screen-256color.
comparing b
Check what is different between your screen and screen-256color with
infocmp, there should be very little:
$ infocmp -x screen screen-256color
comparing screen to screen-256color.
comparing booleans.
ccc: F:NULL.
comparing numbers.
colors: 8, 256.
pairs: 64, 32767.
30 matches
Mail list logo
