TeXworks and hunspell

TeXworks and hunspell

[Ken Brown]

To complete the process of modernizing Cygwin's TeX programs, I am 
thinking about ITPing TeXworks.  I've built it using the .cygport file 
from Ports.  I have two questions for Yaakov.

1. The manual (which is supposed to be available from the Help menu) 
doesn't get installed.  Having never before built a package that uses 
qmake, I'm not sure how to make this happen.  I see in TeXworks.pro the 
lines

	manual.files = manual/*
	manual.path = $$TW_HELPPATH

which I would think should take care of this, but it doesn't.  Do you 
know how to fix this?

2. TeXworks requires hunspell.  Are you interested in moving this into 
the distro?  I suppose I could ITP that also, but I don't really know 
anything about it, so I'm not the best person to be its maintainer. 
BTW, I built hunspell using your .cygport, and cygport warned me that 
the following three scripts didn't get packaged:

   usr/bin/affixcompress
   usr/bin/makealias
   usr/bin/wordforms

Was this deliberate or just an oversight?

Ken

Re: TeXworks and hunspell

[Ken Brown]

On 3/24/2012 11:15 AM, Ken Brown wrote:
> To complete the process of modernizing Cygwin's TeX programs, I am
> thinking about ITPing TeXworks. I've built it using the .cygport file
> from Ports. I have two questions for Yaakov.
>
> 1. The manual (which is supposed to be available from the Help menu)
> doesn't get installed. Having never before built a package that uses
> qmake, I'm not sure how to make this happen. I see in TeXworks.pro the
> lines
>
> manual.files = manual/*
> manual.path = $$TW_HELPPATH
>
> which I would think should take care of this, but it doesn't. Do you
> know how to fix this?

This must have something to do with cygport, because the manual does get 
installed if I build outside of cygport via qmake-qt4, make, make 
install.  But I have more important things to worry about first.  I 
started trying to use texworks and found that I can reliably make the X 
server crash.  Since texworks isn't in the distro yet, I'm not sure 
where to take this.  Should I send the details to the Ports list?

Ken

Re: TeXworks and hunspell

[Ken Brown]

On 3/24/2012 2:39 PM, Ken Brown wrote:
> On 3/24/2012 11:15 AM, Ken Brown wrote:
>> To complete the process of modernizing Cygwin's TeX programs, I am
>> thinking about ITPing TeXworks. I've built it using the .cygport file
>> from Ports. I have two questions for Yaakov.
>>
>> 1. The manual (which is supposed to be available from the Help menu)
>> doesn't get installed. Having never before built a package that uses
>> qmake, I'm not sure how to make this happen. I see in TeXworks.pro the
>> lines
>>
>> manual.files = manual/*
>> manual.path = $$TW_HELPPATH
>>
>> which I would think should take care of this, but it doesn't. Do you
>> know how to fix this?
>
> This must have something to do with cygport, because the manual does get
> installed if I build outside of cygport via qmake-qt4, make, make
> install.

Sorry for the noise.  I just looked more closely at the .cygport file 
and saw that it doesn't use make install.  So I guess I just have to 
manually copy manual/* into ${D}/usr/share/texworks-help.

Another question is how to make the commands under the Help menu that 
want to open a URL work.  Or would this require a KDE desktop?

Ken

Re: TeXworks and hunspell

[Yaakov (Cygwin/X)]

On 2012-03-24 10:15, Ken Brown wrote:
> 1. The manual (which is supposed to be available from the Help menu)
> doesn't get installed.

Fixed in Ports git.

> 2. TeXworks requires hunspell. Are you interested in moving this into
> the distro? I suppose I could ITP that also, but I don't really know
> anything about it, so I'm not the best person to be its maintainer. BTW,
> I built hunspell using your .cygport, and cygport warned me that the
> following three scripts didn't get packaged:
>
> usr/bin/affixcompress
> usr/bin/makealias
> usr/bin/wordforms
>
> Was this deliberate or just an oversight?

Deliberate; they shouldn't be needed by anything.

> Another question is how to make the commands under the Help menu that
> want to open a URL work.  Or would this require a KDE desktop?

No, but it does require a browser; does installing xdg-utils from Ports 
help?


Yaakov

Re: TeXworks and hunspell

[Ken Brown]

On 3/28/2012 5:26 AM, Yaakov (Cygwin/X) wrote:
> On 2012-03-24 10:15, Ken Brown wrote:
>> 1. The manual (which is supposed to be available from the Help menu)
>> doesn't get installed.
>
> Fixed in Ports git.

Thanks!  I never cease to be amazed at the wonders of cygport.

>> Another question is how to make the commands under the Help menu that
>> want to open a URL work. Or would this require a KDE desktop?
>
> No, but it does require a browser; does installing xdg-utils from Ports
> help?

Yes, it does help.  I haven't completely figured out how to configure my 
system so that xdg-open will do everything I want, but I've figured out 
enough to know that it's do-able.

On the subject of xdg-utils, you originally made it a dependency of 
asymptote (which would have required moving it to the distro).  What 
made you change your mind?  Are there problems with xdg-utils that are 
keeping you from moving it to the distro?  I'd be glad to help in any 
way I can.

Ken

Re: TeXworks and hunspell

[Ken Brown]

On 3/29/2012 4:10 PM, Ken Brown wrote:
> On 3/28/2012 5:26 AM, Yaakov (Cygwin/X) wrote:
>> On 2012-03-24 10:15, Ken Brown wrote:
>>> Another question is how to make the commands under the Help menu that
>>> want to open a URL work. Or would this require a KDE desktop?
>>
>> No, but it does require a browser; does installing xdg-utils from Ports
>> help?
>
> Yes, it does help. I haven't completely figured out how to configure my
> system so that xdg-open will do everything I want, but I've figured out
> enough to know that it's do-able.

OK, I've got all the Help menu commands working except the one that's 
supposed to send mail, but that seems to be a cygstart problem.  I've 
just sent a question about this to the cygwin list.

In order to make the command to open the manual work, I created a 
/usr/share/applications/defaults.list file with the following line:

   application/xml=cygstart.desktop

Setting BROWSER=cygstart doesn't help here, because xdg-open receives a 
`file://' URL, which cygstart doesn't understand.

Ken

cygstart URI handling (was: TeXworks and hunspell)

[Yaakov (Cygwin/X)]

[-- Attachment #1: Type: text/plain, Size: 481 bytes --]

On 2012-03-30 09:12, Ken Brown wrote:
> In order to make the command to open the manual work, I created a
> /usr/share/applications/defaults.list file with the following line:
>
> application/xml=cygstart.desktop

Probably you should be using ~/.local/share/applications/mimeapps.list 
instead, but you've got the idea.

> Setting BROWSER=cygstart doesn't help here, because xdg-open receives a
> `file://' URL, which cygstart doesn't understand.

How about the attached?


Yaakov

[-- Attachment #2: cygstart-file-mailto.patch --]
[-- Type: application/x-itunes-itlp, Size: 909 bytes --]

Re: cygstart URI handling

[Yaakov (Cygwin/X)]

[-- Attachment #1: Type: text/plain, Size: 241 bytes --]

On 2012-03-30 13:29, Yaakov (Cygwin/X) wrote:
>> Setting BROWSER=cygstart doesn't help here, because xdg-open receives a
>> `file://' URL, which cygstart doesn't understand.
>
> How about the attached?

Sorry, let's try that again.


Yaakov

[-- Attachment #2: cygstart-file-mailto.patch --]
[-- Type: application/x-itunes-itlp, Size: 909 bytes --]

Re: cygstart URI handling

[Ken Brown]

On 3/30/2012 2:33 PM, Yaakov (Cygwin/X) wrote:
> On 2012-03-30 13:29, Yaakov (Cygwin/X) wrote:
>>> Setting BROWSER=cygstart doesn't help here, because xdg-open receives a
>>> `file://' URL, which cygstart doesn't understand.
>>
>> How about the attached?

Works for me.

Ken

Re: cygstart URI handling

[Ken Brown]

On 3/30/2012 2:29 PM, Yaakov (Cygwin/X) wrote:
> On 2012-03-30 09:12, Ken Brown wrote:
>> In order to make the command to open the manual work, I created a
>> /usr/share/applications/defaults.list file with the following line:
>>
>> application/xml=cygstart.desktop
>
> Probably you should be using ~/.local/share/applications/mimeapps.list
> instead, but you've got the idea.

I used defaults.list rather than mimeapps.list because that's what I saw 
in xdg-mime.  The latter uses mimeapps.list only for KDE 4.

By the way, I initially tried to set the default for application/xml by 
using xdg-mime instead of directly creating a defaults.list file.  But 
that doesn't work, because xdg-mime uses a grep command that fails if 
defaults.list doesn't exist.  That strikes me as a bug.  I would expect 
xdg-mime to create the file if it doesn't exist.

Ken

Re: cygstart URI handling

[Ken Brown]

[-- Attachment #1: Type: text/plain, Size: 398 bytes --]

On 3/30/2012 4:08 PM, Ken Brown wrote:
> By the way, I initially tried to set the default for application/xml by
> using xdg-mime instead of directly creating a defaults.list file. But
> that doesn't work, because xdg-mime uses a grep command that fails if
> defaults.list doesn't exist. That strikes me as a bug. I would expect
> xdg-mime to create the file if it doesn't exist.

Patch attached.


[-- Attachment #2: xdg_mime_create_defaults_list.patch --]
[-- Type: text/plain, Size: 749 bytes --]

--- origsrc/xdg-utils-1.1.0-rc1/scripts/xdg-mime	2011-01-01 05:03:14.000000000 -0500
+++ src/xdg-utils-1.1.0-rc1/scripts/xdg-mime	2012-03-31 13:19:46.769441000 -0400
@@ -658,7 +658,10 @@ make_default_generic()
     # Add $2=$1 to XDG_DATA_HOME/applications/defaults.list
     xdg_user_dir="$XDG_DATA_HOME"
     [ -n "$xdg_user_dir" ] || xdg_user_dir="$HOME/.local/share"
-    default_file="$xdg_user_dir/applications/defaults.list"
+    default_dir="$xdg_user_dir/applications"
+    default_file="$default_dir/defaults.list"
+    mkdir -p $default_dir
+    [ -f $default_file ] || touch $default_file
     DEBUG 2 "make_default_generic $1 $2"
     DEBUG 1 "Updating $default_file"
     grep -v "$2=" $default_file > ${default_file}.new 2> /dev/null