Run command with an ipython-like history - possible?

2012-08-17 Thread Paweł Rumian
Hello,

I am wondering is it possible to make the 'run command' history behave
like ipython?
That means that after entering the first characters, the history would
be restricted to commands starting with the chars entered.
For those not familiar with ipython - the same thing can be achieved
in bash using history-search-backward function.

br,
Paweł

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.


Re: Run command with an ipython-like history - possible?

2012-08-17 Thread Diep Pham Van
dmenu?
On Fri, Aug 17, 2012 at 10:21:08AM +0200, Paweł Rumian wrote:
 Hello,

 I am wondering is it possible to make the 'run command' history behave
 like ipython?
 That means that after entering the first characters, the history would
 be restricted to commands starting with the chars entered.
 For those not familiar with ipython - the same thing can be achieved
 in bash using history-search-backward function.

 br,
 Paweł

 --
 To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

-- 
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.


Re: Run command with an ipython-like history - possible?

2012-08-17 Thread Paweł Rumian
No, it is all about the history.

Paweł

2012/8/17 Diep Pham Van i...@favadi.com:
 dmenu?
 On Fri, Aug 17, 2012 at 10:21:08AM +0200, Paweł Rumian wrote:
 Hello,

 I am wondering is it possible to make the 'run command' history behave
 like ipython?
 That means that after entering the first characters, the history would
 be restricted to commands starting with the chars entered.
 For those not familiar with ipython - the same thing can be achieved
 in bash using history-search-backward function.

 br,
 Paweł

 --
 To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.


Re: Working with multiple screens

2012-08-17 Thread Abhijeet R
I am still having the issue. I tried searching on Google but relevant 
results. Sometimes, even if I open a window in screen2, if I maximize 
it using Mod4+m, it gets back to the screen1. (This doesn't happen 
everytime) I also use Alt+F2 to run dmenu_run. Sometimes, my mouse in 
on screen2  still when I do Alt+F2, the dmenu_run opens at screen1. 
What can be the issue?


My awesome config can be found at: 
https://github.com/shadyabhi/dot-files/tree/master/.config/awesome


This is really driving me crazy.

On Thu 16 Aug 2012 04:19:34 PM IST, Wayne Werner wrote:

On Thu, 16 Aug 2012, Abhijeet R wrote:


So, I have no prior experience with working with multiple screens.
It's my first day at job  I got a monitor.

I used

|xrandr --output VGA1 --mode 1680x1050 --right-of LVDS1
|

Now, if I move my mouse to the edges, my mouse switches to the other
screen. But, when I execute commands to maximize a client, switching
clients using M-j,k, shortcut for dmenu_run, all shortcuts for
executing others, It happens in my laptop screen itself.

What do I need to do?


I may be way off in this, but I think if you do Mod4 + Control + j
(see man awesome), it will change your focus. +j is next screen, +k is
previous screen.

HTH,
Wayne


--
Regards,
Abhijeet
http://blog.abhijeetr.com

--
To unsubscribe, send mail to awesome-unsubscr...@naquadah.org.