Re: [dev] [st] Tip adds non-existing trailing whitespace upon mouse selection + fix

2012-10-10 Thread Roberto E. Vargas Caballero
 The GLYPH_SET flag can be used to compute the end of the line or we
 could add another flag like GLYPH_TAB when appropriate and test it in
 the copy function when it loops over the selection.

Instead of adding GLYPH_TAB we could use directly \t in c and then we don't
have to test anything in selcopy, but of couse we should check it in
drawregion.

But this solution doesn't fix this problem when you use a sequence to locate
the cursor in some place of the screen.



Re: [dev] [st] toggle font

2012-10-10 Thread Roberto E. Vargas Caballero
 I missed this feature a lot when light conditions and distance to
 display change, often so with a notebook, even more when different
 displays plugged. Of course, tmux helps -- kill, start new st, attach to
 the right session --, but I like this approach more.

I also need this feature, but maybe could be done in other way. I talked
about this with other persons of the list, and we liked let st be configured
using the stdin of st, so you can do it something like:

 configurator | st

And, for example, you could use dmenu and select the font you want to use.



Re: [dev] [st] toggle font

2012-10-10 Thread Nick
Quoth Roberto E. Vargas Caballero:
 I also need this feature, but maybe could be done in other way. I talked
 about this with other persons of the list, and we liked let st be configured
 using the stdin of st, so you can do it something like:
 
  configurator | st
 
 And, for example, you could use dmenu and select the font you want to use.

Eugh. That isn't the way anything else is configured. It's a pretty 
weird interface. config.h, argv switches and potentially keybindings 
are reasonable ways to configure programs. stdin is just silly.



Re: [dev] [st] toggle font

2012-10-10 Thread Kurt H Maier
On Wed, Oct 10, 2012 at 09:28:33PM +0100, Nick wrote:
 Quoth Roberto E. Vargas Caballero:
  I also need this feature, but maybe could be done in other way. I talked
  about this with other persons of the list, and we liked let st be configured
  using the stdin of st, so you can do it something like:
  
   configurator | st
  
  And, for example, you could use dmenu and select the font you want to use.
 
 Eugh. That isn't the way anything else is configured. It's a pretty 
 weird interface. config.h, argv switches and potentially keybindings 
 are reasonable ways to configure programs. stdin is just silly.
 

What's wrong with environment variables?



Re: [dev] [st] toggle font

2012-10-10 Thread Christoph Lohmann
Greetings.

On Thu, 11 Oct 2012 05:25:58 +0200 Roberto E. Vargas Caballero 
k...@shike2.com wrote:
  I missed this feature a lot when light conditions and distance to
  display change, often so with a notebook, even more when different
  displays plugged. Of course, tmux helps -- kill, start new st, attach to
  the right session --, but I like this approach more.
 
 I also need this feature, but maybe could be done in other way. I talked
 about this with other persons of the list, and we liked let st be configured
 using the stdin of st, so you can do it something like:
 
  configurator | st
 
 And, for example, you could use dmenu and select the font you want to use.

There  is  xdotool(1)  and friends for such weird stuff. Noone is really
using dmenu. It’s a bloated interface to text strings. Hopefully it will
die soon.


Sincerely,

Christoph Lohmann




Re: [dev] [st] toggle font

2012-10-10 Thread Edgaras
On Wed, Oct 10, 2012 at 09:28:33PM +0100, Nick wrote:
 Quoth Roberto E. Vargas Caballero:
  I also need this feature, but maybe could be done in other way. I talked
  about this with other persons of the list, and we liked let st be configured
  using the stdin of st, so you can do it something like:
  
   configurator | st
  
  And, for example, you could use dmenu and select the font you want to use.
 
 Eugh. That isn't the way anything else is configured. It's a pretty 
 weird interface. config.h, argv switches and potentially keybindings 
 are reasonable ways to configure programs. stdin is just silly.
 

I wouldn't say that. I would say it depends very strongly on the application.
For example for quite some time I have an idea of general key-binder, something
like xbindkeys, except that it would not read any config files, but it would
read configuration from stdin. This would allow simple key rebinding while
application is already running without introducing inconsistent configuration
loadings, i.e. from file and then some other way for rebinding on the fly. What
I want to say that stdin for configuration/commands/options for (maybe just
certain)gui applications can be a nice option (obviously for cli applications
that is not the case, because there stdin is main input for data).