Re: [dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-15 Thread Roberto E. Vargas Caballero 
> hmm, it was originally added with
> b2db58c2a05168257ee4e4b941f0533c6dde2a10 to make the window title the
> status line.
> The window title does become the status line, but sandy keeps spitting
> stuff out while I'm editing, so I'll take a printed terminal status
> line over spittle.
> Is there another app that uses the status line terminal capability
> ("hs" in terminfo) so I can test it?
> I don't know enough ncurses to whip up a test.

Today is common to set the title of your terminal with
the shell prompt, althought in this case ppl usually hardcode
the sequence in PS1.


Regards,

Re: [dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-15 Thread shua lloret 
Seems like the output wasn't flushing correctly.
Created a patch that manually flushes after setting the title which
fixes it for me, though I'm wary that this is just some terminal
setting that should be turned on/off.

-shuall

On Thu, Oct 15, 2015 at 4:08 AM, Roberto E. Vargas Caballero
 wrote:
>> hmm, it was originally added with
>> b2db58c2a05168257ee4e4b941f0533c6dde2a10 to make the window title the
>> status line.
>> The window title does become the status line, but sandy keeps spitting
>> stuff out while I'm editing, so I'll take a printed terminal status
>> line over spittle.
>> Is there another app that uses the status line terminal capability
>> ("hs" in terminfo) so I can test it?
>> I don't know enough ncurses to whip up a test.
>
> Today is common to set the title of your terminal with
> the shell prompt, althought in this case ppl usually hardcode
> the sequence in PS1.
>
>
> Regards,
>
From ba3786702c4a99a6b910bc81a61eb153ae2a5396 Mon Sep 17 00:00:00 2001
From: shuall 
Date: Thu, 15 Oct 2015 12:31:03 -0400
Subject: [PATCH] fix title not updating on terms with "hs" capabilities (st)

---
 sandy.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/sandy.c b/sandy.c
index d08b683..65b936d 100644
--- a/sandy.c
+++ b/sandy.c
@@ -1971,6 +1971,7 @@ i_update(void) {
 		putp(tsl_str);
 		putp(title);
 		putp(fsl_str);
+		fflush(NULL);
 	}
 
 	/* Clean global dirty bits */
-- 
2.6.1

Re: [dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-08 Thread shua lloret 
On Tue, Oct 6, 2015 at 3:56 AM, Roberto E. Vargas Caballero
 wrote:
>
> On Sun, Oct 04, 2015 at 01:45:58PM -0400, shua lloret wrote:
>> When I try to run sandy with TERM set as any of st,st-16color,st-256color,
>>  the title line is not shown, and is instead printed out randomly to stdout
>>  as I try to insert text. This happens when running "TERM=st sandy" in rxvt,
>>  and does not happen when running "TERM=xterm sandy" in st.
>
> Stop doing that. TERM variable is the way user can say to terminfo
> which is the terminal he is using, and terminfo will use this
> information to print the correct escape sequence for the user
> terminal. If you lie to terminfo then you will have problems, like
> the problem you are commenting here. If you are using st, then set
> TERM to st, st-16color or st-256color, but if you are using rxvt
> then you must not use them.
>
>

I don't think you understand. I am having trouble with sandy in st with TERM=st.
I tried different combinations in an attempt to give more info and
narrow down the problem.

I'm using sandy git master and tried both st 0.6 and st master, both
have this problem with TERM=st.
I've tried putting the terminfo files first in ~/. terminfo and next
in /usr/share/terminfo

"hs" which in man terminfo refers to "has_status_line" seems like a
likely candidate, so I removed it from st.info and reinstalled.
It seems to fix it, but I don't want to remove hs if there is a good
reason it's in there.

-shuall

Re: [dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-08 Thread shua lloret 
On Thu, Oct 8, 2015 at 3:15 PM, shua lloret  wrote:
> On Tue, Oct 6, 2015 at 3:56 AM, Roberto E. Vargas Caballero
>  wrote:
>>
>> On Sun, Oct 04, 2015 at 01:45:58PM -0400, shua lloret wrote:
>>> When I try to run sandy with TERM set as any of st,st-16color,st-256color,
>>>  the title line is not shown, and is instead printed out randomly to stdout
>>>  as I try to insert text. This happens when running "TERM=st sandy" in rxvt,
>>>  and does not happen when running "TERM=xterm sandy" in st.
>>
>> Stop doing that. TERM variable is the way user can say to terminfo
>> which is the terminal he is using, and terminfo will use this
>> information to print the correct escape sequence for the user
>> terminal. If you lie to terminfo then you will have problems, like
>> the problem you are commenting here. If you are using st, then set
>> TERM to st, st-16color or st-256color, but if you are using rxvt
>> then you must not use them.
>>
>>
>
> I don't think you understand. I am having trouble with sandy in st with 
> TERM=st.
> I tried different combinations in an attempt to give more info and
> narrow down the problem.
>
> I'm using sandy git master and tried both st 0.6 and st master, both
> have this problem with TERM=st.
> I've tried putting the terminfo files first in ~/. terminfo and next
> in /usr/share/terminfo
>
> "hs" which in man terminfo refers to "has_status_line" seems like a
> likely candidate, so I removed it from st.info and reinstalled.
> It seems to fix it, but I don't want to remove hs if there is a good
> reason it's in there.
>
> -shuall

hmm, it was originally added with
b2db58c2a05168257ee4e4b941f0533c6dde2a10 to make the window title the
status line.
The window title does become the status line, but sandy keeps spitting
stuff out while I'm editing, so I'll take a printed terminal status
line over spittle.
Is there another app that uses the status line terminal capability
("hs" in terminfo) so I can test it?
I don't know enough ncurses to whip up a test.

-shuall

Re: [dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-06 Thread Roberto E. Vargas Caballero 

On Sun, Oct 04, 2015 at 01:45:58PM -0400, shua lloret wrote:
> When I try to run sandy with TERM set as any of st,st-16color,st-256color,
>  the title line is not shown, and is instead printed out randomly to stdout
>  as I try to insert text. This happens when running "TERM=st sandy" in rxvt,
>  and does not happen when running "TERM=xterm sandy" in st.

Stop doing that. TERM variable is the way user can say to terminfo
which is the terminal he is using, and terminfo will use this
information to print the correct escape sequence for the user
terminal. If you lie to terminfo then you will have problems, like
the problem you are commenting here. If you are using st, then set
TERM to st, st-16color or st-256color, but if you are using rxvt
then you must not use them.

Re: [dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-04 Thread Pickfire 


On Sun, Oct 04, 2015 at 01:45:58PM -0400, shua lloret wrote:

When I try to run sandy with TERM set as any of st,st-16color,st-256color,
the title line is not shown, and is instead printed out randomly to stdout
as I try to insert text. This happens when running "TERM=st sandy" in rxvt,
and does not happen when running "TERM=xterm sandy" in st.

I don't know enough about ncurses to diagnose whether it is a problem with
st.info, or sandy's use of ncurses (or ncurses itself), but the only
similar experience I've had is trying to use
TERM=st vi
when /usr/share/terminfo/s/st does not exist.

Does anyone else experience this behaviour?
Right now my solution is similar to ssh:
alias sandy="TERM=xterm-256color sandy"
in my shell rc file

-shuall


Did you `sudo make install`? If you did not do it, did you run `tic -s
st.info`?

Can you explain more about it?

--
_
< Do what you like, like what you do. >
-
   \   ^__^
\  (oo)\___
   (__)\   )\/\
   ||w |
   || ||

[dev] [sandy] [st] Title incorrectly shown if TERM=st

2015-10-04 Thread shua lloret 
When I try to run sandy with TERM set as any of st,st-16color,st-256color,
 the title line is not shown, and is instead printed out randomly to stdout
 as I try to insert text. This happens when running "TERM=st sandy" in rxvt,
 and does not happen when running "TERM=xterm sandy" in st.

 I don't know enough about ncurses to diagnose whether it is a problem with
 st.info, or sandy's use of ncurses (or ncurses itself), but the only
 similar experience I've had is trying to use
 TERM=st vi
 when /usr/share/terminfo/s/st does not exist.

 Does anyone else experience this behaviour?
 Right now my solution is similar to ssh:
 alias sandy="TERM=xterm-256color sandy"
 in my shell rc file

-shuall