Simply AWESOME. Mod+r box does autocomplete on hitting tab after the first few characters.
Alejandro - it simply works for me. I looked at the rc.lua. It simply has a promptbox and a run() used. Can someone explain how autocompletion works in the mod+r prompt box? -- Mohan Sundaram On Fri, Jun 6, 2014 at 5:50 AM, Mohan Sundaram <[email protected]> wrote: > As far as I know tab completion is a bash functionality. The mod+r opens an > input window, captures input and spawns a process. I've never tried tab in > this mode. > > I do not expect tab completion to work but it should not crash either. I'll > try it out later and see what happens. My environment is identical to yours. > > Regards > Mohan Sundaram > Sent from my mobile, please pardon typos > > On Jun 5, 2014 9:18 PM, "Alejandro Jadzinsky" <[email protected]> wrote: >> >> >> Hi first I would like say that I've being using awesome for over a year >> and I'm really happy with it. >> >> now the issue I need help with. >> >> background: >> new laptop, formatted from scratch with Ubuntu 14.04 installed. >> >> sudo apt-get install awesome (everything OK) >> >> log out >> log in using awesome as wm >> >> issue: >> Mod+r (the prompt appears) >> type gedit and press "enter" (the app is opened OK) >> type ged and press "tab" (I'm kicked off to the log-in screen) >> >> context info >> >> ale@smp:~$ uname -a >> Linux smp 3.13.0-27-generic #50-Ubuntu SMP Thu May 15 18:06:16 UTC 2014 >> x86_64 x86_64 x86_64 GNU/Linux >> ale@smp:~$ awesome -v >> awesome v3.4.15 (Never Gonna Give You Up) >> • Build: Jan 23 2014 14:28:37 for x86_64 by gcc version 4.8.2 >> (buildd@komainu) >> • D-Bus support: ✔ >> >> this is the log of the error >> (process:3868): GLib-WARNING **: GError set over the top of a previous >> GError or uninitialized memory. >> This indicates a bug in someone's code. You must ensure an error is NULL >> before it's set. >> The overwriting error message was: Failed to execute child process "" (No >> such file or directory) >> E: awesome: signal_fatal:225: dumping backtrace >> awesome(backtrace_get+0x41) [0x43c9f1] >> awesome() [0x40e8cc] >> /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f856cb01ff0] >> /lib/x86_64-linux-gnu/libc.so.6(cfree+0x1c) [0x7f856cb4ec4c] >> /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_error_free+0x12) [0x7f856f1f9332] >> awesome(spawn_system+0xba) [0x429c6a] >> awesome() [0x426cea] >> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xbfb8) [0x7f856d3e7fb8] >> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0x166ff) [0x7f856d3f26ff] >> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xc3fd) [0x7f856d3e83fd] >> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xb6eb) [0x7f856d3e76eb] >> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0(+0xc58a) [0x7f856d3e858a] >> /usr/lib/x86_64-linux-gnu/liblua5.1.so.0(lua_pcall+0x4d) [0x7f856d3e434d] >> awesome() [0x41b3b8] >> awesome(event_handle+0xb5) [0x41b875] >> awesome() [0x40e846] >> /usr/lib/x86_64-linux-gnu/libev.so.4(ev_invoke_pending+0x55) >> [0x7f856d60ce45] >> /usr/lib/x86_64-linux-gnu/libev.so.4(ev_run+0x907) [0x7f856d60ffe7] >> awesome(main+0x92f) [0x40e61f] >> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f856caecec5] >> awesome() [0x40e72e] >> >> >> I'm using the default rc.lua in /etc/xdg/awesome/rc.lua >> >> I tried using dmenu but it didn't work either >> >> >> Hope anyone has an idea to fix this. >> >> >> > -- To unsubscribe, send mail to [email protected].
