"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
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
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
to view source and edit web forms from Firefox.
I used this setup:
Now I went and changed the Parametes value from
-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
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 :-)
XEmacs-Beta mailing list