10:22 p.m.
Dear XEmacs friends,
I plan on releasing XEmacs-21.4.21 this weekend. At this point, I
don't think I will be adding any major new patches to the source tree,
but I will be reviewing my entire queue of unapplied patches, so if
there's a patch *you* want to lobby for, please feel free to drop me a
line.
I recently made a new gnuclient_setup window kit. This version has a
few improvements:
1. The installation process is a little bit cleaner, with fewer windows.
2. The uninstall process tries harder not to leave behind any traces
of the installed kit.
3. The modifications to site-start.el attempt to be a little more
careful not to disrupt an existing XEmacs installation.
4. The kit now allows the user to add gnuclient to the SendTo menu.
Regards,
Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
10:20 a.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website] (was: Announcements)
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
Dear XEmacs friends,
I plan on releasing XEmacs-21.4.21 this weekend. At this point, I
don't think I will be adding any major new patches to the source tree,
but I will be reviewing my entire queue of unapplied patches, so if
there's a patch *you* want to lobby for, please feel free to drop me a
line.
I recently made a new gnuclient_setup window kit. This version has a
Thanks Vin, it works great for me!
I would like to make it easy from the XEmacs website to fnd and
install your new gnuclient_setup window kit.
I think about putting in a
XEmacs Community News
item for this.
Furthermore I think that download links for gnuclient_setup.exe should
go into
http://www.xemacs.org/Download/win32/
Vin, do you want to copy/mv
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
over to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
I think we never announced the beta binary kits for Windows.
Should
http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
also be moved over, or should I link to the testing location from the website?
Perhaps it's time to remove the information about the outdated
Netinstall
and
InstallShield
kits from that page, and remove the kits from the ftp sites too?
Any objections?
----
I am noting two regressions using gnuclientw vs. winclient (which I used
before):
When I sent a file to XEmacs for editing via winclient before, it
would always raise the XEmacs frame.
Now, when I do this, the file gets loaded in the running XEmacs OK,
but the frame does not get raised.
e.g. C-u in firefox (Firefox->View->Page Source)
The other regression is that no new XEmacs is started when none is running.
Instead I get the error message:
---------------------------
c:\\Program Files\\XEmacs\\XEmacs-21.5-b28\\i586-pc-win32\\gnuclientw.exe
---------------------------
Could not start runemacs
---------------------------
OK
---------------------------
Adrian
few improvements:
1. The installation process is a little bit cleaner, with fewer windows.
2. The uninstall process tries harder not to leave behind any traces
of the installed kit.
3. The modifications to site-start.el attempt to be a little more
careful not to disrupt an existing XEmacs installation.
4. The kit now allows the user to add gnuclient to the SendTo menu.
Regards,
Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:14 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website] (was: Announcements)
On 10/6/07, Adrian Aichner wrote:
Vin Shelton writes:
> I recently made a new gnuclient_setup window kit.
Thanks Vin, it works great for me!
I would like to make it easy from the XEmacs website to find and
install your new gnuclient_setup window kit.
I think about putting in a
XEmacs Community News
item for this.
Furthermore I think that download links for gnuclient_setup.exe should
go into http://www.xemacs.org/Download/win32/
Yes, I think it works well enough that we can move it out of the
testing directory.
Vin, do you want to copy/mv
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
over to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
Sounds like you think we should "go public". I agree.
I had been thinking of waiting for the -b28 release. (Oops - I guess
I missed that triggering event :-) .) I don't see any particular
reason to wait for the impending -b29 release. I'll copy the file
over.
I think we never announced the beta binary kits for Windows.
Should
http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
also be moved over, or should I link to the testing location from the website?
Well, I think you should link to the new location in the InnoSetup
directory and leave the windows/testing directory for the adventurous.
Do you mind making the changes to the website?
Perhaps it's time to remove the information about the outdated
Netinstall
and
InstallShield
kits from that page, and remove the kits from the ftp sites too?
Any objections?
Well, they're pretty old (mostly circa 1999 - 2001). I don't think
keeping them around does the project any good.
I am noting two regressions using gnuclientw vs. winclient (which I
used
before):
When I sent a file to XEmacs for editing via winclient before, it
would always raise the XEmacs frame.
Now, when I do this, the file gets loaded in the running XEmacs OK,
but the frame does not get raised.
e.g. C-u in firefox (Firefox->View->Page Source)
Yes, I see this also. gnuclientw is supposed to handle this.
The other regression is that no new XEmacs is started when none is running.
Instead I get the error message:
---------------------------
c:\\Program Files\\XEmacs\\XEmacs-21.5-b28\\i586-pc-win32\\gnuclientw.exe
---------------------------
Could not start runemacs
---------------------------
OK
---------------------------
I'll investigate and see if I creating a runemacs.cmd file in the
gnuclientw directory suffices.
(BTW, I had to boost TRANSACTION_TIMEOUT to make winclient wait long
enough to start up XEmacs.)
Thanks for the testing and the feedback, Adrian!
- Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5:19 p.m.
On Fri, 05 Oct 2007 17:22:19 -0400, Vin Shelton wrote:
Dear XEmacs friends,
I plan on releasing XEmacs-21.4.21 this weekend. At this point, I don't
think I will be adding any major new patches to the source tree, but I
will be reviewing my entire queue of unapplied patches, so if there's a
patch *you* want to lobby for, please feel free to drop me a line.
Gentoo currently applies a number of patches for XEmacs 21.4.20, but most
should already be applied (linuxplay sound fixes, font-lock-warning-face
fix and font-lock-keywords patch).
Remaining are patches to fix a bit of documentation (already fixed in
21.5) and fixes to let configure figure out newer versions of Berkeley
DB. I think I already posted these to the mailing list earlier, but they
can also be found in our CVS: http://sources.gentoo.org/viewcvs.py/gentoo-
x86/app-editors/xemacs/
Kind regards,
Hans
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:29 a.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
On 10/6/07, Adrian Aichner wrote:
> Vin Shelton writes:
> > I recently made a new gnuclient_setup window kit.
>
> Thanks Vin, it works great for me!
>
> I would like to make it easy from the XEmacs website to find and
> install your new gnuclient_setup window kit.
>
> I think about putting in a
> XEmacs Community News
> item for this.
>
> Furthermore I think that download links for gnuclient_setup.exe should
> go into http://www.xemacs.org/Download/win32/
Yes, I think it works well enough that we can move it out of the
testing directory.
Great!
> Vin, do you want to copy/mv
> http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
> over to
> http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
Sounds like you think we should "go public". I agree.
Good.
I had been thinking of waiting for the -b28 release. (Oops - I guess
I missed that triggering event :-) .) I don't see any particular
reason to wait for the impending -b29 release. I'll copy the file
over.
Thanks!
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
Here's what I'd suggest:
Remove contents of
http://ftp.xemacs.org/xemacs/binaries/win32/installshield/
http://ftp.xemacs.org/xemacs/binaries/win32/netinstall/
nhttp://ftp.xemacs.org/xemacs/windows/ReadMe-21.4.20
http://ftp.xemacs.org/xemacs/windows/XEmacs_Setup_21.4.20.exe
Copy (moving would require perfect timing relative to website update)
http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
Copy
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21.5-b...
Q: Is this really 21.5-b28 or CVS as of 2007-09-26?
Remove all content of
http://ftp.xemacs.org/xemacs/windows/testing
once the website changes have been committed.
Could you do that please?
> I think we never announced the beta binary kits for Windows.
>
> Should
> http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
> also be moved over, or should I link to the testing location from the website?
Well, I think you should link to the new location in the InnoSetup
directory and leave the windows/testing directory for the adventurous.
Do you mind making the changes to the website?
OK, I've started to make the required updates to
xemacs-builds\adrian\website\package-get-2-download-sites.el
and
xemacsweb\Download\win32\index.content
That doesn't mean I wouldn't love to see others to actively work on
the XEmacs website.
Anybody is welcome!
We'll need to coordinate the copying of files in the ftp site and the
commit of my website update.
Please let me know when the files are in place in the new locations.
>
> Perhaps it's time to remove the information about the outdated
> Netinstall
> and
> InstallShield
> kits from that page, and remove the kits from the ftp sites too?
>
> Any objections?
Well, they're pretty old (mostly circa 1999 - 2001). I don't think
keeping them around does the project any good.
Yep, I have worked that into my suggestions above.
> I am noting two regressions using gnuclientw vs. winclient (which I used
> before):
>
> When I sent a file to XEmacs for editing via winclient before, it
> would always raise the XEmacs frame.
>
> Now, when I do this, the file gets loaded in the running XEmacs OK,
> but the frame does not get raised.
>
> e.g. C-u in firefox (Firefox->View->Page Source)
Yes, I see this also. gnuclientw is supposed to handle this.
I thought gnuclientw only avoids the DOS prompt window to pop up.
Should it also raise the XEmacs frame?
>
> The other regression is that no new XEmacs is started when none is running.
>
> Instead I get the error message:
>
> ---------------------------
> c:\\Program Files\\XEmacs\\XEmacs-21.5-b28\\i586-pc-win32\\gnuclientw.exe
> ---------------------------
> Could not start runemacs
> ---------------------------
> OK
> ---------------------------
I'll investigate and see if I creating a runemacs.cmd file in the
gnuclientw directory suffices.
That would be great!
(BTW, I had to boost TRANSACTION_TIMEOUT to make winclient wait long
enough to start up XEmacs.)
Thanks for the testing and the feedback, Adrian!
Thanks for making gnuclient trivial to install for everybody
on Windows!
Adrian
- Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6:09 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
On 10/7/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
> On 10/6/07, Adrian Aichner wrote:
>> Vin Shelton writes:
>> > I recently made a new gnuclient_setup window kit.
>>
>> Thanks Vin, it works great for me!
I have since created an even newer kit that fixes (at least for me)
the 2 remaining problems you had identified:
1) The gnuclient SendTo entry now pops the XEmacs window to the foreground.
2) The gnuclient SendTo entry now creates an XEmacs executable if
one didn't already exist.
Here's what I'd suggest:
Remove contents of
http://ftp.xemacs.org/xemacs/binaries/win32/installshield/
http://ftp.xemacs.org/xemacs/binaries/win32/netinstall/
Done
nhttp://ftp.xemacs.org/xemacs/windows/ReadMe-21.4.20
http://ftp.xemacs.org/xemacs/windows/XEmacs_Setup_21.4.20.exe
I removed those symlinks, as well as
http://ftp.xemacs.org/xemacs/windows/win32
it pointed to the netinstall directory.
I also mv'ed
http://ftp.xemacs.org/xemacs/windows/setup*
to
http://ftp.xemacs.org/xemacs/windows/old/
This leaves
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup
as the only apparent Windows installer kits. Do they need to be
accessible from a more obvious place, like:
http://ftp.xemacs.org/xemacs/windows ?
Copy (moving would require perfect timing relative to website update)
http://ftp.xemacs.org/xemacs/windows/testing/gnuclient_setup.exe
to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
I actually copied the newest version of gnuclient_setup.exe into
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/
Copy
http://ftp.xemacs.org/xemacs/windows/testing/XEmacs_Setup_21.5-b28-2007-0...
to
http://ftp.xemacs.org/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21.5-b...
Done.
Q: Is this really 21.5-b28 or CVS as of 2007-09-26?
This is a copy of XEmacs 21.5 built from CVS on 2007-09-26.
Remove all content of
http://ftp.xemacs.org/xemacs/windows/testing
once the website changes have been committed.
Give me the word and I'll empty out
http://ftp.xemacs.org/xemacs/windows/testing
I will continue to populate it with new setup kits, though as the
packages get updated and as I build new setup kits against the 21.4
and 21.5 sources.
OK, I've started to make the required updates to
xemacs-builds\adrian\website\package-get-2-download-sites.el
and
xemacsweb\Download\win32\index.content
That doesn't mean I wouldn't love to see others to actively work on
the XEmacs website.
Anybody is welcome!
We'll need to coordinate the copying of files in the ftp site and the
commit of my website update.
The inquisitive and observant XEmacs hacker will notice that I have
copied a 21.4.21 setup kit into:
http://ftp.xemacs.org/pub/xemacs/binaries/win32/InnoSetup/XEmacs_Setup_21...
21.4.21 has been tagged in CVS and I will be making a release
announcement this weekend.
- Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:26 a.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
On 10/7/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
> "Vin Shelton" <acs(a)alumni.princeton.edu> writes:
>
> > On 10/6/07, Adrian Aichner wrote:
> >> Vin Shelton writes:
> >> > I recently made a new gnuclient_setup window kit.
> >>
> >> Thanks Vin, it works great for me!
I have since created an even newer kit that fixes (at least for me)
the 2 remaining problems you had identified:
1) The gnuclient SendTo entry now pops the XEmacs window to the foreground.
This still does not work for me.
The buffer does get displayed in a window, like before, but the XEmacs
frame does not get raised (if obscured by other frames) or restored
(if minimized).
winclient does this AFAIR.
2) The gnuclient SendTo entry now creates an XEmacs executable if
one didn't already exist.
gnuclientw now starts a new XEmacs, great!
How does it choose the XEmacs executable to start, if multiple exist?
It starts 21.5-b28 for me, which is good.
I also have 21.5-b27, 21.5-b26, 21.4.19, and 21.1.14 installed under
C:\Program Files\XEmacs.
It looks like a new XEmacs so started does not have a *scratch* buffer.
Is that correct/intended?
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
1:48 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
Good morning, Adrian!
Yes, Sox won 10-3!
On 10/13/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
> On 10/7/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
>> "Vin Shelton" <acs(a)alumni.princeton.edu> writes:
> 1) The gnuclient SendTo entry now pops the XEmacs window to the foreground.
This still does not work for me.
The buffer does get displayed in a window, like before, but the XEmacs
frame does not get raised (if obscured by other frames) or restored
(if minimized).
Are you sure you're using the correct entry from the SendTo menu? The
latest kit invokes gnuclient with the -q and -F options. Can you send
me the properties of your SendTo menu entry? Here's how to find it:
1. Right click on Start and select Explore
2. Choose the SendTo folder
3. Right click on "XEmacs (via gnuclient)" and choose Properties
4. Cut and paste the target string into your reply
winclient does this AFAIR.
Yes, I think that feature is built into DDE - the recipient is
automatically brought to the foreground.
> 2) The gnuclient SendTo entry now creates an XEmacs executable if
> one didn't already exist.
gnuclientw now starts a new XEmacs, great!
How does it choose the XEmacs executable to start, if multiple exist?
It starts 21.5-b28 for me, which is good.
The setup kit adds a gnuclientw entry for the first XEmacs it finds.
When that gnuclient invokes an XEmacs, it uses the one from the
current directory. I decided that anyone sophisticated enough to have
multiple versions of XEmacs installed could change the properties of
the SendTo item.
I also have 21.5-b27, 21.5-b26, 21.4.19, and 21.1.14 installed under
C:\Program Files\XEmacs.
It looks like a new XEmacs so started does not have a *scratch* buffer.
Is that correct/intended?
I don't see that. For me, ^Xb offers *scratch* as the alternate
buffer. This is true in both 21.4 and 21.5.
Regards,
Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5:06 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
Good morning, Adrian!
Yes, Sox won 10-3!
On 10/13/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
> "Vin Shelton" <acs(a)alumni.princeton.edu> writes:
>
> > On 10/7/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
> >> "Vin Shelton" <acs(a)alumni.princeton.edu> writes:
> > 1) The gnuclient SendTo entry now pops the XEmacs window to the foreground.
>
> This still does not work for me.
>
> The buffer does get displayed in a window, like before, but the XEmacs
> frame does not get raised (if obscured by other frames) or restored
> (if minimized).
Are you sure you're using the correct entry from the SendTo menu? The
latest kit invokes gnuclient with the -q and -F options. Can you send
BTW, that setup kit Inoformation text still states:
"This kit has been tested with and is compatible with the Windows-native XEmacs setup
kits that can be found at http://ftp.xemacs.org/pub/xemacs/windows/testing."
Not a big deal, but it might be worth advertising
http://www.xemacs.org/Download/win32/#InnoSetup-Gnuclient-Download
or just
http://www.xemacs.org/Download/win32/
instead of the testing directory.
We can still put a link to the testing directory in the former page to
point people to test kits.
me the properties of your SendTo menu entry? Here's how to find
it:
1. Right click on Start and select Explore
2. Choose the SendTo folder
3. Right click on "XEmacs (via gnuclient)" and choose Properties
4. Cut and paste the target string into your reply
Oh, interesting, it's 21.4.19:
"C:\Program Files\XEmacs\XEmacs-21.4.19\i586-pc-win32\gnuclientw.exe" -q -F
Ah, I actually use
http://dafizilla.sourceforge.net/viewsourcewith/
to view source and edit web forms from Firefox.
I used this setup:
Editor path
c:\Program Files\XEmacs\XEmacs-21.5-b28\i586-pc-win32\gnuclientw.exe
Description
gnuclientw
Parameters
$f
Now I went and changed the Parametes value from
$f
to
-q -F $f
and now the XEmacs frame gets raised or restored as expeccted.
Thanks for the information, Vin!
> winclient does this AFAIR.
Yes, I think that feature is built into DDE - the recipient is
automatically brought to the foreground.
>
> > 2) The gnuclient SendTo entry now creates an XEmacs executable if
> > one didn't already exist.
>
> gnuclientw now starts a new XEmacs, great!
>
> How does it choose the XEmacs executable to start, if multiple exist?
>
> It starts 21.5-b28 for me, which is good.
The setup kit adds a gnuclientw entry for the first XEmacs it finds.
When that gnuclient invokes an XEmacs, it uses the one from the
current directory. I decided that anyone sophisticated enough to have
multiple versions of XEmacs installed could change the properties of
the SendTo item.
Yep, not a problem.
>
> I also have 21.5-b27, 21.5-b26, 21.4.19, and 21.1.14 installed under
> C:\Program Files\XEmacs.
>
> It looks like a new XEmacs so started does not have a *scratch* buffer.
>
> Is that correct/intended?
I don't see that. For me, ^Xb offers *scratch* as the alternate
buffer. This is true in both 21.4 and 21.5.
I tried again:
Ah, I do get a *scratch* buffer, BUT, it's completely empty!
Is this a sequencing issue?
I notice the file to be edited gets loaded real early, when a new
XEmacs is started. It's shows default font-lock colors.
Then my extensive customizations get loaded and the font-locking
changes.
And the way the scratch buffer gets initialized seems to be different
in some respect.
These are all minor issue, I'm quite happy with gnuclientw, and should
rather move on to test hg merging now :-)
Adrian
Regards,
Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5:10 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
"Adrian Aichner" <adrian(a)xemacs.org> writes:
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
>> It looks like a new XEmacs so started does not have a
*scratch* buffer.
>>
>> Is that correct/intended?
>
> I don't see that. For me, ^Xb offers *scratch* as the alternate
> buffer. This is true in both 21.4 and 21.5.
I tried again:
Ah, I do get a *scratch* buffer, BUT, it's completely empty!
Is this a sequencing issue?
I notice the file to be edited gets loaded real early, when a new
XEmacs is started. It's shows default font-lock colors.
Then my extensive customizations get loaded and the font-locking
changes.
And the way the scratch buffer gets initialized seems to be different
in some respect.
I guess initial-scratch-message must be initialized too late or not
get inserted for some reason.
These are all minor issue, I'm quite happy with gnuclientw, and should
rather move on to test hg merging now :-)
Adrian
>
> Regards,
> Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
8:27 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
Dear Adrian,
On 10/13/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
> Then my extensive customizations get loaded and the
font-locking
> changes.
>
> And the way the scratch buffer gets initialized seems to be different
> in some respect.
I guess initial-scratch-message must be initialized too late or not
get inserted for some reason.
Actually, there's a race condition that I have been unable to track
down. When gnuclient starts a fresh XEmacs, it currently waits 3
seconds before sending XEmacs a message because XEmacs can get
confused if the gnuclient command arrives too early on stdin from
gnuserv. I think your setup requires a longer wait.
If I knew what the actual race condition is, I would track it down and
squish it. Setting a wait timeout was the easier (if less robust)
path to take. I could:
a) do nothing
b) increase the timeout
c) make the timeout configurable via a command line parameter
d) find the real bug. I haven't had much luck with this approach.
Let me know what you think. In any case I'll release a new setup kit
replacing the reference to the testing directory - please let me know
your preference around the race condition mentioned above.
Regards,
Vin
--
The Journey by Mary Oliver
http://www.poemhunter.com/p/m/poem.asp?poet=6771&poem=30506
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
8:54 p.m.
New subject: [Adding gnuclient_setup, removing Netinstall and InstallShield from website]
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
Dear Adrian,
On 10/13/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
> > Then my extensive customizations get loaded and the font-locking
> > changes.
> >
> > And the way the scratch buffer gets initialized seems to be different
> > in some respect.
>
> I guess initial-scratch-message must be initialized too late or not
> get inserted for some reason.
Actually, there's a race condition that I have been unable to track
down. When gnuclient starts a fresh XEmacs, it currently waits 3
seconds before sending XEmacs a message because XEmacs can get
confused if the gnuclient command arrives too early on stdin from
gnuserv. I think your setup requires a longer wait.
If I knew what the actual race condition is, I would track it down and
squish it. Setting a wait timeout was the easier (if less robust)
path to take. I could:
a) do nothing
b) increase the timeout
c) make the timeout configurable via a command line parameter
d) find the real bug. I haven't had much luck with this approach.
Let me know what you think. In any case I'll release a new setup kit
replacing the reference to the testing directory - please let me know
your preference around the race condition mentioned above.
Hi Vin, I'm happy to settle for (a) for now.
I'll see if I can help shed some light on (d) as time goes by.
But tomorrow I'll climb a mountain instead!
Have a good weekend!
Adrian
Regards,
Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
3:34 p.m.
New subject: gnuclient_setup suggestion: gnuserv-start via after-init-hook (was: [Adding gnuclient_setup, removing Netinstall and InstallShield from website])
"Adrian Aichner" <adrian(a)xemacs.org> writes:
"Vin Shelton" <acs(a)alumni.princeton.edu> writes:
> Dear Adrian,
>
> On 10/13/07, Adrian Aichner <adrian(a)xemacs.org> wrote:
>
>> > Then my extensive customizations get loaded and the font-locking
>> > changes.
>> >
>> > And the way the scratch buffer gets initialized seems to be different
>> > in some respect.
>>
>> I guess initial-scratch-message must be initialized too late or not
>> get inserted for some reason.
>
> Actually, there's a race condition that I have been unable to track
> down. When gnuclient starts a fresh XEmacs, it currently waits 3
> seconds before sending XEmacs a message because XEmacs can get
> confused if the gnuclient command arrives too early on stdin from
> gnuserv. I think your setup requires a longer wait.
>
> If I knew what the actual race condition is, I would track it down and
> squish it. Setting a wait timeout was the easier (if less robust)
> path to take. I could:
> a) do nothing
> b) increase the timeout
> c) make the timeout configurable via a command line parameter
> d) find the real bug. I haven't had much luck with this approach.
>
> Let me know what you think. In any case I'll release a new setup kit
> replacing the reference to the testing directory - please let me know
> your preference around the race condition mentioned above.
Hi Vin, I'm happy to settle for (a) for now.
I'll see if I can help shed some light on (d) as time goes by.
Hi Vin, I'd suggest new option
e) Start gnuserv after newly XEmacs is fully initialized
Could you please try adding this code at the end of site-start.el
instead in the gnuclient_setup installation:
(add-hook 'after-init-hook
(lambda ()
(load "gnuserv.el" t t)
;; Make sure we start the correct gnuserv executable
(setq gnuserv-program (concat exec-directory "gnuserv.exe"))
(if (file-executable-p gnuserv-program) (gnuserv-start)))
'append)
Please note I also added a file-executable-p test.
This seems to work fine for me.
Adrian
But tomorrow I'll climb a mountain instead!
Have a good weekend!
Adrian
>
> Regards,
> Vin
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
5989
days inactive
6047
days old
12 comments
3 participants
participants (3)
-
Adrian Aichner -
Hans de Graaff -
Vin Shelton