October 2000 - XEmacs-Beta - XEmacs Mailing List Archives

stray @lockdir@ (xemacs-21.2 CVS) 24 years, 1 month

Yoshiaki Kasahara

When I do 'make install' in the top directory, '＠lockdir＠' is created in the current dir. I believe 'lockdir' had been removed from configure several months ago, but Makefile.in still contains several lockdir-related codes. ＠lockdir＠ won't substituted, so '＠lockdir＠' is created in the current directory. -- Yoshiaki Kasahara Computing and Communications Center, Kyushu University kasahara(a)nc.kyushu-u.ac.jp

2 participants
1 comments

Re: outstanding issues 24 years, 1 month

Michael Sperber

>>>>> "John" == John A Turner <turner(a)blueskystudios.com> writes: John> I'm not sure what the schedule for a 21.2 release is, but I thought I'd John> mention a couple of things that I see as outstanding issues - everything is John> as of b36, possibly slightly more recent John> they're pretty minor John> o the dired customize prob reported here remains: John> http://www.xemacs.org/list-archives/xemacs-beta/200002/msg00139.html This one whizzed by me because it was not sent to efs-bug (and doesn't have "dired" in the Subject header). If you could resubmit via M-x dired-report-bug, I'd be grateful. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

3 participants
2 comments

Re: RFC: xemacsweb - XEmacs vs. GNU Emacs 24 years, 1 month

Per Bothner

I am not on any xemacsI mailing list, but I noticed this while browsing: (See http://www.xemacs.org/list-archives/xemacs-beta/200010/msg00236.html) > awhile ago the faq had a link to something i wrote going into this > in more detail. steve removed it without consulting me, probably > because he considered it incendiary Another problem might be that there are some serious factual mistakes. At least I think so. > Although they have not stated their reasons, there are quite a > number of reasons not to sign legal papers: > 1. By doing so you essentially give up all control over your > code. You can no longer release your code under a different > license. If you want to use your code that you've contributed to the > FSF in a project of your own, and that project is not released under > the GPL, you are not allowed to do this. ... False. The standard assignment has this clause: Upon thirty days' prior written notice, the Foundation agrees to grant me non-exclusive rights to use the Work (i.e. my changes and enhancements, not the program which I enhanced) as I see fit; (and the Foundation's rights shall otherwise continue unchanged). There are other options. For example, you can "disclaim" copyright - i.e. sign a statement that you're putting your changes into the public domain. > 2. One of the dangers of assigning copyright to the FSF is that if > the FSF happens to be taken over by some evil corporate identity or > anyone with different ideas than RMS, they will own all > copyright-assigned code, and can revoke the GPL and enforce any > license they please. ... False. From http://gcc.gnu.org/fsf-forms/assign.changes: (The FSF uses multiple forms, but they have this clause.) The Foundation promises that all distribution of the Work, or of any work "based on the Work", that takes place under the control of the Foundation or its assignees, shall be on terms that explicitly and perpetually permit anyone possessing a copy of the work to which the terms apply, and possessing accurate notice of these terms, to redistribute copies of the work to anyone on the same terms. These terms shall not restrict which members of the public copies may be distributed to. These terms shall not require a member of the public to pay any royalty to the Foundation or to anyone else for any permitted use of the work they apply to, or to communicate with the Foundation or its agents in any way either when redistribution is performed or on any other occasion. -- --Per Bothner per(a)bothner.com http://www.bothner.com/~per/

2 participants
1 comments

RE: (setq indent-tabs-mode nil) not working in 21.2b36 on NT? 24 years, 1 month

Troy Noble

>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: >>>>> "sperber" == sperber(a)informatik.uni-tuebingen.de <sperber(a)informatik.uni-tuebingen.de> writes: sperber> Sure sounds like the pdump bug we've known about for ages. Of course, sperber> we need to know if you're using pdump to be sure. Mike, It does indeed appear to be a problem with pdump. Once I enabled USE_PORTABLE_DUMPER=1 The one I compiled started exhibiting the same behavior as the 21.2b36 binary I downloaded off the net. If I breakpoint at src/indent.c line 317, the debugger reports indent_tabs_mode = 1, even though describe-variable indent-tabs-mode indicates the value is "nil". That is indeed consistent with the behavior I'm seeing (it is incorrectly inserting tabs instead of spaces). APA> we need a lot more info. That's how problems can get solved: facts. Adrian, Apologies for not providing more information. I've not contributed bug reports to xemacs list before, so am kinda new at this. APA> How did you get the sources (CVS or tarballs)? I used the xemacs-21.2-b36.tar.gz tarball. This same problem has been reported since b34, so I know it's somewhat long-standing. If the pdump bug has been around a long time, that would explain it. APA> So you did a Windows native build, right? Yes, win32 native GUI... no X support... using MSVC 5.0, not cygwin. APA> Please send us your xemacs/nt/config.inc file then. My nt/config.inc included below. I took a pretty simple-minded approach and put all the .h and .lib files for all the aux libraries in the same directory. Seemed to work OK. APA> Did you use the portable dumper option (we can tell from config.inc)? Not originally. And my .exe worked fine But once I followed Mike's suggestion and turned use of pdump on, the problem re-appeared with the version I compiled too. I would be willing to troubleshoot further if someone could point the way, but as I said.. I'm kinda new at this, so not sure how much progress I'd make. APA> These are just a few simple question on the way to solve the mystery. Thanks for the feedback. Where should I go from here? Troy nt/config.inc: # -*- mode: makefile -*- ############################################################################ INSTALL_DIR=c:\Programs\XEmacs\XEmacs-$(XEMACS_VERSION_STRING) PACKAGE_PREFIX=c:\Programs\XEmacs\xemacs-packages;c:\Program Files\XEmacs ############################################################################ # Multilingual support (not currently working). HAVE_MULE=0 # Native MS Windows support. HAVE_MS_WINDOWS=1 # X Windows support. HAVE_X_WINDOWS=0 X11_DIR= ############################################################################ # Set this to enable XPM support (virtually mandatory), and specify # the directory containing xpm. HAVE_XPM=1 XPM_DIR=c:\build\XEmacs\auxfiles # Set this to enable GIF support. HAVE_GIF=1 # Set this to enable PNG support (virtually mandatory), and specify # the directories containing png and zlib. HAVE_PNG=1 PNG_DIR=c:\build\XEmacs\auxfiles ZLIB_DIR=c:\build\XEmacs\auxfiles # Set this to enable TIFF support, and specify the directory containing tiff. HAVE_TIFF=0 TIFF_DIR= # Set this to enable JPEG support, and specify the directory containing jpeg. HAVE_JPEG=1 JPEG_DIR=c:\build\XEmacs\auxfiles # Set this to enable XFace support, and specify the directory containing # compface. HAVE_XFACE=0 COMPFACE_DIR= ############################################################################ # Set this to specify the location of makeinfo. (If not set, XEmacs will # attempt to use its built-in texinfo support when building info files.) MAKEINFO=c:\p4d\Build_win32_2.0\x86\cygwin\bin\makeinfo.exe ############################################################################ # Set this to enable some debug code that doesn't slow things down. DEBUG_XEMACS=1 # Set this to speed up building, for development purposes. QUICK_BUILD=0 # Set this to see exactly which compilation commands are being run (not # generally recommended). VERBOSECC=1 # Set this to get nmake to use dependency info (requires Perl to be installed) DEPEND=1 ############################################################################ # Some technical options. USE_MINIMAL_TAGBITS=0 USE_INDEXED_LRECORD_IMPLEMENTATION=0 USE_PORTABLE_DUMPER=1 GUNG_HO=0

1 participants
0 comments

Re: (setq indent-tabs-mode nil) not working in 21.2b36 on NT? 24 years, 1 month

Michael Sperber

>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: >>>>> "Troy" == Troy Noble <troy.noble(a)channelpoint.com> writes: Troy> Hey all, Troy> I compiled XEmacs 21.2 b36 from sources with Visual C++ 5.0 Troy> on my own machine in anticipation of firing up a debug Troy> session and looking in the problem some more (namely Troy> indent_to in indent.c. does not honor indent-tabs-mode=nil Troy> setting). Troy> Guess what, indent-tabs-mode = nil works just fine in my Troy> compiled version. Very puzzling. Troy> So I'm not sure why the pre-compiled binary of Troy> XEmacs-21.2-b36-win32.zip off the net is broken. Also makes Troy> me wonder what else is broken in that same beta build??? Sure sounds like the pdump bug we've known about for ages. Of course, we need to know if you're using pdump to be sure. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: (setq indent-tabs-mode nil) not working in 21.2b36 on NT? 24 years, 1 month

Adrian Aichner

>>>>> "Troy" == Troy Noble <troy.noble(a)channelpoint.com> writes: Troy> Hey all, Troy> I compiled XEmacs 21.2 b36 from sources with Visual C++ 5.0 Troy> on my own machine in anticipation of firing up a debug Troy> session and looking in the problem some more (namely Troy> indent_to in indent.c. does not honor indent-tabs-mode=nil Troy> setting). Troy> Guess what, indent-tabs-mode = nil works just fine in my Troy> compiled version. Very puzzling. Troy> So I'm not sure why the pre-compiled binary of Troy> XEmacs-21.2-b36-win32.zip off the net is broken. Also makes Troy> me wonder what else is broken in that same beta build??? Troy> Guess I need to send a mail to the individual who builds the Troy> kit and find out how they built it and try to put our heads Troy> together to figure out why their binary didn't work and mine Troy> did. In theory, they should function identically, right? Troy> Is it possible to run strings and grep out the version ID's Troy> of all the C files used to build the program? Maybe I'll Troy> try that. I suppose that won't work thought if the binary Troy> was stripped... My thought here is that maybe we both used Troy> different versions of the source to build from? I would Troy> hope not though. Hi Troy, we need a lot more info. That's how problems can get solved: facts. How did you get the sources (CVS or tarballs)? If CVS, what's the command you used to get the sources you built from? If you did a "cvs update" to the latest sources (instead of -r r21-2-36) then you got the latest sources at that particular time, which is something after 21.2-b36, more close to a future 21.2-b37. So you did a Windows native build, right? Please send us your xemacs/nt/config.inc file then. Did you use the portable dumper option (we can tell from config.inc)? These are just a few simple question on the way to solve the mystery. Best regards, Adrian Troy> Troy Troy> -----Original Message----- Troy> From: Troy Noble [mailto:troy.noble＠channelpoint.com] Troy> Sent: Friday, October 20, 2000 4:20 PM Troy> To: 'xemacs-beta(a)xemacs.org' Troy> Subject: (setq indent-tabs-mode nil) not working in 21.2b36 on NT? Troy> I'm running: Troy> XEmacs 21.2 (beta36) "Notus" [Lucid] (i586-pc-win32) of Wed Oct 11 2000 on Troy> NEVERYON Troy> Even when I have indent-tabs-mode set to nil, XEmacs is inserting Troy> tabs for indents. Troy> Doesn't matter whether I use (setq-default indent-tabs-mode nil) to set Troy> it globally, or use (setq indent-tabs-mode nil) to set it buffer local. Troy> Also Troy> doesn't matter whether it's cperl-mode, java-mode, cc-mode, or Troy> just good ol' text-mode. Troy> I searched back through the xemacs-beta archives and saw this Troy> same thing reported last back in July for b34. I am still seeing the Troy> same problem with the 21.2b36 binary for NT. So assume it Troy> has not been fixed. Troy> I built the 21.2b36 from source on RedHat Linux 6.2, and using Troy> the same .emacs options file... it works just fine. Also works just Troy> fine on XEmacs 21.1.9 on NT win32. Troy> BTW, diff'd lisp/indent.el from XEmacs 21.1.9 with this one, and it hasn't Troy> changed since then. So it's gotta be lower down. Suspect it's in the Troy> indent.c Troy> somewhere, which was also the conclusion of the last round of discussions Troy> that I read. Troy> So what would cause indent.c to function differently on NT than on Linux? Troy> One thing I did not do is build on Linux with mule support, and maybe Troy> the NT binary does? Troy> Am out of ideas unless I get a chance to re-compile it myself Troy> from scratch on NT (which sounded sorta involved)... Troy> I'd rather not do so if someone else has any better ideas. Troy> Thanks! Troy -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

1 participants
0 comments

RE: (setq indent-tabs-mode nil) not working in 21.2b36 on NT? 24 years, 1 month

Troy Noble

Hey all, I compiled XEmacs 21.2 b36 from sources with Visual C++ 5.0 on my own machine in anticipation of firing up a debug session and looking in the problem some more (namely indent_to in indent.c. does not honor indent-tabs-mode=nil setting). Guess what, indent-tabs-mode = nil works just fine in my compiled version. Very puzzling. So I'm not sure why the pre-compiled binary of XEmacs-21.2-b36-win32.zip off the net is broken. Also makes me wonder what else is broken in that same beta build??? Guess I need to send a mail to the individual who builds the kit and find out how they built it and try to put our heads together to figure out why their binary didn't work and mine did. In theory, they should function identically, right? Is it possible to run strings and grep out the version ID's of all the C files used to build the program? Maybe I'll try that. I suppose that won't work thought if the binary was stripped... My thought here is that maybe we both used different versions of the source to build from? I would hope not though. Troy -----Original Message----- From: Troy Noble [mailto:troy.noble＠channelpoint.com] Sent: Friday, October 20, 2000 4:20 PM To: 'xemacs-beta(a)xemacs.org' Subject: (setq indent-tabs-mode nil) not working in 21.2b36 on NT? I'm running: XEmacs 21.2 (beta36) "Notus" [Lucid] (i586-pc-win32) of Wed Oct 11 2000 on NEVERYON Even when I have indent-tabs-mode set to nil, XEmacs is inserting tabs for indents. Doesn't matter whether I use (setq-default indent-tabs-mode nil) to set it globally, or use (setq indent-tabs-mode nil) to set it buffer local. Also doesn't matter whether it's cperl-mode, java-mode, cc-mode, or just good ol' text-mode. I searched back through the xemacs-beta archives and saw this same thing reported last back in July for b34. I am still seeing the same problem with the 21.2b36 binary for NT. So assume it has not been fixed. I built the 21.2b36 from source on RedHat Linux 6.2, and using the same .emacs options file... it works just fine. Also works just fine on XEmacs 21.1.9 on NT win32. BTW, diff'd lisp/indent.el from XEmacs 21.1.9 with this one, and it hasn't changed since then. So it's gotta be lower down. Suspect it's in the indent.c somewhere, which was also the conclusion of the last round of discussions that I read. So what would cause indent.c to function differently on NT than on Linux? One thing I did not do is build on Linux with mule support, and maybe the NT binary does? Am out of ideas unless I get a chance to re-compile it myself from scratch on NT (which sounded sorta involved)... I'd rather not do so if someone else has any better ideas. Thanks! Troy

1 participants
0 comments

Re: xemacs binary for irix 6.3 24 years, 1 month

Vin Shelton

Ivar, It seems that we only have the binaries for Irix 6.5 at ftp.xemacs.org. I've forwarded your message to the xemacs-beta list, where someone will respond if they know where any 6.3 binaries are. What problems did you have with building (which version of?) XEmacs under Irix 6.3? It may require gcc, IIRC. Good luck, vin shelton >>>>> On Thu, 19 Oct 2000, Ivar Nor <in(a)epmtech.jotne.com> said: Ivar> I've just changed job, and unfortunately I do not have xemacs on Ivar> my irix 6.3 computer. I've been searching the web for a binary Ivar> version for 6.3, but all I can find is for irix 6.5. I've tried Ivar> to compile the source code, but have run into all sorts of Ivar> problems. Would you happen to know a site where I can still Ivar> find a binary for irix 6.3?

1 participants
0 comments

Re: outstanding issues, "dired" in the Subject header 24 years, 1 month

Michael Sperber

>>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: >>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: >>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: APA> What is the canonical repository for EFS development? Michael> I don't know what "canonical" means in this context. The Michael> primary CVS archive for EFS is in Tübingen and private. Michael> An automated procedure creates package releases from it. APA> Oh, I was just trying to better understand your release process for APA> EFS and dired to cooperate better. I think I got the idea now. You APA> collect changes (resulting from bug reports and patches) in your APA> private repository. At release time you commit the new release into APA> the corresponding xemacs-packages module on cvs.xemacs.org. APA> Did I get it right? Exactly. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

Re: outstanding issues, "dired" in the Subject header 24 years, 1 month

Adrian Aichner

>>>>> "Michael" == Michael Sperber <sperber(a)informatik.uni-tuebingen.de> writes: >>>>> "APA" == Adrian Aichner <adrian(a)xemacs.org> writes: APA> What is the canonical repository for EFS development? Michael> I don't know what "canonical" means in this context. The Michael> primary CVS archive for EFS is in Tübingen and private. Michael> An automated procedure creates package releases from it. Oh, I was just trying to better understand your release process for EFS and dired to cooperate better. I think I got the idea now. You collect changes (resulting from bug reports and patches) in your private repository. At release time you commit the new release into the corresponding xemacs-packages module on cvs.xemacs.org. Did I get it right? Schöne Grüße, Adrian Michael> -- Michael> Cheers =8-} Mike Michael> Friede, Völkerverständigung und überhaupt blabla -- Adrian Aichner <adrian(a)xemacs.org>, http://www.xemacs.org

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta October 2000