RE: [Bug: 21.4.20] Network Drives
17 years, 7 months
Steve Higham
Vin, Stephen,
I'm sorry if I've missed something here, but I cannot think of any benefit
from trying to identify whether a file is executable under windows. Surely
the sensible approach it to try and execute it if requested, and report any
resulting failures.
I appreciate that the Unix approach of having an "executable attribute" has
benefits. Furthermore programs like xemacs should obviously respect this
attribute. However windows does not have this attribute. The OS shell and
all other systems, assume that all files are executable.
I can see no end of problems with this proposed function. Where the function
successfully identifies an executable file there will be no benefit. Where
the function fails to recognise a file as executable, the user will
presumably be told that his / her file is not marked as executable. This
will presumably cause loads of grief and no benefit.
Cheers,
Steve
-----Original Message-----
From: ethersoft(a)gmail.com [mailto:ethersoft＠gmail.com] On Behalf Of Vin
Shelton
Sent: 29 April 2007 13:12
To: Stephen J. Turnbull
Cc: Steve Higham; Benson Margulies; xemacs-beta(a)xemacs.org
Subject: Re: [Bug: 21.4.20] Network Drives
On 4/29/07, Stephen J. Turnbull <stephen(a)xemacs.org> wrote:
> Steve Higham writes:
>
> > My machine contains several perl scripts (*.pl) which are certainly
> > executable. Can the "executable extension list" be modified as a
standard
> > lisp variable?
>
> No, that's precisely why I consider it bogus, even though I haven't
> used Windows in years. The list is implicit in a series of if ... else
> if ... clauses in the function.
>
> On the other hand, since I haven't been using Windows, I'm unsure
> whether there's a way to register an extension as executable, and how
> XEmacs could determine that at runtime. So I need somebody who knows
> about that kind of thing to look at it.
I looked at the function; you're right - it's totally bogus. There is
a registry key which defines file associations and we could
potentially use that. I'll investigate a bit further.
- 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
Scrollbar Left Side
17 years, 7 months
David Raleigh Arnold
It should be obvious that it is better to have the vertical scrollbar
on the left side, because there is more text on the left side than
the right and because it is more common to want to access the beginning
of a line than the end. Bill Gates puts scrollbars on the right so that
the window will seem more like the page of a written book. This makes
no sense, but it's done that way so that windows users won't be afraid.
That's fine. Why can't I persuade xemacs to put the vertical scrollbar
on the left side, where I want it? I can't find any option, or
documentation for one, anywhere on the xemacs web site.
There is a way with emacs, but it's not in their menus either. daveA
--
Free download of technical exercises worth a lifetime of practice:
http://www.openguitar.com/dynamic.html :::: You can play the cards
you're dealt, or improve your hand with DGT. Very easy guitar
music, solos, duets, exercises, etc. draTrapVISIT(a)openguitar.com
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
[RFC] whitespace.el
17 years, 7 months
Didier Verna
Hello,
I have some extensions to whitespace.el that I'd like to commit, but I
would like to know the status wrt GNU Emacs:
- No news from the apparent maintainer: Rajesh Vaidheeswarran <rv(a)gnu.org>
- Last incorporation in packages seems to be 2 years old:
$Id: whitespace.el,v 1.3 2005/03/25 17:09:08 aidan Exp $
- But it says: Synched up with: FSF 21.3.
- Advertised URL is inoperative: http://www.dsmit.com/lisp/
So, should I just commit my changes, propose them to the GNU Emacs team,
or what ?
--
Read the Jazz Blog !! http://jazzblog.didierverna.com
Didier Verna, didier(a)lrde.epita.fr, http://www.lrde.epita.fr/~didier
EPITA / LRDE, 14-16 rue Voltaire Tel.+33 (1) 44 08 01 85
94276 Le Kremlin-Bicêtre, France Fax.+33 (1) 53 14 59 22 didier(a)xemacs.org
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Scrollbar Left Side -- SOLVED
17 years, 7 months
David Raleigh Arnold
Thanks for your help. I don't know why my rant was responded
to privately but maybe the copies for the list are in the wind
someplace. Putting this in .xemacs/init.el put the scrollbars
on the left:
(eval-expression (set-specifier scrollbar-on-left-p t))
daveA
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
XEmacs Packages have been pre-released (2007-04-30-18)
17 years, 7 months
Norbert Koch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hey there everyone.
I have just added the following packages to the 'Pre-Releases'
directory:
New Packages in Pre-Release:
===========================
text-modes-1.93-pkg.tar.gz upstream version: none
Previously Announced Packages Still in Pre-Release:
==================================================
Detailed Changes:
================
- ------- ChangeLog Entries from xemacs-packages/text-modes/ChangeLog -------
2007-04-30 Norbert Koch <viteno(a)xemacs.org>
* Makefile (VERSION): XEmacs package 1.93 released.
2007-04-30 Didier Verna <didier(a)xemacs.org>
* whitespace.el: Doc update.
* whitespace.el (whitespace-version): Increase to 2.3.
* whitespace.el (cl): Require it.
* whitespace.el (whitespace-checks-custom-type): New.
* whitespace.el (whitespace-modes): Use it.
* whitespace.el (whitespace-files): New user option.
* whitespace.el (whitespace-check-whitespace-mode): Handle it.
Installing These:
================
Manually:
- --------
1) Download the packages that you want to install from:
/ftp.xemacs.org:/pub/xemacs/beta/experimental/packages/
2) Unpack them to: [1]
/usr/local/lib/xemacs/xemacs-packages/
3) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.[245].x):
- ----------------------------------------------
1) Tools -> Packages -> Add Download Site -> Pre-Releases
2) Tools -> Packages -> List and Install
3) Select the packages you wish to install (there are brief
instructions at the bottom of the packages buffer).
4) Packages -> Install/Remove Selected
5) Re-start XEmacs.
Using XEmacs Package Tools (XEmacs 21.1.14):
- -------------------------------------------
1) Options -> Manage Packages -> Add Download Site -> Pre-Releases
2) Options -> Manage Packages -> List and Install
3 - 5) As per XEmacs 21.[245].x.
norbert - XEmacs Package Release Manager.
Footnotes:
[1] Note: Mule packages should be installed into:
/usr/local/lib/xemacs/mule-packages/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGNiT/gu3ywdHdhM0RAuULAJ9mcNnJD2Z9TitL2kxhBMKe3M1iGwCgyEUq
nTtyea7OLpomVNP4vN6pyQQ=
=X64r
-----END PGP SIGNATURE-----
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
RE: [Bug: 21.4.20] Network Drives
17 years, 7 months
Stephen J. Turnbull
Thanks for diagnosing and testing!
Steve Higham writes:
> /* All files are eXecutable under WIN32. Therefore we simply test for the
> existence of the file. I'm not sure what should happen under Cygwin */
Cygwin will need its own workarounds for this; I don't think it's
worth worrying about it now, as we may need to require a recent
version of Cygwin for Vista in any case.
> #ifndef X_OK
> # ifdef WIN32_NATIVE
> # define X_OK 0
> # else
> # define X_OK 1
> # endif
> #endif
I don't think this is appropriate. There are only a small number of
uses of X_OK, including at least one platform-independent function
that returns it. You'd need to trace such returned values to be sure
they weren't used outside of Windows-specific calls, and of course you
couldn't be sure they wouldn't be in the future.
What 21.5 does in mswindows_access() in nt.c is to check if (mode &
X_OK) is nonzero, and if so calls a function
mswindows_is_executable(). I think this is the preferred idiom.
BTW, mswindows_is_executable() itself looks kinda problematic: it
checks for the extension .bat, .cmd, .com, or .exe, and decides the
file is executable iff it's one of them. (Not a problem in 21.4,
since that function doesn't exist in 21.4.)
> If you're comfortable with this change, could you check it into the
> codebase. I haven't updated the xemacs source code before and would
> rather not start now.
Note that all commits to 21.4 must be approved by Vin Shelton. Please
don't commit to the stable branch without his explicit approval.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: [RFC] whitespace.el
17 years, 7 months
Skip Montanaro
Stephen> skip(a)pobox.com writes:
>> I think the best place for it would be as a write-file-hook though I
>> worry about it not being aware of Python's triple-quoted strings
>> which can extend over multiple lines and which might presumably
>> contain legitimate trailing whitespace.
Stephen> I note that Tim Peters thinks that (as with MIME quoted
Stephen> printable) the last character of trailing whitespace should be
Stephen> written \x20 or \x09. It would be rude to disagree with sweet
Stephen> ol' Uncle Timmy.<wink>
Yes, and I agree, but not everyone uses that scheme now. I think it would
be rude if python-mode suddenly started deleting whitespace where it didn't
before. (We could obviously make this step conditional.)
Skip
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
Re: New 21.5 setup kit
17 years, 7 months
Vin Shelton
I had written:
> I've copied a new setup kit to:
> http://ftp.xemacs.org/pub/xemacs/windows/testing/XEmacs_Setup_21.5-b27-20...
>
> I built this kit on my C: drive, so I don't think it will contain any
> references to the e: drive. Please let me know how this works on your
> system.
On 4/23/07, Sean Boisen wrote:
>
> Looks like a winner. I undid my drive letter change and logged out, and
> starting this up didn't complain as the previous version did.
That's good news. I'll move my build environment over to my C: drive.
Although not all Windows installations use the C: drive, the vast
majority do, so overall, it's probably a winner.
> Should I send other bug reports to xemacs-beta, or to you? I've found a
> few other nits (like kill-buffer for a buffer running a Python shell
> produces "Invalid operation: Cannot send signal to process, #<process
> "Python" pid 736 state:run>", and kills the process, but doesn't kill
> the buffer).
Please send your problem reports to xemacs-beta - many eyes make bugs shallow.
> Thanks again for your help,
You're welcome and thank you, too!
- 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
