Re: Strange bug.
24 years
Nickolay Pakoulin
Nickolay Pakoulin
intro: "NP" == Nick Pakoulin <npak(a)ispras.ru> writes:
NP> Put the following code into a file, say "tmp.el":
NP> ---------------------------------------------------------------------
NP> (require 'edebug)
NP> (eval-after-load "edebug" (progn (put (quote defun) (quote
NP> edebug-form-spec) (quote (&define name lambda-list [&optional stringp]
NP> [&optional ("interactive" (&or stringp def-form))] def-body)))))
NP> ---------------------------------------------------------------------
Never mind, I got it.
Friday evening - "hard day's night" :))
Thinking is not that fast as after weekends :))
Nick.
- 1 participants
- 0 comments
Dired update sucks
24 years
Neal D. Becker
Neal D. Becker
I'm using dired version Value: "7.10" with Value: "21.1 (patch 14)
\"Cuyahoga Valley\" XEmacs Lucid". Since I last updated packages
dired really sucks.
First problem is it keeps screwing up the listing so that the columns
don't align. Hitting 'g' fixes it.
Second, copying a file to another in the same directory inserts it
into the listing at an apparantly random location, rather than
alphabetical.
All in all, I think the previous version (which I never had any
problem with) was better.
- 2 participants
- 1 comments
Strange bug.
24 years
Nickolay Pakoulin
Nickolay Pakoulin
Put the following code into a file, say "tmp.el":
---------------------------------------------------------------------
(require 'edebug)
(eval-after-load "edebug"
(progn
(put (quote defun)
(quote edebug-form-spec)
(quote (&define name lambda-list [&optional stringp]
[&optional ("interactive" (&or stringp def-form))]
def-body)))))
---------------------------------------------------------------------
Then from the command line:
xemacs -vanilla -eval '(load-file "tmp.el")'
I have tried it on windows 2000 with xemacs-21.4.3, xemacs-21.5.1, emacs-20.7.1
and in each case I got the error:
---------------------------------------------------------------------
Symbol's function definition is void: &define
---------------------------------------------------------------------
emacs-20.7.1 on Linux gave the same error message.
xemacs-21.2.46 both mule and no-mule on Linux loaded *without* complains.
BUT! The second load goes ok in all tested emacsens:
xemacs -vanilla -eval '(condition-case nil (load-file "~/tmp.el")\
(error (setq failed t))) (load-file "~/tmp.el")'
All emacsens that failed <<-eval '(load-file "tmp.el")'>> succeeded in the
second case and set `failed' to `t'.
Nick.
- 1 participants
- 0 comments
Mule-related corrections to manual
24 years
Alexey Mahotkin
Alexey Mahotkin
Salam,
Long ago, under subject "some MULE inconsistencies [with patch]" I've
already sent half of that patches. I now retry against 21.4.1 with
proper Cc: to xemacs-patches, ChangeLog entries, and more fixes.
If you need a patch to mule.texi over my patch from [20 Apr 2001],
just ask.
Probably more "＠cindex"es are needed in mule.texi, I'm not sure.
2001-05-29 Alexey Mahotkin <alexm(a)hsys.msk.ru>
* coding.el: Tiny typo fixed
* custom.texi: Documented keyboard shortcut.
* mule.texi: Updated to match reality; tiny fixes.
===================================================================
RCS file: custom.texi,v
retrieving revision 1.1
diff -u -r1.1 custom.texi
--- custom.texi 2001/05/29 19:24:00 1.1
+++ custom.texi 2001/05/29 19:24:21
＠＠ -179,7 +179,8 ＠＠
＠findex customize
＠cindex customization buffer
A convenient way to find the user option variables that you want to
-change, and then change them, is with ＠kbd{M-x customize}. This command
+change, and then change them, is with ＠kbd{M-x customize} (or use a
+keyboard shortcut, ＠kbd{C-h C}. This command
creates a ＠dfn{customization buffer} with which you can browse through
the Emacs user options in a logically organized structure, then edit and
set their values. You can also use the customization buffer to save
＠＠ -203,7 +204,7 ＠＠
＠dfn{groups} to help you find them. Groups are collected into bigger
groups, all the way up to a master group called ＠code{Emacs}.
- ＠kbd{M-x customize} creates a customization buffer that shows the
+ ＠kbd{M-x customize} (or ＠kbd{C-h C} creates a customization buffer that shows the
top-level ＠code{Emacs} group and the second-level groups immediately
under it. It looks like this, in part:
===================================================================
RCS file: mule.texi,v
retrieving revision 1.1
diff -u -r1.1 mule.texi
--- mule.texi 2001/05/29 18:13:14 1.1
+++ mule.texi 2001/05/29 19:17:36
＠＠ -13,8 +13,9 ＠＠
＠cindex IPA
＠cindex Japanese
＠cindex Korean
+＠cindex Cyrillic
＠cindex Russian
- If you compile XEmacs with mule option, it supports a wide variety of
+ If you compile XEmacs with Mule option, it supports a wide variety of
world scripts, including Latin script, as well as Arabic script,
Simplified Chinese script (for mainland of China), Traditional Chinese
script (for Taiwan and Hong-Kong), Greek script, Hebrew script, IPA
＠＠ -70,7 +71,7 ＠＠
＠cindex language environments
All supported character sets are supported in XEmacs buffers if it is
-compile with mule; there is no need to select a particular language in
+compiled with Mule; there is no need to select a particular language in
order to display its characters in an XEmacs buffer. However, it is
important to select a ＠dfn{language environment} in order to set various
defaults. The language environment really represents a choice of
＠＠ -89,8 +90,10 ＠＠
the XEmacs session. The supported language environments include:
＠quotation
-Chinese-BIG5, Chinese-CNS, Chinese-GB, Cyrillic-ISO, English, Ethiopic,
-Greek, Japanese, Korean, Latin-1, Latin-2, Latin-3, Latin-4, Latin-5.
+ASCII, Chinese-BIG5, Chinese-GB, Croatian, Cyrillic-ALT, Cyrillic-ISO,
+Cyrillic-KOI8, Cyrillic-Win, Czech, English, Ethiopic, French, German,
+Greek, Hebrew, IPA, Japanese, Korean, Latin-1, Latin-2, Latin-3, Latin-4,
+Latin-5, Norwegian, Polish, Romanian, Slovenian, Thai-XTIS, Vietnamese.
＠end quotation
Some operating systems let you specify the language you are using by
＠＠ -282,11 +285,15 ＠＠
＠item M-x list-coding-systems
Display a list of all the supported coding systems.
+
+＠item C-u M-x list-coding-systems
+Display comprehensive list of specific details of all supported coding
+systems.
＠end table
-＠kindex C-h C
+＠kindex C-x ＠key{RET} C
＠findex describe-coding-system
- The command ＠kbd{C-h C} (＠code{describe-coding-system}) displays
+ The command ＠kbd{C-x RET C} (＠code{describe-coding-system}) displays
information about particular coding systems. You can specify a coding
system name as argument; alternatively, with an empty argument, it
describes the coding systems currently selected for various purposes,
＠＠ -435,7 +442,8 ＠＠
command.
＠item C-x ＠key{RET} k ＠var{coding} ＠key{RET}
-Use coding system ＠var{coding} for keyboard input.
+Use coding system ＠var{coding} for keyboard input. (This feature is
+non-functional and is temporarily disabled.)
＠item C-x ＠key{RET} t ＠var{coding} ＠key{RET}
Use coding system ＠var{coding} for terminal output.
＠＠ -517,6 +525,8 ＠＠
the sequences that are translated are typically sequences of ASCII
printing characters. Coding systems typically translate sequences of
non-graphic characters.
+
+(This feature is non-functional and is temporarily disabled.)
＠kindex C-x RET p
＠findex set-buffer-process-coding-system
===================================================================
RCS file: coding.el,v
retrieving revision 1.1
diff -u -r1.1 coding.el
--- coding.el 2001/05/29 19:31:22 1.1
+++ coding.el 2001/05/29 18:53:38
＠＠ -50,7 +50,7 ＠＠
TARGET-TYPE specifies which of them to modify.
If it is `file', it affects `file-coding-system-alist' (which see).
If it is `process', it affects `process-coding-system-alist' (which see).
-If it is `network', it affects `network-codign-system-alist' (which see).
+If it is `network', it affects `network-coding-system-alist' (which see).
REGEXP is a regular expression matching a target of I/O operation.
The target is a file name if TARGET-TYPE is `file', a program name if
- 2 participants
- 1 comments
Packages installer doesn't work + other weirdiness
24 years
Jani Averbach
Jani Averbach
Hi!
The Problems:
1st Problem
Compiling won't succees without --without-msw because configure try
linking against winspool library. (This is Linux machnine)
2nd Problem
The package autoinstaller won't work:
tools->packages->add download...
tools->packages->List and Install
(1) (error/warning) Error in process filter: (ftp-error FTP Error: DIR
failed: 500 Illegal PORT command.)
and in the menu buffer there is text:
Wrong type argument: stringp, nil
I have tried xemacs.org, and few other local mirros, but the situation is
always same.
3rd Problem
M-x build-report generated following error:
Symbol's function definition is void: mail
I supposed that it will generate a file, witch one I can mail other way,
but it seems that it like the mail the report by itself...
I compiled XEmacs-21.4.3 in Redhat 6.2 machine (intel,
glibc-2.1.3, kernel 2.4.x, XFree 4.0.3, ) with following command:
./configure i686-pc-linux-gnu --with-xpm --with-png --with-jpeg
--with-tiff --without-msw --with-athena=3d
After that I installed
efs-1.22-pkg.tar.gz
xemacs-base-1.53-pkg.tar.gz
as mentioned in the Installation-HOWTO.
But the result was problems listed above.
Any help will be very appreciate.
BR, Jani
---
Jani Averbach
- 8 participants
- 9 comments
BAD: Handling of package-index by package release and install system
24 years
Adrian Aichner
Adrian Aichner
Hello All, Hello Steve,
many of you must be experiencing the same problems.
I had long wanted to write about the breakage I see.
Some Facts:
The package-index file contains
(package-get-update-base-entry (quote ...))
forms.
The file is not meant to be hand-edited:
;; Package Index file -- Do not edit manually.
;;;＠＠＠
(package-get-update-base-entry (quote
...
Building a package adds a
(package-get-update-base-entry (quote ...))
form at the beginning of the package-index file in the staging area.
The Problem:
When a package-index file is read, the last
(package-get-update-base-entry (quote ...))
form for a certain package in that file supercedes earlier ones.
This means that the Package Release Engineer has to fiddle with the
package-index file or remove the package-index file and rebuild all
packages from scratch.
Two Questions:
1. Is it a valuable feature for the package-index file to contain
multiple instances of the same package to provide a building history
of packages? We don't seem to have the interfaces to make use of this
feature today.
2. Shouldn't the latest addition to the package-index file supercede
older definitions?
Has anybody been working on these problems already?
Any suggestions what should be done?
I think item 2 really needs fixing.
Best regards,
Adrian
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
- 7 participants
- 19 comments
Problem with TAGS, but it's probably me.
24 years
Steve Youngs
Steve Youngs
I wanted to find something buried deep within the XEmacs source. So I
decided to try out this "TAGS" thing.
make tags
Tools -> Tags -> Set Tags Table File (set to appropriate file)
Tools -> Tags -> Find Tag
infinite loop (escapable with C-g)
Is it a problem with me, or with XEmacs (21.5-b1)?
--
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |
|------------------------------------<youngs(a)xemacs.org>---|
- 6 participants
- 8 comments