Hi there, For those of you that wrote me willing to join the project as developers, and to the older ones too ;), here's a pending list of simple matters that need patches. Just in case! 1.- Check the "pending issues" dillo thread in FLTK' site: http://fltk.org/newsgroups.php?gfltk.general+T (search for "dillo") there you'll find a few and some hints too. 2.- CLI From dillo1: $ dillo1 --help Usage: dillo [OPTIONS] [URL|FILE]... Options: -x, --xid XID Open first Dillo window in an existing GtkSocket which window ID is XID (decimal). -v, --version Display version info and exit. -h, --help Display this help text and exit. -f, --fullwindow Start in full window mode: hide address bar, navigation buttons, menu, and status bar. -l, --local Don't follow links for this URL(s). -g, -geometry GEO Set initial window position where GEO is <width>x<height>{+-}<x>{+-}<y> -D, --debug-rendering Draw additionaly several lines in a web page, representing its structure. For debugging. URL URL to browse. FILE Local FILE to vie We need to mimic this. The only complex point is XID option. We don't yet know how to do window embedding by XID with FLTK2. Asking in FLTK general may help. I hope this gets somebody started. /me goes back, to CSS. -- Cheers Jorge.-
Jorge, is there any chance of my various patches getting looked at in the near future? I feel reluctant to start playing with css until then.
Jorge wrote:
On Sat, Nov 08, 2008 at 02:49:35PM +0000, corvid wrote:
Jorge, is there any chance of my various patches getting looked at in the near future? I feel reluctant to start playing with css until then.
Oh, which ones besided the "view source" one?
patch: click elsewhere on page, fltk widget loses focus patch: prefs.vw_fontname as fltk ui's default font patch: middle-click submits in new window/tab (This last one had been sent directly to Jorge. It's a cheap way to get some degree of pages-remember-form-data without having to, you know, actually remember form data.)
On Sat, Nov 08, 2008 at 04:31:41PM +0000, corvid wrote:
Jorge wrote:
On Sat, Nov 08, 2008 at 02:49:35PM +0000, corvid wrote:
Jorge, is there any chance of my various patches getting looked at in the near future? I feel reluctant to start playing with css until then.
Oh, which ones besided the "view source" one?
patch: click elsewhere on page, fltk widget loses focus
patch: prefs.vw_fontname as fltk ui's default font
patch: middle-click submits in new window/tab (This last one had been sent directly to Jorge. It's a cheap way to get some degree of pages-remember-form-data without having to, you know, actually remember form data.)
Hey that's clever! I already thought about actually implementing pages-remember-form-data... A problem may be how to communicate that feature to the user. Cheers, Johannes
Johannes wrote:
On Sat, Nov 08, 2008 at 04:31:41PM +0000, corvid wrote:
patch: middle-click submits in new window/tab (This last one had been sent directly to Jorge. It's a cheap way to get some degree of pages-remember-form-data without having to, you know, actually remember form data.)
Hey that's clever! I already thought about actually implementing pages-remember-form-data...
I wouldn't want to stand in the way of that :) Where do you think form data would fit best? In the history list? (nav stack would require a lot of digging around to clear upon reload, and the cache is low-level and full of images)
A problem may be how to communicate that feature to the user.
Quite true.
Dillo, alone of all browsers I know, cannot handle "www.site.xyz.com," by simply converting it on the fly to "http://www.site.xyz.com" Is there some reason why not? Could it be implemented, or has it been, in the next release? I use Dillo by default, because it's fast and safe, and also more convenient to c&p from (by a country mile, if the URL is very long) than my email, in case I hit a site that it doesn't handle, but that I want a closer look at; or in case I want to bookmark it, or keep it open, in some other browser. Getting hung up on the absence of "http://" is a large, buzzing fly in that ointment. -- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
Hi, On Sat, Nov 08, 2008 at 03:40:08PM -0500, me at swva wrote:
Dillo, alone of all browsers I know, cannot handle "www.site.xyz.com," by simply converting it on the fly to "http://www.site.xyz.com"
It works fine for me. Do you have an example where it doesn't work for you? What version of dillo are you using? Cheers, Johannes
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
Hi,
On Sat, Nov 08, 2008 at 03:40:08PM -0500, me at swva wrote:
Dillo, alone of all browsers I know, cannot handle "www.site.xyz.com," by simply converting it on the fly to "http://www.site.xyz.com"
It works fine for me. Do you have an example where it doesn't work for you? What version of dillo are you using?
Iirc, it has *always* done this to me, on all machines, for years out of mind, on all URLs. Just to check, I did this as root : [root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update [root@Hbsk2 btth]# -- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
On Sat, Nov 08, 2008 at 04:19:19PM -0500, me at swva wrote:
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
Hi,
On Sat, Nov 08, 2008 at 03:40:08PM -0500, me at swva wrote:
Dillo, alone of all browsers I know, cannot handle "www.site.xyz.com," by simply converting it on the fly to "http://www.site.xyz.com"
It works fine for me. Do you have an example where it doesn't work for you? What version of dillo are you using?
Iirc, it has *always* done this to me, on all machines, for years out of mind, on all URLs.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update [root@Hbsk2 btth]#
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6. If you enter "google.com" in the location bar and hit return it doesn't go to google?
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo ^^^^^^^^^^^^^^^^ Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]#
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6.
For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
If you enter "google.com" in the location bar and hit return it doesn't go to google?
It does indeed. I'm putting this badly. I run Alpine 2.0; it is set to launch the default browser, which is dillo -- and URLs in emails are what I use a default browser for. Does this mean something in my Alpine settings (and my Pine 4.64 settings, which it took over) is wrong? My Fedora default browser setting is simply "dillo %s"; my Alpine setting is something I'll have to dig for, as it's buried way deep. -- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
me at swva wrote:
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo
^^^^^^^^^^^^^^^^
Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]#
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6.
For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
That's life. In Fedora, nor even Rawhide, isn't Dillo v2.0. Two reasons: 1) No one packed FLTK 2.x, check repository there's still 1.1.9. 2) Because of (1) no Dillo 2. Although Fedora is usually fresh, in case of Dillo it's still on Dillo 0.8.6 mainline. Feel free to file bug (bugzilla.redhat.com) against Dillo and Package Review for FLTK2, but be aware that having unstable FLTK 2.x in Fedora might be quite fight. (Believe me I am Fedora packager.) Feel free to use mines with SSL enabled (no guarantee at all), both F10. http://www.stud.fit.vutbr.cz/~xnowak01/Fedora/dillo/dillo-2.0-1.i386.rpm http://www.stud.fit.vutbr.cz/~xnowak01/Fedora/fltk/fltk2-2.0.x.r6403-0.1.i38... But you'll probably have more luck with those: http://www.hyperborea.org/software/dillo/rpms/ Enjoy.
If you enter "google.com" in the location bar and hit return it doesn't go to google?
It does indeed. I'm putting this badly.
I run Alpine 2.0; it is set to launch the default browser, which is dillo -- and URLs in emails are what I use a default browser for.
Does this mean something in my Alpine settings (and my Pine 4.64 settings, which it took over) is wrong? My Fedora default browser setting is simply "dillo %s"; my Alpine setting is something I'll have to dig for, as it's buried way deep.
Might be here interesting whether Dillo2 cooperates nicely with alpine, let us know. Michal
On Sat, Nov 08, 2008 at 10:58:43PM +0100, Michal Nowak wrote:
me at swva wrote:
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo
^^^^^^^^^^^^^^^^
Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]#
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6.
For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
That's life. In Fedora, nor even Rawhide, isn't Dillo v2.0. Two reasons:
1) No one packed FLTK 2.x, check repository there's still 1.1.9. 2) Because of (1) no Dillo 2.
Although Fedora is usually fresh, in case of Dillo it's still on Dillo 0.8.6 mainline. Feel free to file bug (bugzilla.redhat.com) against Dillo and Package Review for FLTK2, but be aware that having unstable FLTK 2.x in Fedora might be quite fight. (Believe me I am Fedora packager.)
Dillo2 doesn't need an FLTK2 package installed! It can be statically linked in. One package, that's it. (this is the default BTW). Now, if distros need to also provide source packages by policy, then that's a different story. Please clarify me because I've read that complaint a few times, and don't yet know whether it's my fault not making the statical linking clear enough to packagers, or if there's a packaging policy issue I don't know of. :) -- Cheers Jorge.-
Jorge Arellano Cid wrote:
On Sat, Nov 08, 2008 at 10:58:43PM +0100, Michal Nowak wrote:
me at swva wrote:
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo
^^^^^^^^^^^^^^^^
Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]# On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6. For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
That's life. In Fedora, nor even Rawhide, isn't Dillo v2.0. Two reasons:
1) No one packed FLTK 2.x, check repository there's still 1.1.9. 2) Because of (1) no Dillo 2.
Although Fedora is usually fresh, in case of Dillo it's still on Dillo 0.8.6 mainline. Feel free to file bug (bugzilla.redhat.com) against Dillo and Package Review for FLTK2, but be aware that having unstable FLTK 2.x in Fedora might be quite fight. (Believe me I am Fedora packager.)
Dillo2 doesn't need an FLTK2 package installed! It can be statically linked in. One package, that's it. (this is the default BTW).
Sure I am aware of that, but wrt Fedora, it's something neat forbidden https://fedoraproject.org/wiki/PackagingDrafts/StaticLibraryPolicy unless necessary (and this is not the case).
Now, if distros need to also provide source packages by policy, then that's a different story.
Correct. FLTK can't just be present in compile time, somehow, toolchain has to be clear and for everyone from day0.
Please clarify me because I've read that complaint a few times, and don't yet know whether it's my fault not making the statical linking clear enough to packagers, or if there's a packaging policy issue I don't know of. :)
From my POV, in distros we don't want static built packages; security flaws in linked-in libraries is the main concern. One has to rebuild all apps with those libraries, not just the library (obvious). I don't thing it will be that hard to get FLTK & Dillo2 into Fedora, the thing is that no one did it till now :). (And I ma pretty busy at work & uni :) ). Michal
On Sun, Nov 09, 2008 at 01:12:01PM +0100, Michal Nowak wrote:
Jorge Arellano Cid wrote:
On Sat, Nov 08, 2008 at 10:58:43PM +0100, Michal Nowak wrote:
me at swva wrote:
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo
^^^^^^^^^^^^^^^^
Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]# On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6. For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
That's life. In Fedora, nor even Rawhide, isn't Dillo v2.0. Two reasons:
1) No one packed FLTK 2.x, check repository there's still 1.1.9. 2) Because of (1) no Dillo 2.
Although Fedora is usually fresh, in case of Dillo it's still on Dillo 0.8.6 mainline. Feel free to file bug (bugzilla.redhat.com) against Dillo and Package Review for FLTK2, but be aware that having unstable FLTK 2.x in Fedora might be quite fight. (Believe me I am Fedora packager.)
Dillo2 doesn't need an FLTK2 package installed! It can be statically linked in. One package, that's it. (this is the default BTW).
Sure I am aware of that, but wrt Fedora, it's something neat forbidden
https://fedoraproject.org/wiki/PackagingDrafts/StaticLibraryPolicy
unless necessary (and this is not the case).
Now, if distros need to also provide source packages by policy, then that's a different story.
Correct. FLTK can't just be present in compile time, somehow, toolchain has to be clear and for everyone from day0.
Please clarify me because I've read that complaint a few times, and don't yet know whether it's my fault not making the statical linking clear enough to packagers, or if there's a packaging policy issue I don't know of. :)
From my POV, in distros we don't want static built packages; security flaws in linked-in libraries is the main concern. One has to rebuild all apps with those libraries, not just the library (obvious).
I don't thing it will be that hard to get FLTK & Dillo2 into Fedora, the thing is that no one did it till now :). (And I ma pretty busy at work & uni :) ).
Thanks a lot for the explanation! Although it may be difficult to get a FLTK2 package in the distro because FLTK2 doesn't have a stable release yet. I mean, if policies mandate not to include alpha or beta libraries, we're out... It'd be good to know this (for Fedora, Ubuntu and Debian at least). That way we can ask the FLTK team about their schedule plans. -- Cheers Jorge.-
On Sun, 9 Nov 2008, Jorge Arellano Cid wrote:
I don't thing it will be that hard to get FLTK & Dillo2 into Fedora, the thing is that no one did it till now :). (And I ma pretty busy at work & uni :) ).
Thanks a lot for the explanation!
Although it may be difficult to get a FLTK2 package in the distro because FLTK2 doesn't have a stable release yet. I mean, if policies mandate not to include alpha or beta libraries, we're out...
It'd be good to know this (for Fedora, Ubuntu and Debian at least). That way we can ask the FLTK team about their schedule plans.
I hate to be taking up so much time from people I know are working so hard already, but let me ask just one more : should I be taking this up with Alpine people? Or is one of you going to do that? (You could certainly do it a lot better.) Or have you determined that the trouble is in Fedora and not in Alpine? -- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
On Sun, Nov 09, 2008 at 10:27:11AM -0500, me at swva wrote:
On Sun, 9 Nov 2008, Jorge Arellano Cid wrote:
I don't thing it will be that hard to get FLTK & Dillo2 into Fedora, the thing is that no one did it till now :). (And I ma pretty busy at work & uni :) ).
Thanks a lot for the explanation!
Although it may be difficult to get a FLTK2 package in the distro because FLTK2 doesn't have a stable release yet. I mean, if policies mandate not to include alpha or beta libraries, we're out...
It'd be good to know this (for Fedora, Ubuntu and Debian at least). That way we can ask the FLTK team about their schedule plans.
I hate to be taking up so much time from people I know are working so hard already, but let me ask just one more : should I be taking this up with Alpine people? Or is one of you going to do that? (You could certainly do it a lot better.) Or have you determined that the trouble is in Fedora and not in Alpine?
I ended installing alpine here to check this issue. The URL viewer is taken from .mailcap. When set properly, it works (at least here it works with Ubuntu 8.04.1, so it's not an alpine issue). If you have something like this in your mailcap: (all in one line) text/html; /usr/local/bin/dillo -l -f '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html it works with dillo1. Something like: text/html; /usr/local/bin/dillo -l -f -x XID '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html makes dillo1 exit, so it doesn't work. Reason: XID should be a number containing a window ID, where dillo should embed itself, not a literal string! Note: dillo2 will work with the flawed parameter because as it can't embed itself yet, the parameter is blithely ignored! :-) HTH. -- Cheers Jorge.-
On Tue, 11 Nov 2008, Jorge Arellano Cid wrote: [...]
I ended installing alpine here to check this issue.
The URL viewer is taken from .mailcap. When set properly, it works (at least here it works with Ubuntu 8.04.1, so it's not an alpine issue).
OK, good; but you're over my head. I don't find anything named .mailcap on my machine. Neither does my search function. Since I've been running Pine for years, I have a .pinerc rather than an .alpinerc; but I don't find anything like what you say there, either.
If you have something like this in your mailcap: (all in one line)
text/html; /usr/local/bin/dillo -l -f '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html
it works with dillo1.
About now, I should probably mention that I do my email different ways from different addresses. The main one is remote. It does open links that include "http://" -- in dillo *here*, not on the remote machine -- but not ones without. The same is also true when I run Alpine against the address I'm using at this moment.
Something like:
text/html; /usr/local/bin/dillo -l -f -x XID '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html
I'm guessing that I should c&p that into my .pinerc somewhere, or into the interface Alpine gives me by typing M > S > C (Main menu to Setup to Configure); but I don't know where.
makes dillo1 exit, so it doesn't work. Reason: XID should be a number containing a window ID, where dillo should embed itself, not a literal string!
Now you're way to Helen Gone over my head. Sorry.
Note: dillo2 will work with the flawed parameter because as it can't embed itself yet, the parameter is blithely ignored! :-)
-- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
On Fri, Nov 14, 2008 at 01:21:17PM -0500, me at swva wrote:
On Tue, 11 Nov 2008, Jorge Arellano Cid wrote: [...]
I ended installing alpine here to check this issue.
The URL viewer is taken from .mailcap. When set properly, it works (at least here it works with Ubuntu 8.04.1, so it's not an alpine issue).
OK, good; but you're over my head. I don't find anything named .mailcap on my machine. Neither does my search function.
Since I've been running Pine for years, I have a .pinerc rather than an .alpinerc; but I don't find anything like what you say there, either.
You can create it in your home account. nano -w ~/.mailcap then put the long line there, and see what happens.
If you have something like this in your mailcap: (all in one line)
text/html; /usr/local/bin/dillo -l -f '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html
it works with dillo1.
About now, I should probably mention that I do my email different ways from different addresses. The main one is remote. It does open links that include "http://" -- in dillo *here*, not on the remote machine -- but not ones without. The same is also true when I run Alpine against the address I'm using at this moment.
Probably you use something like: ssh -X <remote_machine> it should work OK.
Something like:
text/html; /usr/local/bin/dillo -l -f -x XID '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html
I'm guessing that I should c&p that into my .pinerc somewhere, or into the interface Alpine gives me by typing M > S > C (Main menu to Setup to Configure); but I don't know where.
makes dillo1 exit, so it doesn't work. Reason: XID should be a number containing a window ID, where dillo should embed itself, not a literal string!
Now you're way to Helen Gone over my head. Sorry.
Never mind, just try the .mailcap suggestion above. -- Cheers Jorge.-
On Tue, 18 Nov 2008, Jorge Arellano Cid wrote:
On Fri, Nov 14, 2008 at 01:21:17PM -0500, me at swva wrote:
The URL viewer is taken from .mailcap. When set properly, it works (at least here it works with Ubuntu 8.04.1, so it's not an alpine issue).
OK, good; but you're over my head. I don't find anything named .mailcap on my machine. Neither does my search function.
Since I've been running Pine for years, I have a .pinerc rather than an .alpinerc; but I don't find anything like what you say there, either.
You can create it in your home account.
nano -w ~/.mailcap
then put the long line there, and see what happens.
I did, and it didn't; but I may have the long line wrong, since it's formatted into two here. I tried it (on my own machine here, not the remote one yet) both with and without a space between the backslash and "test=test" (having done c&p on the two pieces). Are there really supposed to be two spaces between the last semicolon and "nametemplate"?
If you have something like this in your mailcap: (all in one line)
text/html; /usr/local/bin/dillo -l -f '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html
it works with dillo1.
About now, I should probably mention that I do my email different ways from different addresses. The main one is remote. It does open links that include "http://" -- in dillo *here*, not on the remote machine -- but not ones without. The same is also true when I run Alpine against the address I'm using at this moment.
Probably you use something like:
ssh -X <remote_machine>
it should work OK.
I'll try that next.
Something like:
text/html; /usr/local/bin/dillo -l -f -x XID '%s'; description=HTML Text; \ test=test -n "$DISPLAY"; nametemplate=%s.html
I'm guessing that I should c&p that into my .pinerc somewhere, or into the interface Alpine gives me by typing M > S
C (Main menu to Setup to Configure); but I don't know where. [....] Now you're way to Helen Gone over my head. Sorry.
Never mind, just try the .mailcap suggestion above.
-- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
On Tue, Nov 18, 2008 at 10:32:13AM -0500, me at swva wrote:
On Tue, 18 Nov 2008, Jorge Arellano Cid wrote:
On Fri, Nov 14, 2008 at 01:21:17PM -0500, me at swva wrote:
The URL viewer is taken from .mailcap. When set properly, it works (at least here it works with Ubuntu 8.04.1, so it's not an alpine issue).
OK, good; but you're over my head. I don't find anything named .mailcap on my machine. Neither does my search function.
Since I've been running Pine for years, I have a .pinerc rather than an .alpinerc; but I don't find anything like what you say there, either.
You can create it in your home account.
nano -w ~/.mailcap
then put the long line there, and see what happens.
I did, and it didn't; but I may have the long line wrong, since it's formatted into two here. I tried it (on my own machine here, not the remote one yet) both with and without a space between the backslash and "test=test" (having done c&p on the two pieces). Are there really supposed to be two spaces between the last semicolon and "nametemplate"?
The backslash doesn't go in the line. It's a convention to mark a single line when split in two. The .mailcap should go in the same machine where alpine runs. -- Cheers Jorge.-
On Sat, Nov 08, 2008 at 04:40:01PM -0500, me at swva wrote:
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo ^^^^^^^^^^^^^^^^ Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]#
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6.
For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
If you enter "google.com" in the location bar and hit return it doesn't go to google?
It does indeed. I'm putting this badly.
I run Alpine 2.0; it is set to launch the default browser, which is dillo -- and URLs in emails are what I use a default browser for.
Does this mean something in my Alpine settings (and my Pine 4.64 settings, which it took over) is wrong? My Fedora default browser setting is simply "dillo %s"; my Alpine setting is something I'll have to dig for, as it's buried way deep.
I don't know what Alpine exactly does, but if I do dillo google.com on the command line, it works fine with both dillo 2.0 and 0.8.6.
On Sun, 9 Nov 2008 09:38:11 +0100 Johannes Hofmann <Johannes.Hofmann@gmx.de> wrote:
On Sat, Nov 08, 2008 at 04:40:01PM -0500, me at swva wrote:
I think I'm being unclear, in two ways.
Just to check, I did this as root :
[root@Hbsk2 btth]# rpm -q dillo dillo-0.8.6-7.fc9.i386 [root@Hbsk2 btth]# yum update dillo ^^^^^^^^^^^^^^^^ Loaded plugins: refresh-packagekit updates-newkey | 2.3 kB 00:00 updates | 2.6 kB 00:00 fedora | 2.4 kB 00:00 Setting up Update Process No Packages marked for Update ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [root@Hbsk2 btth]#
On Sat, 8 Nov 2008, Johannes Hofmann wrote:
dillo-0.8.6 is no longer supported and you should consider to upgrade to dillo-2.0. But nevertheless for me it also works with dillo-0.8.6.
For those who run other OSs, what the emphasized lines mean is the 0.8.6 is what Fedora has, period. (I run F9, the latest release.) Any idea why it's so far behind?? I didn't realize 1.0 had become official, let alone 2.0
If you enter "google.com" in the location bar and hit return it doesn't go to google?
It does indeed. I'm putting this badly.
I run Alpine 2.0; it is set to launch the default browser, which is dillo -- and URLs in emails are what I use a default browser for.
Does this mean something in my Alpine settings (and my Pine 4.64 settings, which it took over) is wrong? My Fedora default browser setting is simply "dillo %s"; my Alpine setting is something I'll have to dig for, as it's buried way deep.
I don't know what Alpine exactly does, but if I do dillo google.com on the command line, it works fine with both dillo 2.0 and 0.8.6.
The interesting question here is which 0.8.6? the official one or the inofficial dillo-i18n one? At least debian does not ship the official one. If that's about the dillo-i18n stuff (and not reproducable with official dillo), then the problem should go to the corresponding team. Greetings Andreas Kemnade
On Sun, 9 Nov 2008, Andreas Kemnade wrote:
The interesting question here is which 0.8.6? the official one or the inofficial dillo-i18n one? At least debian does not ship the official one. If that's about the dillo-i18n stuff (and not reproducable with official dillo), then the problem should go to the corresponding team.
Definitely the official. Fedora offers both, and I always choose against the one with the funny name -- one more topic that life is too short to learn all about. -- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
On Sun, 9 Nov 2008, Johannes Hofmann wrote:
I run Alpine 2.0; it is set to launch the default browser, which is dillo -- and URLs in emails are what I use a default browser for.
Does this mean something in my Alpine settings (and my Pine 4.64 settings, which it took over) is wrong? My Fedora default browser setting is simply "dillo %s"; my Alpine setting is something I'll have to dig for, as it's buried way deep.
I don't know what Alpine exactly does, but if I do dillo google.com on the command line, it works fine with both dillo 2.0 and 0.8.6.
Yes, that looked normal; here, fwiw, are the messages : [btth@Hbsk2 ~]$ dillo google.com Gtk-WARNING **: Failed to load module "libgnomebreakpad.so": libgnomebreakpad.so: cannot open shared object file: No such file or directory Nav_open_url: Url=>about:splash< Nav_open_url: Url=>http://google.com<; Type check: [Srv: text/html Det: text/html] Type check: [Srv: text/html; charset=UTF-8 Det: text/html] Nav_open_url: Url=>http://www.google.com/<; Type check: [Srv: text/html; charset=ISO-8859-1 Det: text/html] Type check: [Srv: image/gif Det: image/gif] Dillo: normal exit! [btth@Hbsk2 ~]$ -- Beartooth Oldfart, Double Retiree, Neo-Redneck, Linux Convert Remember, I have precious little idea what I am talking about.
participants (6)
-
akemnade＠tzi.de -
Beartooth＠swva.net -
corvid＠lavabit.com -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de -
newman.x＠gmail.com