Steve Youngs <steve@xxxxxxxx> writes:
> > What about writing `report-xwem-bug' Steve? :)
>
> No, I won't do that, but I will write `xwem-report-bug'. :-)
>
> Before I do, some questions...
>
> In my Eicq bug reporter I wrote it so that it only reports Eicq user
> variables that have been changed from the default. Do you want that?
> Very cool stuff. :-P
Yes of course, cool thing! [1]
>
> Which of these do you want included in reports...
>
> - XE installation string (M-x describe-installation)
yes
> - List of installed XE packages
Yes
> - List of currently loaded XE DSO's
yes
> - List of recent keystrokes (how many?)
probably .. don't know how to use this info however .. 10
> - Recent messages from view-lossage (how many?)
20 is enough
>
> - Contents of any lisp backtrace buffer if it exists
Yes
> - Contents of any gdb buffer if it exists
yes
> - Contents of xwem-debug buffer if it exists
Yes
> - Contents of xwem-messages buffer
Yes
> Anything else you want?
- Result of execution xdpyinfo command, command constructed
like this (concat "xdpyinfo -display " (X-Dpy-name
(xwem-dpy)))
- Values of some addition variables, such as:
* window-setup-hook
* kill-emacs-hook
* xwem-after-init-hook (already done by [1]?)
* xwem-exit-hook (already done by [1]?)
* xwem-manage-list (already done by [1]?)
--
XWEM - The best environment for hacker.
|