January 2005 - XEmacs-Patches - XEmacs Mailing List Archives

Google AdWords Part 2 20 years, 3 months

HotWebsites.us

Google AdWords (https://adwords.google.com) is a great way to promote our websites, make sales, and generate profits for yourself. The ROI is good and the method is simple once you learn a few tricks. If you have questions about this or any other method of promotion please contact us via email 24 hours per day and we will do our very best to assist you :) How one Trivial Change Can Cut Your Bid Prices by 95 PERCENT! Today I'm going to talk about the thing that many newcomers find most confusing about Google AdWords - and I'm going to explain why it's a really ingenious twist that will actually help you. The price you bid is almost never the price you actually pay. You almost always pay less. First, it's a little bit like eBay: You pay 1 cent above the position below you, not the maximum that you bid. But there's an even more important secret that is the key to getting lower and lower prices, even while other bidders are jumping into the game: Your Click Thru Rate (CTR) is MORE important than how much you bid. The Click Thru Rate is the percentage of people searching who click. If 100 people search, your ad shows up 100 times, and one person clicks through, that's a 1% click thru rate. So let's say I've got a 1% CTR and I'm paying $1.00 for position #2. Let's say you've got a 2% CTR --- you only have to pay 51 cents to get position #2 and knock me down to position #3. That means if you're 2 times as relevant, you pay 1/2 as much! The rules are simple, but the implications are huge. When you achieve high click-thru rates, your bid prices go down, down, down and your traffic goes up. The difference can be quite amazing. In early tests I attempted to use the exact same words in two different ads. All I did was reverse two of the lines - and the Click Thru Rate jumped from 0.1% to 3.6%!!! That means that the second ad gets more than TWENTY TIMES as much traffic for the same amount of money. Just think how much money we'd be leaving on the table if we didn't discover this?? This is just one of dozens of tricks I've found that push your bid prices down, down, down while your traffic goes up. Beat your best and you'll get more and more traffic for less. I just explained how Google ranks your ad higher as your CTR goes up. Overture does not do this. In Overture, the highest bidder always wins. That rewards people who have more money than brains. Which means that for the smart marketer, Google is vastly superior! There's one other thing I need to tell you: This is precisely the thing that gets people all tangled up over disabled keywords. Keywords get disabled for one and only one reason: The message in the ad doesn't match what the person wanted when they typed in the keyword! How do you fix this problem? By organizing your keywords into narrow themes and by testing different ads, like I described above, until peoples' clicks vote on the words that actually sell! This is an absolutely foolproof method. What does the Wall Street Journal have to do with Google AdWords? Plenty. The Wall Street Journal advertises for new subscriptions with Google AdWords. But that's not what I'm going to talk about today. No, what I'm going to talk about is the WSJ's famous direct mail letter, the one that's been selling millions of subscriptions. They mail 30 million copies of that letter per year. This two page letter says: Dear Reader, On a beautiful late spring afternoon, twenty-five years ago, two young men graduated from the same college. They were very much alike, these two young men. Both had been better than average students, both were personable, and - as young college graduates are - both were filled with ambitious dreams for the future. Recently, these men returned to their college for their twenty-fifth reunion... Of course it goes on to explain that one was super-successful because he read the Wall Street Journal. That letter has been selling WSJ subscriptions for 29 years - unchanged. That's right, they have not changed that letter in 29 years! Not that people haven't tried. Top writers have been trying to beat it ever since it was first written. And nobody's succeeded - until just recently. That's right, a copywriter named Mal Decker just beat it, apparently increasing the response by Twenty Percent! Mr. Decker should be mighty proud of himself. The reason this is so significant is that because of the improved performance of this letter, the WSJ now gets 20% more sales without spending a penny more on postage or printing. I can only guess, but when you subtract out expenses, this might actually double the profit they make selling their paper. The lesson is clear: In advertising, copy - your choice of words - is king. So what does this have to do with Google AdWords? Plenty. AdWords is set up to work the same way as direct mail. If you can beat your existing ad, the same way Mal Decker beat the WSJ letter, the exact same thing happens. You pay the same amount of money but you simply get more visitors. The same thing, in turn, happens once visitors get to your website: The better your copy on the website, and the more traffic it converts to dollars, the more money you get, and you don't have to spend a penny more on traffic! You can change the CTR of your ads hugely just by changing ONE WORD. And this is NOT unusual, not a fluke. It's actually QUITE NORMAL. That's right - ONE word can make that much difference. In coming updates I will show you a few examples of how simply reversing the order of two lines increased the response by 2000%! When you're writing those little ads, little hinges swing big doors! 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 and click on the "Sell our websites" link. You should also check out the "Sell using online auctions" page. 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

Copying text _from_ XEmacs is nice, too. 20 years, 3 months

Aidan Kehoe

Hi! This fixes the same sort of problem as did JWZ’s patches of the middle of last year, but this time for copying text to other apps. The calls to (encode-coding ... 'utf-8) don’t need to be conditionalised on 'mule for 21.5, because that coding system should always be available there. Bye, - Aidan -- “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.” Index: lisp/select.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/select.el,v retrieving revision 1.13 diff -u -r1.13 select.el --- lisp/select.el 2002/05/23 11:46:10 1.13 +++ lisp/select.el 2005/01/12 00:54:09 ＠＠ -255,6 +255,8 ＠＠ ;; Given a selection, this makes an extent in the buffer which holds that ;; selection, for highlighting purposes. If the selection isn't associated ;; with a buffer, this does nothing. + ;; + ;; Something similar needs to be hooked into the rectangle functions. (let ((buffer nil) (valid (and (extentp previous-extent) (extent-object previous-extent) ＠＠ -439,6 +441,35 ＠＠ (buffer-substring (car value) (cdr value))))) (t nil))) +(defun select-convert-to-utf-8-string (selection type value) + (cond ((stringp value) + (cons 'UTF8_STRING (encode-coding-string value 'utf-8))) + ((extentp value) + (save-excursion + (set-buffer (extent-object value)) + (save-restriction + (widen) + (cons 'UTF8_STRING + (encode-coding-string + (buffer-substring (extent-start-position value) + (extent-end-position value)) 'utf-8))))) + ((and (consp value) + (markerp (car value)) + (markerp (cdr value))) + (or (eq (marker-buffer (car value)) (marker-buffer (cdr value))) + (signal 'error + (list "markers must be in the same buffer" + (car value) (cdr value)))) + (save-excursion + (set-buffer (or (marker-buffer (car value)) + (error "selection is in a killed buffer"))) + (save-restriction + (widen) + (cons 'UTF8_STRING (encode-coding-string + (buffer-substring (car value) (cdr value)) + 'utf-8))))) + (t nil))) + (defun select-coerce-to-text (selection type value) (select-convert-to-text selection type value)) ＠＠ -788,7 +819,8 ＠＠ ;; Types listed in here can be selections of XEmacs (setq selection-converter-out-alist - '((TEXT . select-convert-to-text) + '((UTF8_STRING . select-convert-to-utf-8-string) + (TEXT . select-convert-to-text) (STRING . select-convert-to-string) (COMPOUND_TEXT . select-convert-to-compound-text) (TARGETS . select-convert-to-targets)

1 participants
0 comments

Google AdWords Part 1 20 years, 3 months

HotWebsites.us

Google AdWords (https://adwords.google.com) is a great way to promote our websites, make sales, and generate profits for yourself. The ROI is good and the method is simple once you learn a few tricks. We hope to introduce to you a few of the basics over the next couple weeks. If you have questions about this or any other method of promotion please contact us via email 24 hours per day and we will do our very best to assist you :) There is ONE central idea, one key concept that Google wants you to understand. If you have this right, Google will literally reward you by giving you lower prices on clicks, and your customers will reward you by buying what you have to sell. If you DON'T have this right, you'll pay way too much for clicks, your campaigns will get disabled, and your whole Google experience will be unpleasant. The one thing that matters on Google is relevance. You might think of this as "message to market match." This will make complete sense once you understand a bit of Google's history. Google started in 1998, after the "big boys" in the search engine game like Yahoo and AltaVista were well-established. At the time, few people would have bet that Google would overtake them all - but in five years they have done exactly that. What's even more remarkable is they did so without a bunch of hype and loud marketing. They literally built a better mousetrap and the world beat a path to their door. So what happened? Google's mission in life was to build a search engine that would give people exactly what they were searching for, as fast as possible. If you were searching for "California butterflies" they wanted to give you the very best and most popular California butterfly websites on the very first page of results. They developed an amazing mathematical formula for figuring out who visited websites and why, and using that information in their search engine. When they began to sell Pay Per Click advertising, they were extremely concerned that advertisers also put out messages that were highly relevant. Google rewards you for being relevant, and they let people who are searching vote for you. If your ad gets clicked on, it's relevant. If it doesn't, it's not. It's that simple. If you can't get 5 out of 1000 people (0.5%) to click on your ad, Google disables your ad. The higher your click thru rate, though, the less you have to pay for the position you want. So this creates a "Darwinian" effect, a deliberate natural selection that weeds out bad advertisers and rewards good ones. What's good for Google's customers is good for Google and good for you. When all the dust has settled, what really matters is that your ads and your content be relevant to the keywords you're bidding on. Your message must match what the person is thinking. What were they really thinking when they typed in "California butterflies?" That is the question. Figure that out and put it in front of them, and you'll win on Google. Write an ad that matches exactly what they're searching for and you'll beat your competitors by a country mile. A Valuable Little Piece of Customer Psychology for You: Here's a little mental trick to help you write Google ads. Imagine that you are not you. You are your customer. You're not the person with the solution. You're the person with the problem. You've got an itch and you want to scratch it. And you're not in front of your computer. You're sitting in front of their computer. What do you type into the search bar on Google? And what do you hope will come up? Answer that question and you'll be successful marketing online using Google AdWords. 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 and click on the "Sell our websites" link. You should also check out the "Sell using online auctions" page. 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

[CORE (21.4)] More FreeBSD build fixes -- alpha and amd64 20 years, 3 months

Steve Youngs

This should apply cleanly to 21.5 also. 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/unexelf.c Index: src/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v retrieving revision 1.290.2.82 diff -u -U0 -r1.290.2.82 ChangeLog --- src/ChangeLog 9 Jan 2005 18:45:38 -0000 1.290.2.82 +++ src/ChangeLog 10 Jan 2005 03:27:53 -0000 ＠＠ -0,0 +1,6 ＠＠ +2005-01-10 Steve Youngs <steve(a)sxemacs.org> + + From Andrey Slusar <anrays(a)gmail.com>: + + * unexelf.c: define `Elfw(type)' for FreeBSD alpha and amd64. + Index: src/unexelf.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/unexelf.c,v retrieving revision 1.15.2.1 diff -u -u -r1.15.2.1 unexelf.c --- src/unexelf.c 20 Aug 2002 11:38:23 -0000 1.15.2.1 +++ src/unexelf.c 10 Jan 2005 03:27:24 -0000 ＠＠ -475,6 +475,14 ＠＠ # include <sys/exec_elf.h> #endif +#if defined(__FreeBSD__) && (defined(__alpha__) || defined(__amd64__)) +# ifdef __STDC__ +# define ElfW(type) Elf64_##type +# else +# define ElfW(type) Elf64_/**/type +# endif +#endif + #if __GNU_LIBRARY__ - 0 >= 6 # include <link.h> /* get ElfW etc */ #endif -- |---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---| | In space, | | No one can hear you rip a stinky | |------------------------------------<steve(a)sxemacs.org>---|

2 participants
1 comments

[AC21.4] Follow-on patch for parallel builds 20 years, 3 months

Vin Shelton

APPROVE COMMIT 21.4 After applying Malcolm's parallel build patch, I had to apply the following to get 'make install' to work. 2005-01-10 Vin Shelton <acs(a)xemacs.org> * Makefile.in.in (RECURSIVE_MAKE_ARGS): Remove last few. --- Makefile.in.in~ 2005-01-10 17:55:24.133272216 -0500 +++ Makefile.in.in 2005-01-10 20:02:53.286424184 -0500 ＠＠ -414,7 +414,7 ＠＠ install-arch-dep: mkdir for subdir in ${INSTALL_ARCH_DEP_SUBDIR}; do \ - (cd ./$${subdir} && $(RECURSIVE_MAKE) install prefix=${prefix} \ + (cd ./$${subdir} && $(MAKE) $(RECURSIVE_MAKE_ARGS) install prefix=${prefix} \ exec_prefix=${exec_prefix} bindir=${bindir} libdir=${libdir} \ archlibdir=${archlibdir}) ; done if test "`(cd ${archlibdir} && $(pwd))`" != \ ＠＠ -523,7 +523,7 ＠＠ #### would be extremely dangerous for anyone to use it. ##uninstall: ## (cd ./lib-src; \ -## $(RECURSIVE_MAKE) uninstall \ +## $(MAKE) $(RECURSIVE_MAKE_ARGS) uninstall \ ## prefix=${prefix} exec_prefix=${exec_prefix} \ ## bindir=${bindir} libdir=${libdir} archlibdir=${archlibdir}) ## for dir in ${lispdir} ${etcdir} ; do \ ＠＠ -630,7 +630,7 ＠＠ unlock: chmod u+w $(SOURCES) cpp/* -cd ./elisp && chmod u+w Makefile README *.texi - for d in src etc lib-src lisp; do (cd ./$$d && $(RECURSIVE_MAKE) $＠); done + for d in src etc lib-src lisp; do (cd ./$$d && $(MAKE) $(RECURSIVE_MAKE_ARGS) $＠); done cd ./lisp/term && chmod u+w README *.el cd ./man && chmod u+w *texi* ChangeLog split-man cd ./lwlib && chmod u+w *.[ch] Makefile.in.in ＠＠ -638,7 +638,7 ＠＠ relock: chmod u-w $(SOURCES) cpp/* -cd ./elisp && chmod u-w Makefile README *.texi - for d in src etc lib-src lisp; do (cd ./$$d && $(RECURSIVE_MAKE) $＠); done + for d in src etc lib-src lisp; do (cd ./$$d && $(MAKE) $(RECURSIVE_MAKE_ARGS) $＠); done cd ./lisp/term && chmod u+w README *.el cd ./man && chmod u+w *texi* ChangeLog split-man cd ./lwlib && chmod u+w *.[ch] Makefile.in.in

1 participants
0 comments

[AC21.4] Parallel builds. 20 years, 3 months

Vin Shelton

Malcolm Purvis <malcolmpurvis(a)optushome.com.au> writes: > RECOMMEND 21.4 > > This is the 21.4 version of the my parallel builds patch. There is no reason > to include this in 21.4.16 if its inclusion would delay the release. > > Malcolm > > > ChangeLog addition: > > 2004-09-08 Malcolm Purvis <malcolmp(a)xemacs.org> > > * INSTALL: A POSIX compatible Make is required for builds. > * Makefile.in.in: Enable support for parallel builds. > > src/ChangeLog addition: > > 2004-09-08 Malcolm Purvis <malcolmp(a)xemacs.org> > > * Makefile.in.in: Enable support for parallel builds. > APPROVE COMMIT 21.4. Thanks for the patch, Malcolm; it will appear in 21.4.17 - "Jumbo Shrimp". - Vin

2 participants
2 comments

[S] [C] xemacs-21.5: Fix mule-win32-init typo in dumped-lisp.el 20 years, 3 months

Adrian Aichner

SUPERSEDES <41E02799.5090805(a)etb.net.co> COMMIT What's the proper file-coding to use for ChangeLog files to handle wide characters? 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.606 diff -u -U0 -r1.606 ChangeLog --- lisp/ChangeLog 9 Jan 2005 09:44:43 -0000 1.606 +++ lisp/ChangeLog 9 Jan 2005 14:21:17 -0000 ＠＠ -2,0 +3,6 ＠＠ + * dumped-lisp.el (preloaded-file-list): Fix typo in + "mule-win32-init" path in preloaded-file-list, as suggected by + Alejandro L~pez-Valencia. + +2005-01-09 Adrian Aichner <adrian(a)xemacs.org> + xemacs-21.5 source patch: Diff command: cvs -f -z3 -q diff -u -w -N Files affected: lisp/dumped-lisp.el Index: lisp/dumped-lisp.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/dumped-lisp.el,v retrieving revision 1.50 diff -u -w -r1.50 dumped-lisp.el --- lisp/dumped-lisp.el 3 Jan 2005 10:29:13 -0000 1.50 +++ lisp/dumped-lisp.el 9 Jan 2005 14:17:11 -0000 ＠＠ -168,7 +168,7 ＠＠ (when (featurep '(and mule x)) "mule/mule-x-init") (when (featurep '(and mule tty)) "mule/mule-tty-init") (when (and (featurep 'mule) (memq system-type '(windows-nt cygwin32))) - "mule-mule/win32-init") + "mule/mule-win32-init") "code-init" ; set up defaults ;; All files after this can have extended characters in them. (when (featurep 'mule) -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
1 comments

[PATCH] File positions are 0-based 20 years, 3 months

Vin Shelton

Following up on Ben and Steve's sleuthing. lisp/ChangeLog addition: 2004-01-08 Ben Wing <ben(a)xemacs.org> * code-files.el (load): File positions are 0 based not 1 based. Thanks to Steve Youngs. 21.4 source patch: Diff command: cvs -q diff -u Files affected: lisp/code-files.el Index: lisp/code-files.el =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lisp/code-files.el,v retrieving revision 1.7.2.2 diff -a -u -u -r1.7.2.2 code-files.el --- lisp/code-files.el 2002/04/30 16:05:34 1.7.2.2 +++ lisp/code-files.el 2005/01/09 00:26:01 ＠＠ -284,7 +284,7 ＠＠ (set-buffer (get-buffer-create " *load*")) (erase-buffer) (let ((coding-system-for-read 'raw-text)) - (insert-file-contents path nil 1 3001)) + (insert-file-contents path nil 0 3000)) (find-coding-system-magic-cookie)) (if elc ;; if reading a byte-compiled file and we didn't find

1 participants
1 comments

[CORE (21.4)] FreeBSD build fixes 20 years, 3 months

Steve Youngs

A couple of FreeBSD build fixes that one of my developers picked up. I just had a quick look at 21.5 and it looks like this is needed there too. 21.4 patch: ChangeLog files diff command: cvs -q diff -U 0 Files affected: src/ChangeLog lib-src/ChangeLog Source files diff command: cvs -q diff -uN Files affected: src/s/freebsd.h lib-src/fakemail.c Index: lib-src/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lib-src/ChangeLog,v retrieving revision 1.115.2.25 diff -u -U0 -r1.115.2.25 ChangeLog --- lib-src/ChangeLog 6 Dec 2004 01:08:10 -0000 1.115.2.25 +++ lib-src/ChangeLog 8 Jan 2005 18:04:25 -0000 ＠＠ -0,0 +1,8 ＠＠ +2005-01-09 Steve Youngs <steve(a)sxemacs.org> + + From Andrey Slusar <anrays(a)gmail.com>: + + * fakemail.c (CURRENT_USER): Define it if FreeBSD version is >= + 400000. Also, when FreeBSD version is >= 400000 geteuid returns + uid_t instead of unsigned short. + Index: lib-src/fakemail.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/lib-src/fakemail.c,v retrieving revision 1.5 diff -u -u -r1.5 fakemail.c --- lib-src/fakemail.c 12 Apr 2001 18:21:01 -0000 1.5 +++ lib-src/fakemail.c 8 Jan 2005 18:03:41 -0000 ＠＠ -149,9 +149,17 ＠＠ extern char *malloc (), *realloc (); #endif +#if defined(__FreeBSD_version) && __FreeBSD_version >= 400000 +#define CURRENT_USER +#endif + #ifdef CURRENT_USER extern struct passwd *getpwuid (); +#if defined(__FreeBSD_version) && __FreeBSD_version >= 400000 +extern uid_t geteuid (); +#else extern unsigned short geteuid (); +#endif static struct passwd *my_entry; #define cuserid(s) \ (my_entry = getpwuid ((int) geteuid ()), \ Index: src/ChangeLog =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/ChangeLog,v retrieving revision 1.290.2.81 diff -u -U0 -r1.290.2.81 ChangeLog --- src/ChangeLog 6 Dec 2004 01:08:29 -0000 1.290.2.81 +++ src/ChangeLog 8 Jan 2005 18:04:39 -0000 ＠＠ -0,0 +1,7 ＠＠ +2005-01-09 Steve Youngs <steve(a)sxemacs.org> + + From Andrey Slusar <anrays(a)gmail.com>: + + * s/freebsd.h (LIBS_SYSTEM): Only set to "-lutil -lxpg4" if + FreeBSD version is >= 199701 _and_ < 600006. + Index: src/s/freebsd.h =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/s/freebsd.h,v retrieving revision 1.20 diff -u -u -r1.20 freebsd.h --- src/s/freebsd.h 12 Apr 2001 18:24:42 -0000 1.20 +++ src/s/freebsd.h 8 Jan 2005 18:03:46 -0000 ＠＠ -29,7 +29,7 ＠＠ #ifndef __FreeBSD_version #include <osreldate.h> #endif -#if __FreeBSD_version >= 199701 +#if __FreeBSD_version >= 199701 && __FreeBSD_version < 600006 #define LIBS_SYSTEM "-lutil -lxpg4" #else #define LIBS_SYSTEM "-lutil" -- |---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---| | In space, | | No one can hear you rip a stinky | |------------------------------------<steve(a)sxemacs.org>---|

2 participants
1 comments

[ACR21.4] TTY --memory-usage-stats fix. 20 years, 3 months

Malcolm Purvis

APPROVE COMMIT RECOMMEND 21.4 Way back in October Zajcev Evgeny reported the following: If XEmacs is compiled with memory usage enabled, running in console and issuing `(window-memory-usage (selected-window))' will core dump XEmacs because tty console does not have method to compute scrollbar instance usage and there no check for that. His suggested solution, cast as a patch below, fixes the problem. This patch has been committed. It is applicable for 21.4 as well. Thanks Zajcev! Malcolm src/ChangeLog addition: 2005-01-06 Zajcev Evgeny <zevlg(a)yandex.ru> * scrollbar.c (compute_scrollbar_instance_usage): Only call device method compute_scrollbar_instance_usage() if it is defined. xemacs-memory-usage source patch: Diff command: cvs -q diff -u Files affected: src/scrollbar.c Index: src/scrollbar.c =================================================================== RCS file: /pack/xemacscvs/XEmacs/xemacs/src/scrollbar.c,v retrieving revision 1.32 diff -u -r1.32 scrollbar.c --- src/scrollbar.c 2004/09/20 19:19:59 1.32 +++ src/scrollbar.c 2005/01/06 03:14:23 ＠＠ -267,7 +267,8 ＠＠ { int total = 0; - total += DEVMETH (d, compute_scrollbar_instance_usage, (d, inst, ovstats)); + if (HAS_DEVMETH_P(d, compute_scrollbar_instance_usage)) + total += DEVMETH (d, compute_scrollbar_instance_usage, (d, inst, ovstats)); while (inst) { -- Malcolm Purvis <malcolmpurvis(a)optushome.com.au> Q: Why did the chicken cross the Mobius strip? A: To get to the other... uh... err...

2 participants
1 comments

2025

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