Personally, I think it's essential. Not everyone is ready to either live with tons of apps in their tray(kde, gnome, xfce, Windows) or move to more advanced WM(the 'window manager' for windows CAN be changed out for a better open-source one, but...why?) but might be ready for a more powerful browser. Heck, some people don't like the mouse, but might not want to change much else!
I'm going to be moving away from the KDE desktop to Awesome, but still using KDE apps. In all honesty I'd prefer to keep my buffer switching commands and my app focus/bring to top commands totally separate. I try to organise/think about things according to task. I have my virtual desktops named according to what I do on each: Admin, Contact, Media, and New(for making things). For me these features have been a godsend(thank you spaghetti monster!) and are what's given me the courage to move to Awesome. A week with this browser has been enough to make me frustrated with the mouse. I think of it like a video game controller, and trying to use software with one is akin to playing a first-person-shooter with a gamepad: possible, but frustrating and slow. In fact I know someone who's going to be trying conkeror soon to move away from using the mouse, but doesn't want to leave xfce's desktop. For him, I imaging having 4-5 app instances in the tray would be quite annoying. It reminds me of something I read in a lisp blog: If you think it has too many features, then pretend they're not there. You don't have to use them I realise this is likely more about what features to maintain, and they were a little crass(it's a rough memory of a quote! I can't think of a better way to put it! Forgive me!*seppuku*), but I think the point stands. Basically, I think it's very important to me right now, and I don't like change(autistic(and lazy)). Please continue improving Conkeror, and please keep the splitting/multibuffers. > Send Conkeror mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.mozdev.org/mailman/listinfo/conkeror > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Conkeror digest..." > > Today's Topics: > > 1. Re: I think these are two bugs. (Changying Li) > 2. Re: I think these are two bugs. (Jeremy Maitin-Shepard) > 3. Re: I think these are two bugs. (Changying Li) > 4. Re: I think these are two bugs. (Jeremy Maitin-Shepard) > 5. Re: I think these are two bugs. (Jeremy Maitin-Shepard) > 6. Poll: how important is emacs-style splitting of top-level > windows into multiple panes? (Jeremy Maitin-Shepard) > > > ---------- Forwarded message ---------- > From: Changying Li <[EMAIL PROTECTED]> > To: [email protected] > Date: Thu, 17 Apr 2008 15:34:58 +0800 > Subject: Re: [Conkeror] I think these are two bugs. > Jeremy Maitin-Shepard <[EMAIL PROTECTED]> writes: > > > Changying Li <[EMAIL PROTECTED]> writes: > > > >> 1. under archlinux, xmonad wm, if I press 'menu' key ( the right key of > >> right WINDOWS key), the conkeror will be closed with error 'segment > >> fault'. I never bind 'menu'key to any other commands. > > > > I'm not sure about this problem, but it is possible that upgrading to a > > different version of xulrunner will fix it. > > > >> 2. under windows xp or archlinux, sometime I cant run any command (any > >> key) , with an error -- but I cant catch it, and not write it down -- > >> even c-g or c-x c-c. please tell me how to catch that error message. > > > > If you run Conkeror from a terminal, you should be able to see a stack > > trace of the error in the terminal. On Windows, pass the -console > > command-line argument to Conkeror to open a terminal, in which errors > > will be displayed. > I met this error again: > Follow: > call interactively: Type Error: s.manager is null > > this error randomly appeared, or I hasn't find its rule. > > > > -- > > Jeremy Maitin-Shepard > > -- > > Thanks & Regards > > Changying Li > > > > > ---------- Forwarded message ---------- > From: Jeremy Maitin-Shepard <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Thu, 17 Apr 2008 10:16:21 -0400 > Subject: Re: [Conkeror] I think these are two bugs. > Changying Li <[EMAIL PROTECTED]> writes: > > > I met this error again: > > Follow: > > call interactively: Type Error: s.manager is null > > > this error randomly appeared, or I hasn't find its rule. > > You didn't happen to get a stack trace in the terminal, did you? I > tried to track down the problem from that brief description alone, but I > was not able to. A stack trace would make it much easier. > > As I said, if you are running on Linux, the stack trace will be printed > to the terminal in which you invoke conkeror. On Windows, you need to > invoke Conkeror with the -console command-line option in order to have > it open a terminal, in which the stack trace will be visible. > > -- > Jeremy Maitin-Shepard > > > > ---------- Forwarded message ---------- > From: Changying Li <[EMAIL PROTECTED]> > To: [email protected] > Date: Thu, 17 Apr 2008 23:57:43 +0800 > Subject: Re: [Conkeror] I think these are two bugs. > Jeremy Maitin-Shepard <[EMAIL PROTECTED]> writes: > > > Changying Li <[EMAIL PROTECTED]> writes: > > > >> I met this error again: > >> Follow: > >> call interactively: Type Error: s.manager is null > > > >> this error randomly appeared, or I hasn't find its rule. > > > > You didn't happen to get a stack trace in the terminal, did you? I > > tried to track down the problem from that brief description alone, but I > > was not able to. A stack trace would make it much easier. > > > > As I said, if you are running on Linux, the stack trace will be printed > > to the terminal in which you invoke conkeror. On Windows, you need to > > invoke Conkeror with the -console command-line option in order to have > > it open a terminal, in which the stack trace will be visible. > ok, I will try, but the error is not very frequently so that I must run > it from terminal always. > > > > -- > > Jeremy Maitin-Shepard > > -- > > Thanks & Regards > > Changying Li > > > > > ---------- Forwarded message ---------- > From: Jeremy Maitin-Shepard <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Thu, 17 Apr 2008 12:08:24 -0400 > Subject: Re: [Conkeror] I think these are two bugs. > Changying Li <[EMAIL PROTECTED]> writes: > > > Jeremy Maitin-Shepard <[EMAIL PROTECTED]> writes: > >> Changying Li <[EMAIL PROTECTED]> writes: > >> > >>> I met this error again: > >>> Follow: > >>> call interactively: Type Error: s.manager is null > >> > >>> this error randomly appeared, or I hasn't find its rule. > >> > >> You didn't happen to get a stack trace in the terminal, did you? I > >> tried to track down the problem from that brief description alone, but I > >> was not able to. A stack trace would make it much easier. > >> > >> As I said, if you are running on Linux, the stack trace will be printed > >> to the terminal in which you invoke conkeror. On Windows, you need to > >> invoke Conkeror with the -console command-line option in order to have > >> it open a terminal, in which the stack trace will be visible. > > ok, I will try, but the error is not very frequently so that I must run > > it from terminal always. > > You could possibly run it as: conkeror >> some-log-file.txt > > And then you don't need to run it from a terminal. > > -- > Jeremy Maitin-Shepard > > > > ---------- Forwarded message ---------- > From: Jeremy Maitin-Shepard <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Date: Thu, 17 Apr 2008 12:49:04 -0400 > Subject: Re: [Conkeror] I think these are two bugs. > John Foerch helped me track this down. I've pushed a fix. You > shouldn't need to worry about running Conkeror always in a terminal > now. :) > > -- > Jeremy Maitin-Shepard > > > > ---------- Forwarded message ---------- > From: Jeremy Maitin-Shepard <[EMAIL PROTECTED]> > To: [email protected] > Date: Thu, 17 Apr 2008 13:23:06 -0400 > Subject: [Conkeror] Poll: how important is emacs-style splitting of top-level > windows into multiple panes? > How useful would it be for Conkeror to support Emacs-style splitting of > top-level windows (frames in Emacs terminology) into multiple panes > (windows in Emacs terminology)? > > For me, it is essentially not at all useful, because I don't even use > multiple buffers per window, and I'd just assume let my window manager > take care of handling each buffer. Splitting and multiple buffers per > window are in some sense window manager features implemented in the > application, and for both consistency and simplicity, it just seems > better to leave window manager features in the window manager. > > Microsoft Windows is, of course, a bit of an exception since the "window > manager" is sort of fixed, not very good, and not easily changeable. > > If you have thoughts on this, send a reply. > > -- > Jeremy Maitin-Shepard > > > _______________________________________________ > Conkeror mailing list > [email protected] > https://www.mozdev.org/mailman/listinfo/conkeror > > _______________________________________________ Conkeror mailing list [email protected] https://www.mozdev.org/mailman/listinfo/conkeror
