June 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: mouse-track-insert bug/limitation question (Windows NT, native build) 24 years, 5 months

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Vin> In 21.1.10 on Linux x86, both methods 1 and 2 work as Vin> advertised for different buffers in the same window. Thanks, Vin! Vin> - vin >>>>> On 10 Jun 2000, Adrian Aichner <aichner(a)ecf.teradyne.com> said: APA> Hello All! APA> I have become an enthusiastic fan of APA> C-button1 mouse-track-insert APA> recently. APA> 1. APA> I pick the point where I want to insert something, hold down the Ctrl APA> key, and drag thru the selection I want to insert. APA> 2. APA> As an alternative, double clicking on the word I want to insert (while APA> holding Ctrl pressed) will also insert at the point current when Ctrl APA> was pressed. APA> The little gripe I have is this. APA> Method 1 works even when picking a selection in another buffer, method APA> 2 does not, in my native NT builds of XEmacs-21.1.10-close-to-11 and APA> XEmacs-21.2-b34-with-latest-CVS-changes. APA> Could somebody please let me know whether method 2 works under X (UNIX APA> or even cygwin builds on Windows NT) with the selection being made in APA> another buffer? APA> Does anyone even have an explanation/workaround/solution? Turns out mswindows implements this in mouse.el, while x used x-mouse.el. I can't find a solution for this problem, but here is the symptom: When doing a mouse-track-insert from another buffer using double-click the default 'default-mouse-track-click-hook gets called under mswindows instead of the desired 'mouse-track-insert-click-hook Adrian APA> Best regards, APA> Adrian

1 participants
0 comments

Re: mouse-track-insert bug/limitation question (Windows NT, native build) 24 years, 5 months

Vin Shelton

In 21.1.10 on Linux x86, both methods 1 and 2 work as advertised for different buffers in the same window. - vin >>>>> On 10 Jun 2000, Adrian Aichner <aichner(a)ecf.teradyne.com> said: APA> Hello All! APA> I have become an enthusiastic fan of APA> C-button1 mouse-track-insert APA> recently. APA> 1. APA> I pick the point where I want to insert something, hold down the Ctrl APA> key, and drag thru the selection I want to insert. APA> 2. APA> As an alternative, double clicking on the word I want to insert (while APA> holding Ctrl pressed) will also insert at the point current when Ctrl APA> was pressed. APA> The little gripe I have is this. APA> Method 1 works even when picking a selection in another buffer, method APA> 2 does not, in my native NT builds of XEmacs-21.1.10-close-to-11 and APA> XEmacs-21.2-b34-with-latest-CVS-changes. APA> Could somebody please let me know whether method 2 works under X (UNIX APA> or even cygwin builds on Windows NT) with the selection being made in APA> another buffer? APA> Does anyone even have an explanation/workaround/solution? APA> Best regards, APA> Adrian

1 participants
0 comments

mouse-track-insert bug/limitation question (Windows NT, native build) 24 years, 5 months

Adrian Aichner

Hello All! I have become an enthusiastic fan of C-button1 mouse-track-insert recently. 1. I pick the point where I want to insert something, hold down the Ctrl key, and drag thru the selection I want to insert. 2. As an alternative, double clicking on the word I want to insert (while holding Ctrl pressed) will also insert at the point current when Ctrl was pressed. The little gripe I have is this. Method 1 works even when picking a selection in another buffer, method 2 does not, in my native NT builds of XEmacs-21.1.10-close-to-11 and XEmacs-21.2-b34-with-latest-CVS-changes. Could somebody please let me know whether method 2 works under X (UNIX or even cygwin builds on Windows NT) with the selection being made in another buffer? Does anyone even have an explanation/workaround/solution? Best regards, Adrian

1 participants
0 comments

Re: configure probs with sparc-unknown-linux 24 years, 5 months

Vin Shelton

Is this still true? Do you want to supply a patch for this? - vin >>>>> On 20 Feb 2000, Jason R Mastaler <jason(a)mastaler.com> said: Jason> I'm not able to build XEmacs on Redhat Linux 6.1 for sparc due to some Jason> problems with the configure script. This goes for the latest 21.2 Jason> beta as well as 21.1.9. `sed' is having trouble with some of the Jason> lines in conftest.s2 and conftest.frag. sed on this machine is GNU Jason> sed version 3.02. Jason> Has anyone else seen this problem? The output below is what I see Jason> at the end of ./configure just after Installation is written out. Jason> The result is that all the Makefiles end up as empty files. Jason> creating ./config.status Jason> creating Makefile.in Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating lib-src/Makefile.in Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating lwlib/Makefile.in Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating src/Makefile.in Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating src/paths.h Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating lib-src/config.values Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating lib-src/ellcc.h Jason> sed: file conftest.s2 line 35: Unknown command: `` Jason> creating src/config.h Jason> sed: file conftest.frag line 1: Unknown command: ``%'' Jason> creating lwlib/config.h Jason> sed: file conftest.frag line 1: Unknown command: ``%'' Jason> creating ./Makefile Jason> creating ./GNUmakefile Jason> creating lib-src/Makefile Jason> creating lib-src/GNUmakefile Jason> creating lwlib/Makefile Jason> creating lwlib/GNUmakefile Jason> creating src/Makefile Jason> creating src/GNUmakefile Jason> % ls -l Makefile lib-src/Makefile lwlib/Makefile src/Makefile Jason> -r--r--r-- 1 jason wheel 0 Feb 19 23:31 Makefile Jason> -r--r--r-- 1 jason wheel 0 Feb 19 23:31 lib-src/Makefile Jason> -r--r--r-- 1 jason wheel 0 Feb 19 23:31 lwlib/Makefile Jason> -r--r--r-- 1 jason wheel 0 Feb 19 23:31 src/Makefile

1 participants
0 comments

Re: Problem with package-get 24 years, 5 months

Vin Shelton

Jan, Do you want to cons up a patch to this effect for 21.1.11? - vin >>>>> On 21 Feb 2000, Jan Vroonhof <vroonhof(a)math.ethz.ch> said: "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: >> AFAIK the change to coding-system 'binary in i-f-c-l is already in >> 21.2 ... oops, no, that's only in UTF-2000. Evidently Tomo found it >> necessary but hasn't yet reported it to xemacs-beta. Jan> He did... However he combined it with some other crap (explicit Jan> knowledge about jka-compr) from FSF emacs, and I vetoed that. A stand Jan> alone patch never appeared IMHO. My improved patch contains the Jan> 'binary part too, but that is stalled waiting for a new EFS. However Jan> it doesn't really require it so I guess it is time to apply the core Jan> part of it. Jan> So Jan> 1. package-get should use i-f-c-l Jan> 2. In 21.1.10 i-f-c-l should be made to use 'binary Jan> 3. Apply the core half of my patch to 21.2 (includes coding system Jan> change). Jan> Jan

1 participants
0 comments

Re: 21.2.34 documentation bug 24 years, 5 months

Colin Rafferty

Raymond Toy writes: > With the latest sumo tarball and 21.2.34 on Solaris, I get some weird > results from hyper-apropos. > C-h a change-log produces this: > b* vc-comment-to-change-log - ffer pop-to-buffer] 9 (#$ . 20892)]) > b* vc-update-change-log - "fVC rename file: \nFRename to: "]) > However, if I look at the actual code, the comment is right, so I have > no idea what the problem is. > Note: this is vc-cc. The problem is that the DOC file that XEmacs is using is not the one that was built when it was dumped. DOC files are associated exactly with each built XEmacs. They cannot be shared between different versions. -- Colin

1 participants
0 comments

21.2.34 documentation bug 24 years, 5 months

Raymond Toy

With the latest sumo tarball and 21.2.34 on Solaris, I get some weird results from hyper-apropos. C-h a change-log produces this: b* vc-comment-to-change-log - ffer pop-to-buffer] 9 (#$ . 20892)]) b* vc-update-change-log - "fVC rename file: \nFRename to: "]) And if I look at vc-comment-to-change-log shows: `vc-comment-to-change-log' (buffer: *Hyper Apropos*, mode: Hyper-Apropos) Interactive compiled Lisp function, (loaded from "vc"): arguments: (&optional whoami file-name) ffer pop-to-buffer] 9 (#$ . 20892)]) #＠230 Enter last VC comment into change log file for current buffer's file. Optional arg (interactive prefix) non-nil means prompt for user name and site. Second arg is file name of change log. If nil, uses `change-log-default-name'. However, if I look at the actual code, the comment is right, so I have no idea what the problem is. Note: this is vc-cc. Ray

1 participants
0 comments

ANNOUNCE: MinGW grahpics library binaries 24 years, 5 months

Ben Wing

I've posted MinGW binaries of all the graphics libraries required by XEmacs at ftp://ftp.xemacs.org/pub/xemacs/aux/mingw/ Thanks to Craig Lanning for providing these. -- Ben In order to save my hands, I am cutting back on my mail. I also write as succinctly as possible -- please don't be offended. If you send me mail, you _will_ get a response, but please be patient, especially for XEmacs-related mail. If you need an immediate response and it is not apparent in your message, please say so. Thanks for your understanding. See also http://www.666.com/ben/chronic-pain/

1 participants
0 comments

Re: xemacs crashes immediately on Alpha Linux 24 years, 5 months

SL Baur

Falk Hueffner <falk.hueffner(a)student.uni-tuebingen.de> writes in xemacs-beta(a)xemacs.org: > SL Baur <steve(a)turbolinux.co.jp> writes: ... >> Which distribution of Linux are you using? (and kernel, gcc, glibc, >> binutils versions, etc.) > Debian 2.2 (potato) > Linux version 2.2.14 > gcc version 2.95.2 20000313 (Debian GNU/Linux) > Compaq C T6.2-235 on Linux 2.2.14 alpha / Compiler Driver T6.2-235 (Linux) cc Driver > glibc 2.1.3 > binutils 2.9.5.0.37 That combination of software does not compile out-of-the-box on the Alpha. ... > Now, should I still try to find the problem, or would it be OK to just > mention in PROBLEMS that --pdump has to be used? I. e., does --pdump > have any disadvantages, except for it's experimentalness? Please try to find the problem if you can, ie. see if you can isolate where in the code it is crashing. This is a potentially serious bug, but we won't know for sure until we take a look at it.

1 participants
0 comments

Re: forwarded message from Charles G Waldman 24 years, 5 months

Mike Alexander

At 3:57 PM -0500 6/6/00, Kevin Cutts wrote: >I can confirm the same problem. call-process-region doesn't seem to >connect stdin of the process to the contents of the buffer. Any ideas? I submitted some patches for that a week or so ago, but they were somewhat less than perfect. I just submitted another version, let's see if they work any better. Mike

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 June 2000