Hello. I have been using dwm for about two years and undergone many
version changes, but one bug always persisted. I am using the
following section in my xorg.conf to switch between English and
Lithuanian keyboard layouts:
Section "InputClass"
Identifier"Keyboard0"
MatchIsK
> Whenever I am using the Lithuanian keyboard layout, mouse click on
> statusbar does nothing.
Running xev I saw that when the grp_toggle is active, the button events
report a mask of 8192 (instead of 0). So something like this helps:
diff -r 5248279b9601 dwm.c
--- a/dwm.c Tue Jun 14 05:51:21
[2011-06-12 18:55] Martin Kühl
>
> [...] command-quasimode [...]
> [...] mostly modeless.
[2011-06-12 22:38] Connor Lane Smith
>
> For substitution I'm tempted to just add a keybind to switch to and
> from the command pane, which appears at the bottom of the view
> (`Quake-like', as Paul says).
> Still I wonder why you try so much to stay modeless. Modes are a real
> advantage because each mode offers a separate editor. Take vi: You can
> edit in normal mode (= the actual vi mode) or in ex mode or in insert
> mode (e.g. with ^W, ^U). You have the choice which editor (mode) you
> use for s
On Wed, Jun 15, 2011 at 1:12 PM, Peter John Hartman
wrote:
> A simple editor probably shouldn't have any more keybindings than, say,
> surf; in fact one or two less: page up/down, up/right/left/down, and find.
> One doesn't need modes for that. If you want to do something wacked out to
> your fil
On 15 June 2011 12:26, markus schnalke wrote:
> What's the difference between a mode and a ``quasimode''?
What's the difference between shift and caps lock?
> Surely, the problems are knowing in which mode you're in and switching
> modes. But in return, each mode lets you re-use your keyboard ke
On Wed, Jun 15, 2011 at 02:47:55PM +0100, Connor Lane Smith wrote:
> My view of that kind of editing is, you select the third word in the
> fourth sentence (either by leaping or with the mouse), hop over to the
> command buffer (Ctrl-Tab?), and run `x/[aeiou]/d'. If you want
> something weird like
Josh Rickmar writes:
> This makes sense. I love sam, but always wished there was a way to
> switch to the command window (~~sam~~) using the keyboard.
I think sam together with the "common" discussed keybindings (which are
partly implemented in p9p already), up/down-cursor keys for line
movemen
it's kinda annoying to lose focus in a fullscreen app if a new one is
started in the background, eg: fullscreen mplayer running in `chat` tag.
it's a bug or a feature!?
On Wed, Jun 15, 2011 at 04:42:27PM +0200, Christian Neukirchen wrote:
> Josh Rickmar writes:
>
> > This makes sense. I love sam, but always wished there was a way to
> > switch to the command window (~~sam~~) using the keyboard.
>
> I think sam together with the "common" discussed keybindings (
Josh Rickmar writes:
> Why not just keep the underlying sam the same (sam -d) but write a
> different samterm for it which does one window per buffer? This
> would also make it easy to switch to any buffer you wanted since
> it would just be part of the window manger.
That's how I'd do it if I h
On 15 June 2011 15:54, Josh Rickmar wrote:
> Why not just keep the underlying sam the same (sam -d) but write a
> different samterm for it which does one window per buffer?
That question is where my editor started. The answer to "why not" is,
sam is ugly. A common misconception is that samterm ju
- Original message -
> > Still I wonder why you try so much to stay modeless. Modes are a real
> > advantage because each mode offers a separate editor. Take vi: You can
> > edit in normal mode (= the actual vi mode) or in ex mode or in insert
> > mode (e.g. with ^W, ^U). You have the choic
On Wed, Jun 15, 2011 at 11:59 AM, Jon bradley wrote:
> I own a keyboard that has no pgup/pgdn, or arrow keys.
Did you steal it from a museum?
--Andrew Hills
> > A simple editor probably shouldn't have any more keybindings than, say,
> > surf; in fact one or two less: page up/down, up/right/left/down, and find.
> > One doesn't need modes for that. If you want to do something wacked out to
> > your file (like go to the third word on the 4th sentence and
* Andrew Hills [2011-06-15 11:51:17 -0400]:
> On Wed, Jun 15, 2011 at 11:59 AM, Jon bradley wrote:
> > I own a keyboard that has no pgup/pgdn, or arrow keys.
>
> Did you steal it from a museum?
you don't have to go to a musem for that
http://en.wikipedia.org/wiki/File:T-Mobile_G1_launch_event_
On Wed, Jun 15, 2011 at 4:02 PM, Szabolcs Nagy wrote:
> * Andrew Hills [2011-06-15 11:51:17 -0400]:
>> On Wed, Jun 15, 2011 at 11:59 AM, Jon bradley wrote:
>> > I own a keyboard that has no pgup/pgdn, or arrow keys.
>>
>> Did you steal it from a museum?
>
> you don't have to go to a musem for th
On Wed, Jun 15, 2011 at 4:24 PM, Andrew Hills wrote:
> That keyboard also doesn't have Ctrl... and I'm guessing no one here
> will bother porting the editor to an Android app.
Nokia n900/n810 have no pgdn or pgup, but do have ctrl and arrows.
--
# Kurt H Maier
On Wed, Jun 15, 2011 at 05:03:23PM -0400, Kurt H Maier wrote:
> On Wed, Jun 15, 2011 at 4:24 PM, Andrew Hills wrote:
> > That keyboard also doesn't have Ctrl... and I'm guessing no one here
> > will bother porting the editor to an Android app.
>
> Nokia n900/n810 have no pgdn or pgup, but do have
plus mark, cut and paste.
On Wed, Jun 15, 2011 at 2:11 PM, Peter John Hartman <
peterjohnhart...@gmail.com> wrote:
> On Wed, Jun 15, 2011 at 05:03:23PM -0400, Kurt H Maier wrote:
> > On Wed, Jun 15, 2011 at 4:24 PM, Andrew Hills
> wrote:
> > > That keyboard also doesn't have Ctrl... and I'm gues
On 06/15/11 21:24, Andrew Hills wrote:
On Wed, Jun 15, 2011 at 4:02 PM, Szabolcs Nagy wrote:
* Andrew Hills [2011-06-15 11:51:17 -0400]:
On Wed, Jun 15, 2011 at 11:59 AM, Jon bradley wrote:
I own a keyboard that has no pgup/pgdn, or arrow keys.
Did you steal it from a museum?
you don't
On Wed, Jun 15, 2011 at 1:40 PM, Piotr Zalewa wrote:
> I use G2 as an emergency when I need to edit via SSH.
> it works well with vi.
I have a Motorola Droid on which I use vi over SSH on a regular basis.
It is extremely painless.
--Andrew Hills
On 11 June 2011 00:40, Connor Lane Smith wrote:
> Why not just edit the individual files' main() functions (in a build
> directory) and generate a main.c, compile them, and link the object
> files together? Don't have to worry about anything except main(),
> then.
An update: I've done this, and a
23 matches
Mail list logo
