June 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: mswindows-get-clipboard broken in beta 15? 25 years, 5 months

Dmitry Yaitskov

Adrian Aichner <aichner(a)ecf.teradyne.com> wrote: <snip> > how do you copy text into XEmacs-21.2b15 under X then? > > Try this please: > Select text in a cmdtool or dtpad or textedit. > Edit->Copy it. > In an XEmacs window select some text to be replaced. > Press the XEmacs Paste button. > > Does this replace the region with the copied text from outside XEmacs? > > The analoguous operation *has* worked on system-type windows-nt, > window-system mswindows, previous to 21.2b15. > > I miss it badly (and so does Dmitry), sneaf, sneaf .. And so, I dare say, will 99% of all Windows users. And please not that it's even worse! Simply selecting text without doing any explicit copy or cut in XEmacs b15 looks as if the text *has* been copied to the clipboard. And guess what? It is, I just tried (no, I do not run b15 normally, it is unusable for me). -- Cheers, -Dima.

1 participants
0 comments

Re: mswindows-get-clipboard broken in beta 15? 25 years, 5 months

Adrian Aichner

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> Dmitry Yaitskov <dimas(a)home.com> writes: >> I do not care much about C-c being copy, this is something that can >> be easily customized if needed. The thing I'm talking about here is >> something much more basic. With the latest changes what happens is, >> when under mswindows I *select* text (note - not copy or paste, just >> select), the selection goes into the clipboard, overwriting its >> previous contents. Hrvoje> This sounds like a bug to me. Under XEmacs, selecting Hrvoje> text will not overwrite the clipboard contents -- it will Hrvoje> merely grab the "primary selection" (which is separate Hrvoje> from the clipboard.) Hello Hrvoje, how do you copy text into XEmacs-21.2b15 under X then? Try this please: Select text in a cmdtool or dtpad or textedit. Edit->Copy it. In an XEmacs window select some text to be replaced. Press the XEmacs Paste button. Does this replace the region with the copied text from outside XEmacs? The analoguous operation *has* worked on system-type windows-nt, window-system mswindows, previous to 21.2b15. I miss it badly (and so does Dmitry), sneaf, sneaf .. Adrian Hrvoje> It is a separate matter that clipboard is rarely used Hrvoje> under X, so that the operation of "pasting" (middle mouse Hrvoje> button) first tries to paste the contents of primary Hrvoje> selection. -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: Lisp, Siod and LyX, Guile and ANSI Lisp 25 years, 5 months

Karl M. Hegbloom

>>>>> "Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> I think the "open-source" model is deeply overhyped. Hrvoje> Maybe someone will write a new essay that explains its Hrvoje> shortcomings in some detail. It's a recruiting gimmick.

1 participants
0 comments

Re: Lisp, Siod and LyX, Guile and ANSI Lisp 25 years, 5 months

Karl M. Hegbloom

What about `ECoLisp'? (Once again, let me qualify this mail with a loud I'M JUST A STUDENT, NOT AN EXPERT NOR AN AUTHORITY.) I plan to try and understand ECL at some point; I suspect it will be a year still before I can do it right. From the README: 8<--------------------------------------------------------------->8 This is ECoLisp (ECL), an Embeddable Common Lisp implementation. ECL is an implementation of Common Lisp designed for being embeddable into C based applications. ECL uses standard C calling conventions for Lisp compiled functions, which allows C programs to easily call Lisp functions and viceversa. No foreign function interface is required: data can be exchanged between C and Lisp with no need for conversion. ECL is based on a Common Runtime Support (CRS) which provides basic facilities for memory managment, dynamic loading and dumping of binary images, support for multiple threads of execution. The CRS is built into a library that can be linked with the code of the application. ECL is modular: main modules are the program development tools (top level, debugger, trace, stepper), the compiler, and CLOS. A native implementation of CLOS is available in ECL: one can configure ECL with or without CLOS. A runtime version of ECL can be built with just the modules which are required by the application. The ECL compiler compiles from Lisp to C, and then invokes the GCC compiler to produce binaries. ECL has been ported so far on: - Sun workstations with SunOS 4.x or Solaris 2.x - Silicon Graphics with IRIX 4.x - NeXT with NeXTStep 2.x - IBM PC with DOS/emx - IBM PC with DOS/go32 - IBM PC with Linux - IBM PC with FreeBSD 1.1.5 The newest versions are available via anonymous ftp from: - ftp.icsi.berkeley.edu [128.32.201.6], directory /pub/ai/ecl - ftp.di.unipi.it [131.114.4.6], directory /pub/lang/lisp

1 participants
0 comments

Re: Lisp, Siod and LyX, Guile and ANSI Lisp 25 years, 5 months

Karl M. Hegbloom

:-) I'm no expert; don't let me pretend to be one. I've just begun to learn to write code, and to understand the Scheme interpreter, &c. I'm a junior here. A student only, at this point.

1 participants
0 comments

Re: ldap support fails 25 years, 5 months

Karl M. Hegbloom

>>>>> "Michael" == Michael Harnois <mharnois(a)willinet.net> writes: Michael> I ended up disabling ldap support in the latest 21.2 from Michael> CVS because I couldn't figure out a way around this Michael> error: Michael> dereferencing pointer to incomplete type Michael> I tried several different things to no avail. This has Michael> been compiling for me for some time with no problem; I'm Michael> not sure what has changed, although I see there have been Michael> changes applied. I thought this was a bug in the `libopenldap', so I emailed the maintainer of the Debian libopenldap package. (Ben Collins <bcollins(a)debian.org>) He told me that there's been changes made... The `potato' version of libopenldap is a current CVS development snapshot. I'd tracked it down to there being, in `ldap.h', a `typedef struct ldap LDAP', but no `struct ldap' to be found. I was told that `struct ldap' has been moved to private headers, since it's not supposed to be visible to user codes anymore. He said perhaps he'd have a look at the XEmacs `eldap.[hc]', and I told him about cvs.xemacs.org, told him the password to anoncvs, about the WWW at cvs.xemacs.org, and that more info is in the FAQ, please join the list, etc. I don't know if he's got time to deal with it or not... I guess Oscar F. is really the one who ought to do the work anyway?? At any rate, I have no clue how to fix it. I'll look at your diffs, iff I've the time and remember to. The stack of books is threatening to fall on me again... I've got to go.

1 participants
0 comments

Re: mswindows-get-clipboard broken in beta 15? 25 years, 5 months

Hrvoje Niksic

Dmitry Yaitskov <dimas(a)home.com> writes: > I do not care much about C-c being copy, this is something that can > be easily customized if needed. The thing I'm talking about here is > something much more basic. With the latest changes what happens is, > when under mswindows I *select* text (note - not copy or paste, just > select), the selection goes into the clipboard, overwriting its > previous contents. This sounds like a bug to me. Under XEmacs, selecting text will not overwrite the clipboard contents -- it will merely grab the "primary selection" (which is separate from the clipboard.) It is a separate matter that clipboard is rarely used under X, so that the operation of "pasting" (middle mouse button) first tries to paste the contents of primary selection. > replacing the new selection with the clipboard contents is > *impossible*, I cannot even write a new "my-paste" lisp function to > do that - the XEmacs behaviour is now "consistent" with X selection > being the same as "clipboard", Nope.

1 participants
0 comments

[SUCCESS] 21.2 (beta15) "Sakuragawa" XEmacs Lucid on i586-pc-linux 25 years, 5 months

John Mignault

Patched up from b14. Ran 'make check' and all tests passed. Running fine so far. j > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.2.12/Installation: > (Output from most recent run of ./configure) uname -a: Linux jbm 2.0.34 #1 Fri May 8 16:05:57 EDT 1998 i586 unknown ./configure '--dynamic' '--with-database=gnudbm' '--with-xpm' '--with-mule=no' '--with-png=yes' '--with-ldap' '--with-sound=native' '--use-union-type' '--compiler=egcs' '--debug' XEmacs 21.2-b15 "Sakuragawa" configured for `i586-pc-linux'. Where should the build process find the source code? /usr/local/src/xemacs-21.2.12 What installation prefix should install use? /usr/local What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? egcs -g -O3 -Wall -Wno-switch Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for LDAP (UMich libs). Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using the union type for Lisp_Objects. Compiling in extra code for debugging. WARNING: --------------------------------------------------------- WARNING: Compiling in support for runtime error checking. WARNING: XEmacs will run noticeably more slowly as a result. WARNING: Error checking is on by default for XEmacs beta releases. WARNING: --------------------------------------------------------- > /usr/local/src/xemacs-21.2.12/beta.err does not exist! -- #!/usr/bin/perl $dot="\x2e";$lt="\x3c";$gt="\x3e";$at="\x40"; print "J Mignault ${lt}jbm${at}panix${dot}com${gt}\n"; $wright = qq(Did Washington just flash a quarter for his ID?);

1 participants
0 comments

Re: mswindows-get-clipboard broken in beta 15? 25 years, 5 months

Dmitry Yaitskov

Hrvoje Niksic <hniksic(a)srce.hr> wrote: > Dmitry Yaitskov <dimas(a)home.com> writes: > > > I am not sure I understand you correctly, but if so - this means > > that it breaks the way cut/copy/paste is done in Windows. Is it a > > "good thing"? Why is that a lot better than what we had before? > > I, for one, think that consistency across platforms is a good thing. > You won't see C-c being copy or C-v paste in XEmacs any time soon -- > at least not by default. For that matter, XEmacs already does many > things differently than typical X applications do. > > I'm not sure I fully understand your requests, though, so I might be > wrong about consistency. I do not care much about C-c being copy, this is something that can be easily customized if needed. The thing I'm talking about here is something much more basic. With the latest changes what happens is, when under mswindows I *select* text (note - not copy or paste, just select), the selection goes into the clipboard, overwriting its previous contents. Hence the one of my most often used ops - getting something into the clipboard, then selecting something else and replacing the new selection with the clipboard contents is *impossible*, I cannot even write a new "my-paste" lisp function to do that - the XEmacs behaviour is now "consistent" with X selection being the same as "clipboard", or rather with the lack of a notion of a clipboard in X. This is consistent with X, but for Windows it is absolutely outrageous. Selection and clipboard is not the same in Windows, and - for once - this is something in which Windows is way better than X. I hope that I simply missed something (I certainly could've, in which case I sincerely apologize for my drivel), but if not - the latest change simply makes XEmacs *unusable* for me, period. For now, I went back to b14... -- Cheers, -Dima.

1 participants
0 comments

Re: xemacs.mak patch to build 21.2-b14 NT native 25 years, 5 months

Adrian Aichner

>>>>> "lykos" == Norbert Koch <n.koch(a)delta-ii.de> writes: lykos> Adrian, lykos> I'm not sure what really causes the problems, but after I lykos> put the sources back to their old location and after lykos> applying your patch, everything seems to look pretty ok for lykos> me. Do you know whether there are known problems with lykos> either moving the sources around or having the sources on a lykos> "mounted" drive? Have you run nmake -f xemacs.mak distclean in the new location? I haven't ever tried moving the sources, don't know whether this works. lykos> I also had to remove the mule-coding dependencies from your lykos> makefile in order to get things running, since I build with lykos> mule and the c-file no longer seems to be part of the Now that you mention it: I have also removed mule-coding dependecies (I think Andy suggested that fix) but haven't sent a patch. lykos> distribution. It's pretty dumb that we can't simply do a lykos> make depend on a WinNT system but have to remove files by lykos> hand - sigh. I send a patch to xemacs-patches. Regards, Adrian lykos> 'norbert. -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

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 1999