January 2005 - XEmacs-Patches - XEmacs Mailing List Archives

[COMMIT] Announce Package Release 2005-01-18 19 years, 3 months

Norbert Koch

NOTE: This patch has been committed. Hi! New packages for the people to play with. The content file has been committed separately. norbert. ChangeLog addition: 2005-01-19 Norbert Koch <viteno(a)xemacs.org> * index.content: New packages have been released on 2005-01-18. Releases/ChangeLog addition: 2005-01-19 Norbert Koch <viteno(a)xemacs.org> * index.content: * 2005-01-18.content: New packages have been released on 2005-01-18. xemacsweb source patch: Diff command: cvs -f -z3 -q diff -u -N Files affected: Releases/index.content index.content Index: index.content =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacsweb/index.content,v retrieving revision 1.138 diff -u -r1.138 index.content --- index.content 17 Dec 2004 04:04:42 -0000 1.138 +++ index.content 19 Jan 2005 12:18:02 -0000 ＠＠ -97,7 +97,7 ＠＠ <dl>  <dt><a href="">Official</a> Release:</dt> - <dd><a href="Releases/2004-08-18.html">2004-08-18</a></dd> + <dd><a href="Releases/2005-01-18.html">2005-01-18</a></dd> </dl> <h1>XEmacs Community News</h1> Index: Releases/index.content =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Releases/index.content,v retrieving revision 1.94 diff -u -r1.94 index.content --- Releases/index.content 17 Dec 2004 02:03:31 -0000 1.94 +++ Releases/index.content 19 Jan 2005 12:18:02 -0000 ＠＠ -369,6 +369,7 ＠＠ <ul> + <li>2005-01-18: <a href="2005-01-18.html">[2005-01-18 release notice]</a> <a href="2005-01-18.html#changes">[changelogs]</a></li> <li>2004-08-18: <a href="2004-08-18.html">[2004-08-18 release notice]</a> <a href="2004-08-18.html#changes">[changelogs]</a></li> <li>2004-05-17: <a href="2004-05-17.html">[2004-05-17 release notice]</a> <a href="2004-05-17.html#changes">[changelogs]</a></li> <li>2004-02-02: <a href="2004-02-02.html">[2004-02-02 release notice]</a> <a href="2004-02-02.html#changes">[changelogs]</a></li>

1 participants
0 comments

[PATCH] (revised) Make definition of "command" more accessible in Lispref. 19 years, 3 months

Aidan Kehoe

Revised, in response to Stephen’s comments in 878y6qdv8y.fsf(a)tleepslib.sk.tsukuba.ac.jp , to rename the node globally, and to change a couple of “pxref”s to “xref”s. This is in response to a user who managed, quite quickly, to write some useful lisp code, but had real trouble finding out about the (interactive) declaration. The comp.emacs.xemacs thread starts at http://google.ie/groups?selm=1105972348.239860.235850＠c13g2000cwb.googleg... man/ChangeLog addition: 2005-01-19 Aidan Kehoe <kehoea(a)parhasard.net> * man/lispref/functions.texi (Functions): Rename to "Functions and Commands" * man/lispref/functions.texi (What Is a Function): Move the definition of a command further up the list, give information on a trivial (interactive) declaration, and cross-reference to the key binding detail. Cf. 87vf9wgd08.fsf(a)tleepslib.sk.tsukuba.ac.jp (comp.emacs.xemacs, 2005-01-18). * man/lispref/eval.texi man/lispref/lispref.texi man/lispref/macros.texi man/lispref/mule.texi man/lispref/symbols.texi man/lispref/variables.texi: Fix cross references XEmacs Current source patch: Diff command: cvs -q diff -u Files affected: man/lispref/eval.texi man/lispref/functions.texi man/lispref/lispref.texi man/lispref/macros.texi man/lispref/mule.texi man/lispref/symbols.texi man/lispref/variables.texi Index: man/lispref/eval.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/eval.texi,v retrieving revision 1.5 diff -u -r1.5 eval.texi --- man/lispref/eval.texi 2001/04/12 18:22:13 1.5 +++ man/lispref/eval.texi 2005/01/19 10:40:00 ＠＠ -74,7 +74,7 ＠＠ function ＠code{car}. Evaluation of a function call ultimately calls the function specified -in it. ＠xref{Functions}. The execution of the function may itself work +in it. ＠xref{Functions and Commands}. The execution of the function may itself work by evaluating the function definition; or the function may be a Lisp primitive implemented in C, or it may be a byte-compiled function (＠pxref{Byte Compilation}). Index: man/lispref/functions.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/functions.texi,v retrieving revision 1.2 diff -u -r1.2 functions.texi --- man/lispref/functions.texi 2001/04/12 18:22:14 1.2 +++ man/lispref/functions.texi 2005/01/19 10:40:03 ＠＠ -3,8 +3,8 ＠＠＠c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. ＠c See the file lispref.texi for copying conditions. ＠setfilename ../../info/functions.info -＠node Functions, Macros, Variables, Top -＠chapter Functions +＠node Functions and Commands, Macros, Variables, Top +＠chapter Functions and Commands A Lisp program is composed mainly of Lisp functions. This chapter explains what functions are, how they accept arguments, and how to ＠＠ -45,6 +45,39 ＠＠ specifically to mean a function written in Lisp. Special forms and macros are not functions. +＠item command +＠cindex command + +A ＠dfn{command} is a possible definition for a key sequence---we count +mouse events and menu accesses as key sequences for this purpose. More +formally, within XEmacs lisp, a command is something that +＠code{command-execute} can invoke. + +Some functions are commands; a function written in Lisp is a command if +it contains an interactive declaration. A trivial interactive +declaration is a line ＠code{(interactive)} immediately after the +documentation string. For more complex examples, with prompting and +completion, see ＠xref{Defining Commands}. Such a function can be called +from Lisp expressions like other functions; in this case, the fact that +the function is a command makes no difference. + +Keyboard macros (strings and vectors) are commands also, even though +they are not functions. A symbol is a command if its function +definition is a command; such symbols can be invoked with ＠kbd{M-x}. +The symbol is a function as well if the definition is a function. + +In the case where you want to call a command in reaction to a +user-generated event, you'll need to bind it to that event. For how to +do this, see ＠xref{Key Binding Commands}. +＠xref{Command Overview}. + +＠item keystroke command +＠cindex keystroke command +A ＠dfn{keystroke command} is a command that is bound to a key sequence +(typically one to three keystrokes). The distinction is made here +merely to avoid confusion with the meaning of ``command'' in non-Emacs +editors; for Lisp programs, the distinction is normally unimportant. + ＠item primitive ＠cindex primitive ＠cindex subr ＠＠ -83,28 +116,6 ＠＠ original expression. Macros enable Lisp programmers to do the sorts of things that special forms can do. ＠xref{Macros}, for how to define and use macros. - -＠item command -＠cindex command -A ＠dfn{command} is an object that ＠code{command-execute} can invoke; it -is a possible definition for a key sequence. Some functions are -commands; a function written in Lisp is a command if it contains an -interactive declaration (＠pxref{Defining Commands}). Such a function -can be called from Lisp expressions like other functions; in this case, -the fact that the function is a command makes no difference. - -Keyboard macros (strings and vectors) are commands also, even though -they are not functions. A symbol is a command if its function -definition is a command; such symbols can be invoked with ＠kbd{M-x}. -The symbol is a function as well if the definition is a function. -＠xref{Command Overview}. - -＠item keystroke command -＠cindex keystroke command -A ＠dfn{keystroke command} is a command that is bound to a key sequence -(typically one to three keystrokes). The distinction is made here -merely to avoid confusion with the meaning of ``command'' in non-Emacs -editors; for Lisp programs, the distinction is normally unimportant. ＠item compiled function A ＠dfn{compiled function} is a function that has been compiled by the Index: man/lispref/lispref.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/lispref.texi,v retrieving revision 1.20 diff -u -r1.20 lispref.texi --- man/lispref/lispref.texi 2004/07/19 08:24:28 1.20 +++ man/lispref/lispref.texi 2005/01/19 10:40:06 ＠＠ -144,8 +144,10 ＠＠ * Evaluation:: How Lisp expressions are evaluated. * Control Structures:: Conditionals, loops, nonlocal exits. * Variables:: Using symbols in programs to stand for values. -* Functions:: A function is a Lisp program - that can be invoked from other functions. + +* Functions and Commands:: A function is a Lisp program that can be + invoked from other functions. + * Macros:: Macros are a way to extend the Lisp language. * Customization:: Writing customization declarations. Index: man/lispref/macros.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/macros.texi,v retrieving revision 1.2 diff -u -r1.2 macros.texi --- man/lispref/macros.texi 2001/04/12 18:22:17 1.2 +++ man/lispref/macros.texi 2005/01/19 10:40:06 ＠＠ -3,7 +3,7 ＠＠＠c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. ＠c See the file lispref.texi for copying conditions. ＠setfilename ../../info/macros.info -＠node Macros, Loading, Functions, Top +＠node Macros, Loading, Functions and Commands, Top ＠chapter Macros ＠cindex macros Index: man/lispref/mule.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/mule.texi,v retrieving revision 1.11 diff -u -r1.11 mule.texi --- man/lispref/mule.texi 2004/11/04 23:06:07 1.11 +++ man/lispref/mule.texi 2005/01/19 10:40:08 ＠＠ -2056,7 +2056,23 ＠＠＠comment Node, Next, Previous, Up ＠subsection CCL Examples - This section is not yet written. +CCL isn't an especially nice language to program in, compared to Emacs +lisp, but writing coding systems in it is a huge improvement in +stability and convenience over writing them in XEmacs' C core, which is +the alternative. So for that reason, it's worth learning, should you +need or want to transform data with in the coding system framework. + +This section describes the implementation, in CCL, of a coding system to +transform from the standard GSM coding system, as used for SMS text +messages in your mobile phone, to XEmacs' internal format. (Yes, for the +detail-oriented among you, if you're in East Asia you probably send SMS +messages using UCS-2. But, if you're in East Asia, you're more likely to +be sending email from your phone than text messages anyway.) + +The GSM coding system is a seven-bit, packed, variable length +encoding. This means that characters + + ＠node Category Tables, Unicode Support, CCL, MULE ＠section Category Tables Index: man/lispref/symbols.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/symbols.texi,v retrieving revision 1.4 diff -u -r1.4 symbols.texi --- man/lispref/symbols.texi 2001/04/12 18:22:21 1.4 +++ man/lispref/symbols.texi 2005/01/19 10:40:09 ＠＠ -11,8 +11,8 ＠＠ describes symbols, their components, their property lists, and how they are created and interned. Separate chapters describe the use of symbols as variables and as function names; see ＠ref{Variables}, and -＠ref{Functions}. For the precise read syntax for symbols, see -＠ref{Symbol Type}. +＠ref{Functions and Commands}. For the precise read syntax for symbols, +see ＠ref{Symbol Type}. You can test whether an arbitrary Lisp object is a symbol with ＠code{symbolp}: ＠＠ -154,7 +154,7 ＠＠ cell, is derived from the idea that ＠code{defun} gives the symbol its definition as a function.) ＠code{defsubst}, ＠code{define-function} and ＠code{defalias} are other ways of defining a function. -＠xref{Functions}. +＠xref{Functions and Commands}. ＠code{defmacro} defines a symbol as a macro. It creates a macro object and stores it in the function cell of the symbol. Note that a Index: man/lispref/variables.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/variables.texi,v retrieving revision 1.6 diff -u -r1.6 variables.texi --- man/lispref/variables.texi 2002/10/02 09:30:52 1.6 +++ man/lispref/variables.texi 2005/01/19 10:40:09 ＠＠ -3,7 +3,7 ＠＠＠c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. ＠c See the file lispref.texi for copying conditions. ＠setfilename ../../info/variables.info -＠node Variables, Functions, Control Structures, Top +＠node Variables, Functions and Commands, Control Structures, Top ＠chapter Variables ＠cindex variable ＠＠ -225,7 +225,7 ＠＠＠itemize ＠bullet ＠item -Function calls (＠pxref{Functions}). +Function calls (＠pxref{Functions and Commands}). ＠item Macro calls (＠pxref{Macros}). -- “Ah come on now Ted, a Volkswagen with a mind of its own, driving all over the place and going mad, if that’s not scary I don’t know what is.”

1 participants
1 comments

[CORE (21.4)] "clever" compilers sometimes opt away too much. 19 years, 3 months

Steve Youngs

Sorry, haven't checked 21.5, but I'd imagine this is needed there too. 21.4 patch: ChangeLog files diff command: cvs -q diff -U 0 Files affected: src/ChangeLog Source files diff command: cvs -q diff -uN Files affected: src/emacs.c Index: src/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v retrieving revision 1.290.2.83 diff -u -U0 -r1.290.2.83 ChangeLog --- src/ChangeLog 11 Jan 2005 02:02:11 -0000 1.290.2.83 +++ src/ChangeLog 12 Jan 2005 01:11:36 -0000 ＠＠ -0,0 +1,7 ＠＠ +2005-01-12 Steve Youngs <steve(a)sxemacs.org> + + From Evgeny Zajcev <lg(a)sxemacs.org>: + + * emacs.c (debug_can_access_memory): Fix problem of "clever" + compilers being over-zealous in their optimising. + Index: src/emacs.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/emacs.c,v retrieving revision 1.97.2.8 diff -u -u -r1.97.2.8 emacs.c --- src/emacs.c 13 Jun 2004 20:19:39 -0000 1.97.2.8 +++ src/emacs.c 12 Jan 2005 01:10:26 -0000 ＠＠ -535,15 +535,13 ＠＠ old_sigsegv = (SIGTYPE (*) (int)) signal (SIGSEGV, debug_memory_error); - if (len > 1) - /* If we can, try to avoid problems with super-optimizing compilers - that might decide that memcmp (ptr, ptr, len) can be optimized - away since its result is always 1. */ - memcmp (ptr, (char *) ptr + 1, len - 1); - else - memcmp (ptr, ptr, len); - } - else + /* Examine memory pool at PTR */ + while (len-- > 0) { + char a = ((char*)ptr)[len]; + if (a == '1') + /* pass */; + } + } else retval = 0; signal (SIGBUS, old_sigbus); signal (SIGSEGV, old_sigsegv); -- |---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---| | In space, | | No one can hear you rip a stinky | |------------------------------------<steve(a)sxemacs.org>---|

5 participants
7 comments

[PATCH] Make the definition of what a command is more accessible in Lispref. 19 years, 3 months

Aidan Kehoe

This is in response to a user who managed, quite quickly, to write some useful lisp code, but had real trouble finding out about the (interactive) declaration. The comp.emacs.xemacs thread starts at http://google.ie/groups?selm=1105972348.239860.235850＠c13g2000cwb.googleg... man/ChangeLog addition: 2005-01-18 Aidan Kehoe <kehoea(a)parhasard.net> * lispref/functions.texi (Functions): Rename to "Functions and Commands" * lispref/functions.texi (What Is a Function): Move the definition of a command further up the list, give information on a trivial (interactive) declaration, and cross-reference to the key binding detail. Cf. 87vf9wgd08.fsf(a)tleepslib.sk.tsukuba.ac.jp (comp.emacs.xemacs, 2005-01-18). XEmacs Current source patch: Diff command: cvs -q diff -u Files affected: man/lispref/functions.texi Index: man/lispref/functions.texi =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/man/lispref/functions.texi,v retrieving revision 1.2 diff -u -r1.2 functions.texi --- man/lispref/functions.texi 2001/04/12 18:22:14 1.2 +++ man/lispref/functions.texi 2005/01/18 23:20:30 ＠＠ -4,7 +4,7 ＠＠＠c See the file lispref.texi for copying conditions. ＠setfilename ../../info/functions.info ＠node Functions, Macros, Variables, Top -＠chapter Functions +＠chapter Functions and Commands A Lisp program is composed mainly of Lisp functions. This chapter explains what functions are, how they accept arguments, and how to ＠＠ -45,6 +45,39 ＠＠ specifically to mean a function written in Lisp. Special forms and macros are not functions. +＠item command +＠cindex command + +A ＠dfn{command} is a possible definition for a key sequence---we count +mouse events and menu accesses as key sequences for this purpose. More +formally, within XEmacs lisp, a command is something that +＠code{command-execute} can invoke. + +Some functions are commands; a function written in Lisp is a command if +it contains an interactive declaration. A trivial interactive +declaration is a line ＠code{(interactive)} immediately after the +documentation string. For more complex examples, with prompting and +completion, see ＠pxref{Defining Commands}. Such a function can be called +from Lisp expressions like other functions; in this case, the fact that +the function is a command makes no difference. + +Keyboard macros (strings and vectors) are commands also, even though +they are not functions. A symbol is a command if its function +definition is a command; such symbols can be invoked with ＠kbd{M-x}. +The symbol is a function as well if the definition is a function. + +In the case where you want to call a command in reaction to a +user-generated event, you'll need to bind it to that event. For how to +do this, see ＠pxref{Key Binding Commands}. +＠xref{Command Overview}. + +＠item keystroke command +＠cindex keystroke command +A ＠dfn{keystroke command} is a command that is bound to a key sequence +(typically one to three keystrokes). The distinction is made here +merely to avoid confusion with the meaning of ``command'' in non-Emacs +editors; for Lisp programs, the distinction is normally unimportant. + ＠item primitive ＠cindex primitive ＠cindex subr ＠＠ -83,28 +116,6 ＠＠ original expression. Macros enable Lisp programmers to do the sorts of things that special forms can do. ＠xref{Macros}, for how to define and use macros. - -＠item command -＠cindex command -A ＠dfn{command} is an object that ＠code{command-execute} can invoke; it -is a possible definition for a key sequence. Some functions are -commands; a function written in Lisp is a command if it contains an -interactive declaration (＠pxref{Defining Commands}). Such a function -can be called from Lisp expressions like other functions; in this case, -the fact that the function is a command makes no difference. - -Keyboard macros (strings and vectors) are commands also, even though -they are not functions. A symbol is a command if its function -definition is a command; such symbols can be invoked with ＠kbd{M-x}. -The symbol is a function as well if the definition is a function. -＠xref{Command Overview}. - -＠item keystroke command -＠cindex keystroke command -A ＠dfn{keystroke command} is a command that is bound to a key sequence -(typically one to three keystrokes). The distinction is made here -merely to avoid confusion with the meaning of ``command'' in non-Emacs -editors; for Lisp programs, the distinction is normally unimportant. ＠item compiled function A ＠dfn{compiled function} is a function that has been compiled by the -- “Ah come on now Ted, a Volkswagen with a mind of its own, driving all over the place and going mad, if that’s not scary I don’t know what is.”

2 participants
1 comments

eBay Help 19 years, 3 months

HotWebsites.us

A cool online audio tour that will teach you to sell on eBay is located at http://pages.ebay.com/education/howtosell/index.html You can create an eBay Seller's Account at http://cgi4.ebay.com/ws/eBayISAPI.dll?SellerSignIn. If you don't have a credit card, establish your proof of identity with ID Verify at http://pages.ebay.com/services/buyandsell/idverify-login.html. You can get ID Verified without putting your credit card on file for only $5. ---------- Different Selling Formats: Online Auction This is classic eBay. Collect bids on your item and sell to the highest bidder in a fixed length of time. You may also include a Buy It Now price in your auction, which disappears after the first bid. Quantity: Offer bidding on one or multiple items. Where: Your listing appears in the eBay category (or categories) you choose and in search results. Fixed Price You set the price for your item or items, so buyers can purchase immediately (no bidding). Quantity: Offer one or multiple items for sale at the Buy It Now price anytime during the listing. Where: Your listing appears in the eBay category (or categories) you choose and in search results. Store Inventory Buyers can purchase the item immediately from your eBay Store at a set price (no bidding or waiting!). Quantity: Offer one or multiple items for one Buy It Now price. You must open an eBay Store to use this format. Where: Your Store Inventory items appear only within your eBay Store, but your eBay Store is promoted from your other listings. Duration: 30, 60, 90, and 120 days. Also available in the Good 'Til Cancelled duration--the listing will automatically renew every 30-days until you end it or all the inventory is sold. ---------- Some tips from http://pages.ebay.com/help/sell/checklist.html Register for selling-related services. Make your selling process easier by registering for additional services before you begin the Sell Your Item form. If you want to sell in the Mature Audiences section, now would be a good time to go through the ID Verify process. If you want to sell through your own eBay Store, open one now. Plan your item title. Give some thought to naming your item. What will buyers most want to know about it? What are its most appealing characteristics? What words might buyers use to search for your item? Choose your eBay category (or categories). The right category helps interested buyers find your item. Search for items similar to yours and see which categories other sellers have chosen. You can also use the eBay Suggested Categories feature to have eBay suggest categories for you. For an additional fee, you can list your item in a second category to maximize your item's visibility. Choose the most specific category available. This will help buyers find your item. As eBay is a global community with members from every corner of the world, you will need to decide on where you are comfortable and able to sell your item, as well as determine who you would like to bid on your item. We recommend selling internationally and allowing bids from any country in the world. Offer PayPal as a payment method. ---------- And when your listing ends... Communicate with your buyer Using eBay's Checkout service? When your buyer has completed Checkout, eBay will notify you by email. You can also use Checkout to send the buyer an invoice. All websites will be delivered instantly online. If you selected not to use Checkout, you should contact the buyer directly using email or phone. Important: You should contact the buyer directly if you have not heard from the buyer or the buyer has not completed Checkout within 24 hours of your listing's end. Receive payment If the buyer paid with PayPal, you will receive an email confirming payment. If you have not yet registered for the PayPal service, you will be asked to register to accept the payment. Ship the item to the buyer Simply log in to your affiliate account at http://66.34.230.9/login.php and place your wholesale order for the correct website. The website will be transfered into the new owner's name and they will receive a welcome email with all required information. Leave the buyer feedback eBay's feedback system helps create a trustworthy community for everyone. Your feedback about your buyer is important information for other sellers! If you are not yet an authorized reseller today is the perfect time for you to get started. Please log in to your member account at http://66.34.230.9/login.php and click on the "Sell our websites" Help Pages link. You should also check out the "Sell using online auctions" and "Selling on eBay.com" pages. These pages will give you almost all of the information you need regarding reselling our websites and they will also get you started with the online auctions. Also remember to email us so that we can add your information to our list of authorized resellers. If you have any specific questions after reading this information please ask and we will do everything possible to assist you :) http://66.34.230.9/login.php username= xemacspatches password= 208871 You are receiving this email because you are a member of HotWebsites.us. If you would like to change your email preferences please contact customer service at Help(a)HotWebsites.us

1 participants
0 comments

[A21.5R21.4] [C] xemacs-21.5: Fix shifted-motion-keys-select-region docstring 19 years, 3 months

Adrian Aichner

COMMIT APPROVE 21.5 RECOMMEND 21.4 Outcome of discussion in Message-ID: <4qhjlkx6.fsf(a)smtpmail.t-online.de> Vin, could you please apply this to 21.4. Best regards, Adrian xemacs-21.5 ChangeLog patch: Diff command: cvs -q diff -U 0 Files affected: lisp/ChangeLog Index: lisp/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/ChangeLog,v retrieving revision 1.607 diff -u -U0 -r1.607 ChangeLog --- lisp/ChangeLog 9 Jan 2005 14:22:08 -0000 1.607 +++ lisp/ChangeLog 17 Jan 2005 11:16:42 -0000 ＠＠ -0,0 +1,5 ＠＠ +2005-01-17 Adrian Aichner <adrian(a)xemacs.org> + + * simple.el (shifted-motion-keys-select-region): Fix statement + about unshifted-motion-keys-deselect-region. + xemacs-21.5 source patch: Diff command: cvs -f -z3 -q diff -u -w -N Files affected: lisp/simple.el Index: lisp/simple.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/simple.el,v retrieving revision 1.48 diff -u -w -r1.48 simple.el --- lisp/simple.el 14 Dec 2004 10:09:08 -0000 1.48 +++ lisp/simple.el 17 Jan 2005 11:12:01 -0000 ＠＠ -1979,7 +1979,7 ＠＠ When the region has been enabled or augmented as a result of a shifted motion key, an unshifted motion key will normally deselect the region. -However, if `unshifted-motion-keys-deselect-region' is t, the region +However, if `unshifted-motion-keys-deselect-region' is nil, the region will remain active, augmented by the characters moved over by this motion key. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
1 comments

[AC21.5R21.4] AltGr/iso-level3-shift not defined/I-search breakage 19 years, 3 months

Stephen J. Turnbull

APPROVE COMMIT 21.5 RECOMMEND 21.4 Ville, thanks for snuffling this out. Malcolm, there may be a similar problem in event-gtk.h; I don't understand GTK well enough to guess. I don't recall such reports for GTK builds, but they're not as common as Xt builds so that may not mean much. Ville, would you be able to check whether this occurs with a GTK build, with and without your patch? 2005-01-12 Ville Skyttä <scop(a)xemacs.org> * console-x.h: #include X11/keysym.h before xintrinsic.h. >>>>> "Ville" == Ville Skyttä <scop(a)xemacs.org> writes: Ville> When pressing AltGr in XEmacs 21.4.1[56] on my Fedora Core Ville> 3 box (Mule, Finnish X keymap, x.org X11 6.8.1), an error Ville> is signaled: Ville> iso-level3-shift is not defined Ville> Additionally, pressing AltGr quits I-search, which is very Ville> annoying. GNU Emacs suffers from the same I-search Ville> problem, but does not display any errors. Ville> I Googled and found some workaround suggestions like: Ville> (define-key global-map [(iso-level3-shift)] '#ignore) Ville> This "works" in the sense that the error message goes away; Ville> however it does not help with the I-search problem which is Ville> the important one. Ville> But when discussing this in Red Hat Bugzilla, these were Ville> found: Ville> Apparent root cause: Ville> https://bugs.freedesktop.org/show_bug.cgi?id=1625 Ville> The workaround applied in GNU Emacs: Ville> http://lists.gnu.org/archive/html/bug-gnu-emacs/2004-10/msg00150.html Ville> Attached is a workaround patch for XEmacs 21.4.16 which Ville> fixes the problem for me (probably applicable to 21.5 too). Ville> Could someone review whether this patch is worth applying Ville> in XEmacs? Or maybe <X11/keysym.h> should be included in Ville> xintrinsic.h before <X11/Intrinsic.h> instead for Ville> completeness? The patch is at worst harmless unless somebody is doing something _really_ evil with keysym definitions. It should be applied. It only matters when both keysym.h and Xutil.h are being _used_. There are some instances where Xutil is #include'd, plus there's the GTK code. I think it's probably better to explicitly move the include for keysym.h in the files where it is used rather than put it in xintrinsic.h. Here's a slightly improved patch (I just love to read my own writing ;-) and a ChangeLog. 2005-01-12 Ville Skyttä <scop(a)xemacs.org> * console-x.h: #include X11/keysym.h before xintrinsic.h. Index: src/console-x.h =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/console-x.h,v retrieving revision 1.12 diff -u -r1.12 console-x.h --- src/console-x.h 12 Apr 2001 18:23:30 -0000 1.12 +++ src/console-x.h 17 Jan 2005 09:21:32 -0000 ＠＠ -35,10 +35,13 ＠＠ #ifdef HAVE_X_WINDOWS #include "console.h" +/* must come before Xutil.h, which is included indirectly from xintrinsic.h, + to avoid breakage in keysym-parsing macros from X11R6, at least X.org as + of 2005-01-17, and probably XFree86 too from reports on c.e.x */ +#include <X11/keysym.h> #include "xintrinsic.h" #include <X11/cursorfont.h> -#include <X11/keysym.h> #include <X11/Xatom.h> #include

3 participants
2 comments

[PATCH] Rework the XFT branch to use the FcCharSet functions. 19 years, 3 months

Aidan Kehoe

This uses XFT's native font character-coverage API when looking up a font to use for a given character set. Stephen had some doubts about using this, and I think they're worth revisiting when we have a decent language-tagging infrastructure in place within XEmacs, but for the moment, they give, effectively, equivalent functionality to what we have under native X11 without major acrobatics. I've also omitted the CCL charset translation when XFT is in place; I quote from the comment beside this: /* There's no need to special-case charsets that use CCL conversion here. XFT gives us access to a _unified_ character set, so _there is no difference_ between a Windows 1251 CYRILLIC CAPITAL LETTER ES and an ISO 8859-5 CYRILLIC CAPITAL LETTER ES, because they both map to the same code point in the UCS. If there were any indication that the Mule charset CCL conversion were used for some other purpose than something orthogonal to the iso-8859-5 --> non-ISO-2022 conversion, there would be grounds for reconsidering this. */ Also, don't abort when we don't get a good Unicode translation for a character. We don't enforce that every character set has to have a Unicode translation at the moment. Stephen, did you load etc/HELLO with your previous patch at all? :-) (Note, I’m not applying this, nor considering doing so. If you’ve written this functionality already, Stephen, that’s cool.) src/ChangeLog addition: 2005-01-17 Aidan Kehoe <kehoea(a)parhasard.net> * charset.h: Include a fontconfig header file, declare fc_charset_from_mule_charset. * objects-x.c (x_find_charset_font): Call fc_charset_from_mule_charset, use its result when looking up the XFT font to use for a given Mule charset. * redisplay-x.c (separate_textual_runs): Abort less on interesting Mule character sets. * unicode.c (fc_charset_from_mule_charset): Added. Uses a static array of length NUM_LEADING_BYTES to cache the Mule charsets' FcCharSet objects. xemacs-sjt-xft source patch: Diff command: cvs -q diff -u Files affected: src/unicode.c src/redisplay-x.c src/objects-x.c src/charset.h Index: src/charset.h =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/charset.h,v retrieving revision 1.9 diff -u -r1.9 charset.h --- src/charset.h 2004/11/04 23:06:16 1.9 +++ src/charset.h 2005/01/17 23:13:15 ＠＠ -549,4 +549,12 ＠＠ #endif /* MULE */ +#ifdef USE_XFT + +#include <fontconfig/fontconfig.h> + +FcCharSet *fc_charset_from_mule_charset(Lisp_Object charset); + +#endif /* USE_XFT */ + #endif /* INCLUDED_charset_h_ */ Index: src/objects-x.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/objects-x.c,v retrieving revision 1.26.2.5 diff -u -r1.26.2.5 objects-x.c --- src/objects-x.c 2004/12/11 05:16:25 1.26.2.5 +++ src/objects-x.c 2005/01/17 23:13:20 ＠＠ -1035,11 +1035,46 ＠＠ and FcInitBringUpToDate() here? */ { FcChar8 *lang = "en"; + FcCharSet *fccharset = NULL; fcc = FcConfigGetCurrent (); patternxft = FcNameParse (patternext); + + if (debug_xft > 0) + { + stderr_out ("finding a charset font for mule charset id %i\n", + XCHARSET_ID(charset)); + } + + fccharset = fc_charset_from_mule_charset(charset); + if (NULL != fccharset) + { + if (debug_xft > 0) + { + stderr_out ("got a result from fc_charset_from_mule_charset, " + "it's %p", fccharset); + } + FcPatternAddCharSet(patternxft, FC_CHARSET, fccharset); + } + else + { + if (debug_xft > 0) + { + stderr_out ("Got NULL from fc_charset_from_mule_charset--does " + "this Mule charset have a Unicode mapping table at" + " all?"); + } + } + /* #### Next four return FcBool, but what does the return mean? */ /* #### There's probably a way to do this with FcCharsets, but isn't - the language approach better in the long run? */ + the language approach better in the long run? + + It's certainly better in the long run, but that would involve me + finishing the UCS-as-the-internal-coding code, and the + infrastructure for passing up language information from a coding + system. So, stick with the FcCharSet approach until that's in + place. -- aidan, 2005-01-17 */ + /* #### can we regression test this, or does it break too early? */ if (debug_xft > 0) stderr_out ("FcNameParse'ed name is %s\n", ＠＠ -1048,32 +1083,11 ＠＠ if (debug_xft > 0) stderr_out ("FcConfigSubstitute'ed name is %s\n", FcNameUnparse (patternxft)); + FcDefaultSubstitute (patternxft); if (debug_xft > 0) stderr_out ("FcDefaultSubstitute'ed name is %s\n", FcNameUnparse (patternxft)); - if (EQ (charset, Fget_charset (intern ("katakana-jisx0201"))) - || EQ (charset, Fget_charset (intern ("japanese-jisx0208"))) - || EQ (charset, Fget_charset (intern ("japanese-jisx0212")))) - { - if (debug_xft > 0) - stderr_out ("checking if %s handles Japanese\n", patternext); - lang = "ja"; - } - else if (EQ (charset, Fget_charset (intern ("ascii")))) - { - if (debug_xft > 0) - stderr_out ("checking if %s handles English\n", patternext); - lang = "en"; - } - else - { - /* #### is this the right way to make a warning? */ - warn_when_safe_lispobj (intern ("xft"), Qwarning, - list2 (build_string ("unknown charset"), - charset)); - /* default to "en" */ - } patternxft = FcFontMatch (fcc, patternxft, &fcresult); /* #### stderr_out crashed in the next block; why? Index: src/redisplay-x.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/redisplay-x.c,v retrieving revision 1.39.2.2 diff -u -r1.39.2.2 redisplay-x.c --- src/redisplay-x.c 2004/12/10 06:43:50 1.39.2.2 +++ src/redisplay-x.c 2005/01/17 23:13:26 ＠＠ -172,7 +172,7 ＠＠ MULE is not defined */ int runs_so_far = 0; int i; -#ifdef MULE +#if defined(MULE) && !defined(USE_XFT) struct ccl_program char_converter; int need_ccl_conversion = 0; #endif ＠＠ -209,13 +209,15 ＠＠ runs_so_far++; prev_charset = charset; #ifdef MULE +#ifndef USE_XFT { Lisp_Object ccl_prog = XCHARSET_CCL_PROGRAM (charset); if ((!NILP (ccl_prog)) && (setup_ccl_program (&char_converter, ccl_prog) >= 0)) need_ccl_conversion = 1; } -#endif +#endif /* !USE_XFT */ +#endif /* MULE */ } #ifndef USE_XFT ＠＠ -255,10 +257,33 ＠＠ XftChar16 xftchar16 = 0xFFFD; /* unsigned short */ int unicode = ichar_to_unicode (ch); if (unicode < 0) - abort(); /* #### serious error, tables are corrupt */ + { + /* abort(); */ /* #### serious error, tables are corrupt + + Umm, Not necessarily, a charset exists without + a Unicode mapping table, that's not the end of + the world. */ + + unicode = 0xFFFD; + } +#if 0 + /* There's no need to special-case charsets that use CCL conversion + here. XFT gives us access to a _unified_ character set, so _there + is no difference_ between a Windows 1251 CYRILLIC CAPITAL LETTER + ES and an ISO 8859-5 CYRILLIC CAPITAL LETTER ES, because they + both map to the same code point in the UCS. + + If there were any indication that the Mule charset CCL conversion + were used for some other purpose than something orthogonal to the + iso-8859-5 --> non-ISO-2022 conversion, there would be grounds + for reconsidering this. */ + else if (need_ccl_conversion) - /* #### maybe we should just ignore this and hope the font wins? */ - unicode = 0xFFFD; /* REPLACEMENT CHARACTER, can't represent */ + { + /* #### maybe we should just ignore this and hope the font wins? */ + unicode = 0xFFFD; /* REPLACEMENT CHARACTER, can't represent */ + } +#endif else if (unicode > 65535) unicode = 0xFFFD; /* REPLACEMENT CHARACTER, can't represent */ else Index: src/unicode.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/unicode.c,v retrieving revision 1.23 diff -u -r1.23 unicode.c --- src/unicode.c 2004/11/04 23:06:58 1.23 +++ src/unicode.c 2005/01/17 23:13:33 ＠＠ -2385,6 +2385,102 ＠＠ return 0; #endif } +#ifdef USE_XFT + +extern int debug_xft; + +/* Making the FcCharSet objects available to Lisp would just be mad. So, + this array isn't available to it. */ + +FcCharSet *leading_byte_to_fc_charset[NUM_LEADING_BYTES]; + +#define XFT_DEBUG_DUMP(...) do { \ + if (debug_xft > 0) { stderr_out(__VA_ARGS__); }} while (0) +#define XFT_ASSERT(ARG) assert(ARG) + +FcCharSet * +fc_charset_from_mule_charset(Lisp_Object charset) +{ + FcCharSet *fc_charset; + FcBool fcadd_ret; + + int cache_table_index, charset_dim, i, j, + **to_unicode_branch, *to_unicode_leaf; + + void *to_unicode_table; + + XFT_DEBUG_DUMP("mule Charset is %p, doing a fontconfig lookup\n", + (void *)charset); + + if (NULL == (void *)charset) + { + XFT_DEBUG_DUMP("charset was null, returning null\n"); + return NULL; + } + + cache_table_index = XCHARSET_LEADING_BYTE(charset) - MIN_LEADING_BYTE; + charset_dim = XCHARSET_DIMENSION(charset); + + if (NULL != leading_byte_to_fc_charset[cache_table_index]) + { + XFT_DEBUG_DUMP("succeeded looking up charset, %p, id %d\n", + (void *)charset, cache_table_index + MIN_LEADING_BYTE); + /* We got a cache hit--cool, pass it up. */ + return leading_byte_to_fc_charset[cache_table_index]; + } + + /* Pull the mapping to unicode from the character set. */ + to_unicode_table = XCHARSET_TO_UNICODE_TABLE(charset); + if (NULL == to_unicode_table || + (1 == charset_dim && to_unicode_blank_1 == (int *)to_unicode_table) || + (2 == charset_dim && to_unicode_blank_2 == (int **)to_unicode_table)) + { + XFT_DEBUG_DUMP("unicode table was null, or blank. returning null."); + return NULL; + } + + fc_charset = FcCharSetCreate(); + XFT_ASSERT(fc_charset); + + if (1 == charset_dim) + { + to_unicode_leaf = to_unicode_table; + for (i = 0; i < 96; ++i) + { + if (-1 != to_unicode_leaf[i]) + { + fcadd_ret = FcCharSetAddChar(fc_charset, to_unicode_leaf[i]); + XFT_ASSERT(fcadd_ret); + } + } + XFT_DEBUG_DUMP("1-dimensional charset, made FcCharSet, returning it"); + return leading_byte_to_fc_charset[cache_table_index] = fc_charset; + } + + XFT_ASSERT(2 == charset_dim); + + to_unicode_branch = to_unicode_table; + + for (j = 0; j < 96; ++j) + { + to_unicode_leaf = to_unicode_branch[j]; + if (to_unicode_blank_1 != to_unicode_leaf) + { + for (i = 0; i < 96; ++i) + { + if (-1 != to_unicode_leaf[i]) + { + fcadd_ret = FcCharSetAddChar(fc_charset, to_unicode_leaf[i]); + XFT_ASSERT(fcadd_ret); + } + } + } + } + XFT_DEBUG_DUMP("Two dimensional charset, made FcCharSet, returning it."); + return leading_byte_to_fc_charset[cache_table_index] = fc_charset; +} + +#endif /* USE_XFT */ /************************************************************************/ -- “Ah come on now Ted, a Volkswagen with a mind of its own, driving all over the place and going mad, if that’s not scary I don’t know what is.”

1 participants
0 comments

Re: [AC21.5R21.4] Fix warning warning 19 years, 3 months

Vin Shelton

"Stephen J. Turnbull" <stephen(a)xemacs.org> writes: > APPROVE COMMIT 21.5 > > Vin: I think this is OK for 21.4, but maybe you should check with > Jerry. > >>>>>> "sjt" == Stephen J Turnbull <stephen(a)xemacs.org> writes: > > sjt> I think this just requires tinkering with the autoconf > sjt> scripts in ./modules. I'll try to get to it later: > > sjt> cd ./modules/postgresql && make all cc1plus: warning: > sjt> "-Wmissing-declarations" is valid for C/ObjC but not for > sjt> C++ cc1plus: warning: "-Wmissing-declarations" is valid for > sjt> C/ObjC but not for C++ > > Turns out this is something I've wondered about for a while and never > did track down. I had an old patch, discussed with Jerry but never > committed, to fix the C++ flags in modules. It needed a little > something more. Here's the whole thing: > Jerry, Is there any reason I should not apply this patch to 21.4.17? Thanks, VIn

2 participants
1 comments

Dear , please check this out immediately 19 years, 3 months

Global Power Team

Dear, please check this out immediately. I just aligned myself with the Global Power Team. They have developed a way to build a reliable income of over $9,000 per month in as little time as possible through a very unique and simple 3-step system that is unlike anything I have ever seen - and through a product that people already spend BILLIONS of dollars per year on. And get this... It's been designed so you will start F.R.E.E and be well on your way to this income goal before you ever spend a penny. This system rewards "spillover" like crazy to the people who are working the hardest - it's really the first forced matrix I have ever seen. And since it's F.R.E.E to start, it's spreading across the globe VERY fast. Someone else will have joined us by the time you finish reading this email. Timing is critical! I won't go into a lot of detail in this email, but you need to go look at this today. Right now! It will only take a few minutes to get positioned and activate your f.r.e.e trial so you can begin earning commissions immediately. The short audio clip on my web site will explain everything: http://www.5000-dollar.ws I strongly encourage you to go signup as soon as possible. It's f.r.e.e, so you're risking nothing except the few minutes it will take you to check this out, and you'll also get a web site and a domain name to use for whatever you want as an added bonus. Email me back and let me know when you're ready to get started so I can help you progress though the 3 steps as quickly as I am. I REALLY don't want you to miss this. I wish you and all your family and friends a happy and successful new year Best regards from Germany Olga "Global Power Team" Olga Reimer Olga-20(a)web.de http://www.5000-dollar.ws * You get this email, because you (or somebody using your email address) ordered Information about home-based-business or sign in our newsletter. If you don't do, please delete this mail. You'll get it only one time.

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

XEmacs-Patches January 2005