- Dillo-dev - lists.mailman3.com

Debug build

by jcid＠dillo.org

On Sun, Apr 24, 2011 at 09:41:04PM -0400, Rob S. wrote: > > Is there a way to turn on a debug mode when building? No need to patch. It builds with debug information by default. Maybe there's something in your environment... -- Cheers Jorge.-

April 25, 2011

1.3 port

by rogerx.oss＠gmail.com

> On Sun, Apr 24, 2011 at 07:36:17PM -0300, Jorge Arellano Cid wrote: >On Sat, Apr 23, 2011 at 09:57:29AM +0200, Thomas Orgis wrote: >> Am Fri, 22 Apr 2011 20:48:03 -0400 >> schrieb Rob S. <mr_semantics(a)hotmail.com>: >> [...] >> For the middle or right click: Well, I just observed Firefox >> closing a tab on middle-clicking on the handle. I don't think I >> like that. There's a close button on that handle. Middle-Click >> action onto a browser for has the connotation of pasting a URL >> into it ... and when I do it on a tab handle, I expect the URL >> being loaded in that tab. Not closing. Even worse for right >> click, though: That really is wired to the appearance of a >> context menu from countless other GUIs -- and no immediate >> action on its own. >> >> So, if a click has to close a tab, it should be the middle >> click, but it's the lesser of two evils, IMHO;-) > > I understand... > > >> And now, since there seems to be a "standard" >> set by other browsers about closing a tab with middle click, >> why has dillo have to choose the right click for the same >> action? > > Because it is surprisingly easy to use right-click! > >> Isn't that a guarantee to annoy any converts? > > No. See the two posts above (and my preference). > >> For what gain? > > Middle click is not handy with a scroll wheel middle button. > > Now, given that middle click became the standard, we can set it >as default and also add a dillorc preference for those of us that >really enjoy right click. No problem. You are somewhat correct here Jorge. I too have a scroll wheel for a middle button and find the right-mouse-click much easier to close tabs! (In Seamonkey browsers, I think the middle button is paste-and-open-url-in-window action.) However, as I mentioned, the other are right about the ctrl-q & ctrl-w being somewhat a standard. The only time I mind is when I use a standard browser, as I end up accidentally quiting the standard browser after using ctrl-q. Maybe I should complain to the Standard Browsers that they're not following the Dillo Standard? -- Roger http://rogerx.freeshell.org/

April 25, 2011

Debug build

by mr_semantics＠hotmail.com

> To: dillo-dev(a)dillo.org > Subject: Re: [Dillo-dev] Debug build > Date: Sun, 24 Apr 2011 21:52:18 -0400 > From: obeythepenguin(a)gmail.com > > On Sun, 24 Apr 2011 21:41:04 -0400, Rob S. <mr_semantics(a)hotmail.com> > wrote: > > > Is there a way to turn on a debug mode when building? I have done > > ./configure --help, and don't see much there. Basically I am stuck - I > > built dillo 1.3 on my opensuse machine, and it was segfaulting. I won't > > fill in the details of a long story, but I went and built it on a Fedora > > 14 machine (actually the same machine, just booted into Fedora), and the > > segfault did not happen. Built it on Linux Mint (Debian edition) and > > the same segfault is back. It is showing the problem as being in libc, > > but when I do a backtrace, there is not much meaningful stuff there. I > > would basically like to see more information - starting with turning off > > the optimisation, and possibly cranking the level of the debug from -g > > to -ggdb3. I just wanted to ask before I started monkeying with the > > configure files... > > This patch might help: > http://dillo-win32.sourceforge.net/files/01-dillo-r1785.configure.in.diff > > It adds an --enable-debug option, among other things (it also has some > fixes for building on Windows). You'll have to run ./autogen.sh to > re-generate your configure script after applying it. Thank you very much. ?This gave me an idea of where to start (the patch was good enough, but I wanted to tweak things, and now I know where. ? Before that I was thinking I would have to learn about how to use autotools ::shudders::. ?

April 25, 2011

Debug build

by obeythepenguin＠gmail.com

On Sun, 24 Apr 2011 21:41:04 -0400, Rob S. <mr_semantics(a)hotmail.com> wrote: > Is there a way to turn on a debug mode when building? I have done > ./configure --help, and don't see much there. Basically I am stuck - I > built dillo 1.3 on my opensuse machine, and it was segfaulting. I won't > fill in the details of a long story, but I went and built it on a Fedora > 14 machine (actually the same machine, just booted into Fedora), and the > segfault did not happen. Built it on Linux Mint (Debian edition) and > the same segfault is back. It is showing the problem as being in libc, > but when I do a backtrace, there is not much meaningful stuff there. I > would basically like to see more information - starting with turning off > the optimisation, and possibly cranking the level of the debug from -g > to -ggdb3. I just wanted to ask before I started monkeying with the > configure files... This patch might help: http://dillo-win32.sourceforge.net/files/01-dillo-r1785.configure.in.diff It adds an --enable-debug option, among other things (it also has some fixes for building on Windows). You'll have to run ./autogen.sh to re-generate your configure script after applying it. Cheers, ~Benjamin

April 25, 2011

Debug build

by mr_semantics＠hotmail.com

Is there a way to turn on a debug mode when building? I have done ./configure --help, and don't see much there. Basically I am stuck - I built dillo 1.3 on my opensuse machine, and it was segfaulting. I won't fill in the details of a long story, but I went and built it on a Fedora 14 machine (actually the same machine, just booted into Fedora), and the segfault did not happen. Built it on Linux Mint (Debian edition) and the same segfault is back. It is showing the problem as being in libc, but when I do a backtrace, there is not much meaningful stuff there. I would basically like to see more information - starting with turning off the optimisation, and possibly cranking the level of the debug from -g to -ggdb3. I just wanted to ask before I started monkeying with the configure files...

April 25, 2011

1.3 port

by mr_semantics＠hotmail.com

> Now, given that middle click became the standard, we can set it > as default and also add a dillorc preference for those of us that > really enjoy right click. No problem. This makes me happy - at least have the option to change it (which I will) to using right click to close. ^_^

April 25, 2011

1.3 port

by jcid＠dillo.org

On Sat, Apr 23, 2011 at 09:57:29AM +0200, Thomas Orgis wrote: > Am Fri, 22 Apr 2011 20:48:03 -0400 > schrieb Rob S. <mr_semantics(a)hotmail.com>: > [...] > For the middle or right click: Well, I just observed Firefox > closing a tab on middle-clicking on the handle. I don't think I > like that. There's a close button on that handle. Middle-Click > action onto a browser for has the connotation of pasting a URL > into it ... and when I do it on a tab handle, I expect the URL > being loaded in that tab. Not closing. Even worse for right > click, though: That really is wired to the appearance of a > context menu from countless other GUIs -- and no immediate > action on its own. > > So, if a click has to close a tab, it should be the middle > click, but it's the lesser of two evils, IMHO;-) I understand... > And now, since there seems to be a "standard" > set by other browsers about closing a tab with middle click, > why has dillo have to choose the right click for the same > action? Because it is surprisingly easy to use right-click! > Isn't that a guarantee to annoy any converts? No. See the two posts above (and my preference). > For what gain? Middle click is not handy with a scroll wheel middle button. Now, given that middle click became the standard, we can set it as default and also add a dillorc preference for those of us that really enjoy right click. No problem. -- Cheers Jorge.-

April 25, 2011

1.3 port

by thomas-forum＠orgis.org

Am Sun, 24 Apr 2011 11:57:52 -0800 schrieb Roger <rogerx.oss(a)gmail.com>: > Looking at this from a coding perspective, the ctrl+q combo will close tabs, > ***as well as*** quit the application. Yes, that's the case with dillo... I don't think that this is the best way. I'd have to look up whatever the "official" GUIdeline should be, but in NEdit (as well as xpdf) ctrl+w only closes open documents (which may be tabs, or some of the multiple windows of the app), where ctrl+q is needed to close the application... oh; in xpdf you need simple "q" for closing the app, ctrl+q won't do it. Lame. So much for a standard. Hm. You checked Seamonkey ... Let's look at another behemoth: OpenOffice (a reason to start it once in a month;-). Yup. The same: Ctrl+w closes files, but also the app when no file open. Ctrl+q closes the app right away. > So maybe ctrl+w should be assigned to close tabs within Dillo? (I've noticed > too, when I go to close a tab within Seamonkey I would accidentally press > ctrl+q to close a window -- and watch in horror as Seamonkey quit 5+ tabs of > active research! ;-) Yeah, it seems that using ctrl+w for closing tabs and dillo would be what others do (though I would prefer to limit the closing to ctrl+q). But then, re-defining ctrl+q to close dillo right away would mean a big change from the existing function. Anyhow, my comment was mainly about introducing yet another shift with the different working of the right or middle mouse buttons... the answer to the keyboard shortcuts might be user-configurable mappings anyway -- which still leaves open the question for the sane default. Alrighty then, Thomas.

April 25, 2011

1.3 port

by jcid＠dillo.org

On Sun, Apr 24, 2011 at 11:57:52AM -0800, Roger wrote: > > On Sat, Apr 23, 2011 at 09:57:29AM +0200, Thomas Orgis wrote: > >Am Fri, 22 Apr 2011 20:48:03 -0400 > >schrieb Rob S. <mr_semantics(a)hotmail.com>: > > > >> > The right-click close tab works far easier then ctrl-q... and I'm a keyboard > >> > fanatic! > >> > >> I am in 100% Agreement here - I know Ben mentioned the same functionality can be had with a middle click on some other browsers, but with my mouse, it is not nearly as nice clicking a middle mouse button to close tabs (I tested this on some other browsers) as it is right clicking. > > > > ... > > >But then... given the precedence of Ctrl+w / Ctrl+q being in place for GUI apps since ages (heck, even xpdf closes the file with Ctrl+w and the whole app with Ctrl+q) ... why does dillo have to have a slightly different idea about the workins of these shortcuts? And now, since there seems to be a "standard" set by other browsers about closing a tab with middle click, why has dillo have to choose the right click for the same action? Isn't that a guarantee to annoy any converts? For what gain? > > Looking at this from a coding perspective, the ctrl+q combo will close tabs, > ***as well as*** quit the application. Seems to be a dual purpose. > Checking Seamonkey, so OK, ctrl+w does quit the browser while closing > tabs/windows, too! > > So maybe ctrl+w should be assigned to close tabs within Dillo? (I've noticed > too, when I go to close a tab within Seamonkey I would accidentally press > ctrl+q to close a window -- and watch in horror as Seamonkey quit 5+ tabs of > active research! ;-) Don't worry, this is quite easy to change... And today it looks like Ctrl-w has won as the "de facto" tab closer for browsers. We can follow suit easily. -- Cheers Jorge.-

April 25, 2011

1.3 port

by rogerx.oss＠gmail.com

> On Sat, Apr 23, 2011 at 09:57:29AM +0200, Thomas Orgis wrote: >Am Fri, 22 Apr 2011 20:48:03 -0400 >schrieb Rob S. <mr_semantics(a)hotmail.com>: > >> > The right-click close tab works far easier then ctrl-q... and I'm a keyboard >> > fanatic! >> >> I am in 100% Agreement here - I know Ben mentioned the same functionality can be had with a middle click on some other browsers, but with my mouse, it is not nearly as nice clicking a middle mouse button to close tabs (I tested this on some other browsers) as it is right clicking. > ... >But then... given the precedence of Ctrl+w / Ctrl+q being in place for GUI apps since ages (heck, even xpdf closes the file with Ctrl+w and the whole app with Ctrl+q) ... why does dillo have to have a slightly different idea about the workins of these shortcuts? And now, since there seems to be a "standard" set by other browsers about closing a tab with middle click, why has dillo have to choose the right click for the same action? Isn't that a guarantee to annoy any converts? For what gain? Looking at this from a coding perspective, the ctrl+q combo will close tabs, ***as well as*** quit the application. Seems to be a dual purpose. Checking Seamonkey, so OK, ctrl+w does quit the browser while closing tabs/windows, too! So maybe ctrl+w should be assigned to close tabs within Dillo? (I've noticed too, when I go to close a tab within Seamonkey I would accidentally press ctrl+q to close a window -- and watch in horror as Seamonkey quit 5+ tabs of active research! ;-) -- Roger http://rogerx.freeshell.org/

April 24, 2011