June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: where is lpr-buffer? 24 years, 11 months

Adrian Aichner

>>>>> "Andy" == Andy Piper <andyp(a)parallax.co.uk> writes: Andy> Toolbar print defaults to lpr-buffer. I cannot find this Hello Andy, (package-get-package-provider 'lpr-buffer) nil (package-get-package-provider 'lpr) (os-utils "1.08") HTH, Adrian Andy> function anymore. It used to work until relatively Andy> recently. Andy> andy Andy> --------------------------------------------------------------------------- Andy> " .sigs are like your face - rarely seen by you and uglier Andy> than you think" Dr Andy Piper, Technical Architect, Parallax Andy> Solutions Ltd mail: andyp(a)parallax.co.uk web: Andy> www.parallax.co.uk/~andyp -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: where is lpr-buffer? 24 years, 11 months

Didier Verna

Andy Piper <andyp(a)parallax.co.uk> writes: > Toolbar print defaults to lpr-buffer. I cannot find this function anymore. > It used to work until relatively recently. os-utils/lpr.el

1 participants
0 comments

where is lpr-buffer? 24 years, 11 months

Andy Piper

Toolbar print defaults to lpr-buffer. I cannot find this function anymore. It used to work until relatively recently. andy --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

1 participants
0 comments

[Crash] XEmacs 21.0b46 24 years, 11 months

Holger Schauer

Sorry, folks, no core this time. The sysadmin seems to have set a ulimit on the core size. XEmacs died during starting up VM. uname -a: SunOS noblues.coling.uni-freiburg.de 5.6 Generic sun4u sparc SUNW,Ultra-1 ./configure 'sparc-sun-solaris2.6' '--prefix=/home/schauer/misc' '--package-path=/home/schauer/misc/lib/xemacs/packages/xemacs-packages' '--cflags=-O2' '--site-includes=/home/schauer/misc/include' '--site-libraries=/home/schauer/misc/lib' XEmacs 21.0 "Toggenburg" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /home/schauer/misc/src/packages/xemacs/xemacs-21.0-b46 What installation prefix should install use? /home/schauer/misc What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -O2 Should XEmacs use the GNU version of malloc? yes 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/dt/include /usr/openwin/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional header files: /home/schauer/misc/include Additional libraries: /home/schauer/misc/lib Runtime library search path: /home/schauer/misc/lib:/usr/dt/lib:/usr/openwin/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for GIF image conversion. Compiling in support for JPEG image conversion. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Lisp backtrace follows: # (catch #<INTERNAL EMACS BUG (opaque, size=4) 0x242ac0> ...) # (unwind-protect ...) # (unwind-protect ...) add-spec-list-to-specifier(#<image-specifier global=<unspecified> fallback=((nil . ...)) 0x1621> ((global (nil . "/home/schauer/misc/lib/xemacs/packages/xemacs-packages/etc/vm/print-dn.xpm"))) nil) # bind (is-valid nval how-to-add tag-set locale value specifier) set-specifier(#<image-specifier global=<unspecified> fallback=((nil . ...)) 0x1621> "/home/schauer/misc/lib/xemacs/packages/xemacs-packages/etc/vm/print-dn.xpm" nil nil nil) # bind (how-to-add tag-set locale value property glyph) set-glyph-property(#<glyph (buffer) #<image-specifier global=<unspecified> fallback=(...) 0x1621>0x1620> image "/home/schauer/misc/lib/xemacs/packages/xemacs-packages/etc/vm/print-dn.xpm" nil nil nil) # bind (how-to-add tag-set locale spec glyph) set-glyph-image(#<glyph (buffer) #<image-specifier global=<unspecified> fallback=(...) 0x1621>0x1620> "/home/schauer/misc/lib/xemacs/packages/xemacs-packages/etc/vm/print-dn.xpm") # bind (glyph type spec-list) make-glyph("/home/schauer/misc/lib/xemacs/packages/xemacs-packages/etc/vm/print-dn.xpm") # bind (f) #<compiled-function (f) "...(7)" [make-glyph expand-file-name f vm-toolbar-pixmap-directory] 4>("print-dn.xpm") mapcar(#<compiled-function (f) "...(7)" [make-glyph expand-file-name f vm-toolbar-pixmap-directory] 4> ("print-up.xpm" "print-dn.xpm" "print-dn.xpm")) # bind (tuples tuple files var) vm-toolbar-initialize() vm-toolbar-install-toolbar() # bind (full-startup did-read-index-file folder-buffer first-time totals-blurb preserve-auto-save-file) byte-code("..." [bufferp folder nil preserve-auto-save-file totals-blurb first-time folder-buffer did-read-index-file full-startup expand-file-name vm-primary-inbox vm-folder-directory file file-directory-p error "%s is a directory" vm-get-file-buffer default-directory t no-conversion coding-system-for-read enable-local-variables inhibit-local-variables message "Reading %s..." find-file-noselect item vm-folder-history "Reading %s... done" buffer-file-coding-system current-load-list vm-xemacs-mule-p get-coding-system no-conversion-unix no-conversion-dos no-conversion-mac binary buffer-modified-p omodified buffer-read-only ((set-buffer-modified-p omodified)) encode-coding-region set-buffer-file-coding-system decode-coding-region vm-check-for-killed-summary vm-check-for-killed-presentation 0 vm-messages-not-on-disk major-mode vm-mode buffer-file-name file-newer-than-file-p make-auto-save-file-name read-only default-value vm-folder-read-only buffer-disable-undo abbrev-mode auto-fill-mode vm-mode-internal vm-read-index-file-maybe vm-assimilate-new-messages vm-gobble-visible-header-variables vm-gobble-bookmark vm-gobble-pop-retrieved vm-gobble-summary vm-gobble-labels vm-start-itimers-if-needed this-command apply vm-goto-new-folder-frame-maybe (folder) (primary-folder folder) vm-summary-buffer vm-presentation-buffer buffer-to-display vm-display vm startup vm-raise-frame-at-startup vm-raise-frame vm-emit-totals-blurb vm-thoughtfully-select-message vm-update-summary-and-mode-line vm-toolbar-support-possible-p vm-use-toolbar "Initializing toolbar..." vm-toolbar-install-toolbar "Initializing toolbar... done" vm-toolbar-update-toolbar vm-use-menus vm-menu-support-possible-p vm-menu-install-visited-folders-menu vm-should-generate-summary vm-summarize vm-mutable-frames vm-frame-per-summary vm-mutable-windows switch-to-buffer vm-message-list vm-preview-current-message run-hooks vm-visit-folder-hook substitute-command-keys "Auto save file is newer; consider \\[recover-file]. FOLDER IS READ ONLY." throw done vm-auto-get-new-m ail vm-block-new-mail "Checking for new mail for %s..." buffer-name vm-get-spooled-mail vm-startup-message-displayed vm-display-startup-message input-pending-p] 7) # (catch done ...) # bind (read-only folder) #<compiled-function (&optional folder read-only) "...(7)" [vm-session-initialization done (byte-code "À !?À !« ªÝ ®É\n\" Í !«ÎÏ \"ªÄÐ !®¾«É!®ÒÂÓ×Ø \"Ù ! ®\nk¬×Ü \",)qÝB«Åà!àá!a¬»à!àâ!a¬±à!àã!a¬§à!àä!a¬Âå &'èéed#êÓÂ\"ëed#+ì í å «¬þ «C«D«EF «GªH\««I®J®pKLKDCD®MND$O«P «Q R S T «U«×V!W ×X!Y Z«[ «\\«Ð] «¬^ÒÂ\"I«_«`«O«P a«LÂDCD®MND$ªbI®J®p!)c«d ef«× ««×gh!««ijÒ\"k«½l¬¹7¬µ×m2®n \"oÒ!«ýÒ!«Q R «d ªS × !tp?q r ?× !." ... 7)] 2 "Read mail under Emacs.\nOptional first arg FOLDER specifies the folder to visit. It defaults\nto the value of vm-primary-inbox. The folder buffer is put into VM\nmode, a major mode for reading mail.\n\nPrefix arg or optional second arg READ-ONLY non-nil indicates\nthat the folder should be considered read only. No attribute\nchanges, message additions or deletions will be allowed in the\nvisited folder.\n\nVisiting the primary inbox causes any contents of the system mailbox to\nbe moved and appended to the resulting buffer.\n\nAll the messages can be read by repeatedly pressing SPC. Use `n'ext and\n`p'revious to move about in the folder. Messages are marked for\ndeletion with `d', and saved to another folder with `s'. Quitting VM\nwith `q' expunges deleted messages and saves the buffered folder to\ndisk.\n\nSee the documentation for vm-mode for more information." (list nil current-prefix-arg)>(nil nil) call-interactively(vm) # (condition-case ... . error) # (catch top-level ...) Holger -- --- http://www.coling.uni-freiburg.de/~schauer --- Why people hate using Lisp: "Are people suffering from parenthophobia-by-proxy, mistaking `parens' for `parents'?" - Erik Naggum in comp.emacs.xemacs

1 participants
0 comments

"Where is perldb?" or "Package debug provides nil" 24 years, 11 months

Adrian Aichner

Hi Packagers! Say I want to use perldb in XEmacs-21.0. So I see who provides this feature: (package-get-package-provider 'perldb) Hmmh.. Lucky as I am, I have it installed, so: (find-function-noselect 'perldb) (#<buffer "gud.el"> . 86738) (locate-library "gud.el") "/export/home/tmp/packages-21.0/lisp/debug/gud.el" Ah, it's part of the debug package. Hmmh! package debug is understating its utility enormously with `provides nil': (package-get-info-find-package package-get-base 'debug) ((standards-version 1.0 version "1.03" author-version "21.0b42" date "1998-06-01" build-date "1998-06-01" maintainer "XEmacs Development Team <xemacs-beta(a)xemacs.org>" distribution contrib priority low category "prog" dump nil description "GUD, gdb, dbx debugging support." filename "debug-1.03-pkg.tar.gz" md5sum "8714c8ed2dd221501b2ec9818c773d29" size 90336 provides nil requires (xemacs-base) type regular)) How is the provides property generated? Could this be a systematic error affecting other packages as well? I can answer the second one I think: (mapcan (function (lambda (p) (unless (plist-get (cadr p) 'provides) (list (car p))))) package-get-base) ;; These are the package with a 'provides property of nil: (sounds-au sounds-wav tooltalk edict egg-its leim locale debug) Best, Adrian -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: To ChangeLog or not to ChangeLog, that is the question 24 years, 11 months

Christoph Wedler

>>>>>"Hrvoje" == Hrvoje Niksic <hniksic(a)srce.hr> writes: Hrvoje> When a changelog addition is not needed, it's not needed. For Hrvoje> example, none of my NEWS patches contain a changelog entry. Hrvoje> Why? Because it's not needed. But only if you *add* entries (like Changes in XEmacs-21.0). I would vote for the following scheme: ChangeLog entries are always required, except for: * Fixing typos in comments (IMHO, they should be ChangeLogged in user visible parts, e.g., NEWS, docstrings, texi files). * changing code indentation (probably spacing in general) * Adding (but only adding!) things to the "history part" of files, e.g., the ChangeLog file itself, the "Changes in XEmacs-X.Y" of NEWS, etc. Changing comments should be ChangeLogged, because they should have a reason :-) (except typos, see above) I guess, this is more a "yes" vote... - Christoph

1 participants
0 comments

Re: To ChangeLog or not to ChangeLog, that is the question 24 years, 11 months

Hrvoje Niksic

SL Baur <steve(a)vmailer.xemacs.org> writes: > I propose the following addition to the rules of approving patches > on xemacs-review: > > If a ChangeLog-less patch appears that you wish to approve because > it is in your area of expertise of XEmacs, you include appropriate > ChangeLog entries with the approval. OK with me. However, there is one more thing where I disagree with Kyle: I don't think ChangeLogs should be exact descriptions of changes. We have CVS for that. In my opinion, something like "would return the wrong value", or "fixed counter incrementing" are perfectly fine ChangeLog entries. ChangeLog should be regarded as a "conceptual undo list" of changes, not as a plain-English replacement for `diff -u'. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Unspeakable horrors from outer space paralyze the living and resurrect the dead!

1 participants
0 comments

Re: Cannot "cvs ... checkout xemacs-packages" under Windows NT 24 years, 11 months

SL Baur

Andy Piper <andyp(a)parallax.co.uk> writes: > Er, I know you did the psgml goop in the core dist but did you do it > in the packages as well (which is what Adrian is trying to check > out)? Ur, um. No. Oops. Sorry, my mistake. > I don't see how you can have since we never resolved the issue of > what code actually references the badly named files. A Lisp stack backtrace will suffice.

1 participants
0 comments

Re: To ChangeLog or not to ChangeLog, that is the question 24 years, 11 months

SL Baur

Andy Piper <andyp(a)parallax.co.uk> writes: ... > I don't think patches should be rejected for not having changelogs but I > certainly don't think we should change policy from changelogs being > requested for all patches. The policy has been fairly lax. ChangeLog entries have been requested if missing, but in the case of small patches that I understand and can test, have not been an impediment to getting the patch applied. In the case of small & obvious (or documented elsewhere) patches, I've made the ChangeLog entries myself while applying the patch. In certain circumstances I'll apply ChangeLog-less medium-sized (or larger :-() patches and *not* add proper entries. This is evil -- I want this practice formally stopped. I don't have time to check every line of every patch that goes into XEmacs, but I don't think it's unreasonable to expect that people making patches use add-log.el as they go along. It's very easy to use and even its critics like Kyle, appear to have no problem synthetically generating ChangeLog entries. In other circumstances large patches have been accompanied by incomplete ChangeLog entries. I wish this practice stopped as well, hence this discussion. TopLevel ChangeLog: 1998-06-26 J Random Luser <luser(a)aol.com> **/*: Global change to do blah is *not* a proper ChangeLog entry and does nothing to help maintainers figure out what has gone wrong if something gets broken. We *have* to consider maintainability as a top priority. I propose the following addition to the rules of approving patches on xemacs-review: If a ChangeLog-less patch appears that you wish to approve because it is in your area of expertise of XEmacs, you include appropriate ChangeLog entries with the approval. It solves everything, including recalcitrant developers who refuse to document their work.

2 participants
1 comments

Re: Cannot "cvs ... checkout xemacs-packages" under Windows NT 24 years, 11 months

SL Baur

Adrian Aichner <aichner(a)ecf.teradyne.com> writes: > My environment was so clean before the checkout that the CVS working > directory did not even exist! I just try to checkout xemacs-packages > from scratch. When in doubt, reinstall the OS. It's the Microsoft Way(TM). I have no idea why you should still be having problems. The directory name with the colon in it was changed to the detriment of XEmacs maintenance long ago.

2 participants
1 comments

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 1998