Retrieving exceptions displayed thourgh the message "buffer"

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Retrieving exceptions displayed thourgh the message "buffer"

MontaroPDF
Hello,

First of all best wishes for this new year.

While I am using StumpWM for, maybe, a year, I just recently subscribed to this ML.

Recently, I got an exception with stumptray regarding a value of an invalid type.

I would like to know how I can get any message copied to the clipboard or how to display the messages log of the current stumpwm session in a text editor, for example.

This will allow me to open issue in github or seek for assistance on this ML.

Environment:
- OS: Fedora Linux 31
- StumpWM version: master branch of the github repository

Regards,

Roland Everaert
---
Use the F.O.S.S., Luke



Sent with ProtonMail Secure Email.

Reply | Threaded
Open this post in threaded view
|

Re: Retrieving exceptions displayed thourgh the message "buffer"

Stefan Reichör
Hi Roland,

the commands copy-last-message, copy-unhandled-error should do what you want...

Stefan.

> Hello,
>
> First of all best wishes for this new year.
>
> While I am using StumpWM for, maybe, a year, I just recently
> subscribed to this ML.
>
> Recently, I got an exception with stumptray regarding a value of an
> invalid type.
>
> I would like to know how I can get any message copied to the
> clipboard or how to display the messages log of the current stumpwm
> session in a text editor, for example.
>
> This will allow me to open issue in github or seek for assistance on
> this ML.
>
> Environment:
> - OS: Fedora Linux 31
> - StumpWM version: master branch of the github repository
> - Configuration: https://github.com/montaropdf/stumpwm-config
>
> Regards,
>
> Roland Everaert
> ---
> Use the F.O.S.S., Luke
>
>
>
> Sent with ProtonMail Secure Email.

Reply | Threaded
Open this post in threaded view
|

Re: Retrieving exceptions displayed thourgh the message "buffer"

MontaroPDF
Hello Stefan,

Unfortunately, none of those commands seems to catch anything, at least when called interactively.

copy-lass-message does not return anything, even in the clipboard history. And copy-unhandled-error tells me that there is no unhandled errors.


Roland Everaert
---
Use the F.O.S.S., Luke

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Le vendredi 10 janvier 2020 13:23, Stefan Reichör <[hidden email]> a écrit :

> Hi Roland,
>
> the commands copy-last-message, copy-unhandled-error should do what you want...
>
> Stefan.
>
> > Hello,
> > First of all best wishes for this new year.
> > While I am using StumpWM for, maybe, a year, I just recently
> > subscribed to this ML.
> > Recently, I got an exception with stumptray regarding a value of an
> > invalid type.
> > I would like to know how I can get any message copied to the
> > clipboard or how to display the messages log of the current stumpwm
> > session in a text editor, for example.
> > This will allow me to open issue in github or seek for assistance on
> > this ML.
> > Environment:
> >
> > -   OS: Fedora Linux 31
> > -   StumpWM version: master branch of the github repository
> > -   Configuration: https://github.com/montaropdf/stumpwm-config
> >
> > Regards,
> >
> > Roland Everaert
> >
> > ----------------
> >
> > Use the F.O.S.S., Luke
> > Sent with ProtonMail Secure Email.



Reply | Threaded
Open this post in threaded view
|

Re: Retrieving exceptions displayed thourgh the message "buffer"

Stefan Reichör
Hi Roland,

perhaps you find something of interest in ~/.xsession-errors

Stefan.

> Hello Stefan,
>
> Unfortunately, none of those commands seems to catch anything, at least when called interactively.
>
> copy-lass-message does not return anything, even in the clipboard history. And copy-unhandled-error tells me that there is no unhandled errors.
>
>
> Roland Everaert
> ---
> Use the F.O.S.S., Luke
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> Le vendredi 10 janvier 2020 13:23, Stefan Reichör <[hidden email]> a écrit :
>
>> Hi Roland,
>>
>> the commands copy-last-message, copy-unhandled-error should do what you want...
>>
>> Stefan.
>>
>> > Hello,
>> > First of all best wishes for this new year.
>> > While I am using StumpWM for, maybe, a year, I just recently
>> > subscribed to this ML.
>> > Recently, I got an exception with stumptray regarding a value of an
>> > invalid type.
>> > I would like to know how I can get any message copied to the
>> > clipboard or how to display the messages log of the current stumpwm
>> > session in a text editor, for example.
>> > This will allow me to open issue in github or seek for assistance on
>> > this ML.
>> > Environment:
>> >
>> > -   OS: Fedora Linux 31
>> > -   StumpWM version: master branch of the github repository
>> > -   Configuration: https://github.com/montaropdf/stumpwm-config
>> >
>> > Regards,
>> >
>> > Roland Everaert
>> >
>> > ----------------
>> >
>> > Use the F.O.S.S., Luke
>> > Sent with ProtonMail Secure Email.

Reply | Threaded
Open this post in threaded view
|

Re: Retrieving exceptions displayed thourgh the message "buffer"

MontaroPDF
Unfortunately, no such file in my homedir.

Running "(stumpwm:copy-last-message)" in the REPL return

"(:PRIMARY)"

But "xclip -selection p -o", in a terminal, returns "Error: target STRING not available" and not the error I see. So I suppose this is not related to my current issue.


Roland Everaert
---
Use the F.O.S.S., Luke

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Le vendredi 10 janvier 2020 15:35, Stefan Reichör <[hidden email]> a écrit :

> Hi Roland,
>
> perhaps you find something of interest in ~/.xsession-errors
>
> Stefan.
>
> > Hello Stefan,
> > Unfortunately, none of those commands seems to catch anything, at least when called interactively.
> > copy-lass-message does not return anything, even in the clipboard history. And copy-unhandled-error tells me that there is no unhandled errors.
> >
> > Roland Everaert
> >
> > ----------------
> >
> > Use the F.O.S.S., Luke
> > Sent with ProtonMail Secure Email.
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > Le vendredi 10 janvier 2020 13:23, Stefan Reichör [hidden email] a écrit :
> >
> > > Hi Roland,
> > > the commands copy-last-message, copy-unhandled-error should do what you want...
> > > Stefan.
> > >
> > > > Hello,
> > > > First of all best wishes for this new year.
> > > > While I am using StumpWM for, maybe, a year, I just recently
> > > > subscribed to this ML.
> > > > Recently, I got an exception with stumptray regarding a value of an
> > > > invalid type.
> > > > I would like to know how I can get any message copied to the
> > > > clipboard or how to display the messages log of the current stumpwm
> > > > session in a text editor, for example.
> > > > This will allow me to open issue in github or seek for assistance on
> > > > this ML.
> > > > Environment:
> > > >
> > > > -   OS: Fedora Linux 31
> > > > -   StumpWM version: master branch of the github repository
> > > > -   Configuration: https://github.com/montaropdf/stumpwm-config
> > > >
> > > > Regards,
> > > > Roland Everaert
> > > >
> > > > Use the F.O.S.S., Luke
> > > > Sent with ProtonMail Secure Email.



Reply | Threaded
Open this post in threaded view
|

Re: Retrieving exceptions displayed thourgh the message "buffer"

MontaroPDF
I have been able to reproduce the error through the REPL with SLY. Below you can find all the informations.

** In the REPL **

CL-USER> (in-package :stumpwm)
#<PACKAGE "STUMPWM">
STUMPWM> (stumptray::stumptray)
NIL
STUMPWM> (load-module "stumptray")
#<ASDF/LISP-ACTION:LOAD-OP >
#<ASDF/PLAN:SEQUENTIAL-PLAN {1005072E03}>
STUMPWM> (stumptray::stumptray)
; Debugger entered on #<TYPE-ERROR expected-type: (UNSIGNED-BYTE 32) datum: NIL>
[1] STUMPWM>
; Evaluation aborted on #<TYPE-ERROR expected-type: (UNSIGNED-BYTE 32) datum: NIL>
STUMPWM>


** Backtraces **

The value
  NIL
is not of type
  (UNSIGNED-BYTE 32)
   [Condition of type TYPE-ERROR]

Restarts:
 0: [RETRY] Retry SLY mREPL evaluation request.
 1: [*ABORT] Return to SLY's top level.
 2: [ABORT] abort thread (#<THREAD "sly-channel-1-mrepl-remote-1" RUNNING {1005CAC683}>)

Backtrace:
 0: (XLIB::WRITE-VECTOR-CARD32 #<XLIB:DISPLAY :0 (Fedora Project R12006000)> 24 #(NIL 408 2097209 0 0) 0 5)
 1: (XLIB::WRITE-SEQUENCE-CARD32 #<XLIB:DISPLAY :0 (Fedora Project R12006000)> 24 #(NIL 408 2097209 0 0) 0 5 NIL)
 2: (XLIB::CLIENT-MESSAGE-EVENT-PUT #<XLIB:DISPLAY :0 (Fedora Project R12006000)> :FORMAT 32 :SEQUENCE NIL :EVENT-WINDOW NIL :WINDOW #<XLIB:WINDOW :0 187> :TYPE :MANAGER :DATA #(NIL 408 2097209 0 0))
 3: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK :IN XLIB:SEND-EVENT))
 4: ((FLET "WITHOUT-INTERRUPTS-BODY-29" :IN SB-THREAD::CALL-WITH-RECURSIVE-LOCK))
 5: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK :IN XLIB:SEND-EVENT) {7FB51F95C70B}> #<SB-THREAD:MUTEX "CLX Buffer Lock" owner: #<SB-THREAD:THREAD "sly-channe..
 6: (XLIB:SEND-EVENT #<XLIB:WINDOW :0 187> :CLIENT-MESSAGE 131072 :WINDOW #<XLIB:WINDOW :0 187> :TYPE :MANAGER :FORMAT 32 :DATA #(NIL 408 2097209 0 0) :PROPAGATE-P NIL)
 7: (XLIB:SEND-EVENT #<XLIB:WINDOW :0 187> :CLIENT-MESSAGE 131072 :WINDOW #<XLIB:WINDOW :0 187> :TYPE :MANAGER :FORMAT 32 :DATA #(NIL 408 2097209 0 0) :PROPAGATE-P NIL) [more]
 8: (STUMPTRAY::FDO-TRAY-SEND-MANAGER-NOTIFICATION #S(STUMPTRAY::TRAY :WIN #<XLIB:WINDOW #1=:0 200037> :SOWIN #<XLIB:WINDOW #1#:0 200039> :FPWIN #<XLIB:WINDOW #1#:0 200038> :VIWIN #<XLIB:WINDOW #1#:0 2000..
 9: (STUMPTRAY::FDO-TRAY-INIT #S(STUMPTRAY::TRAY :WIN #<XLIB:WINDOW #1=:0 200037> :SOWIN #<XLIB:WINDOW #1#:0 200039> :FPWIN #<XLIB:WINDOW #1#:0 200038> :VIWIN #<XLIB:WINDOW #1#:0 20003A> :HIWIN #<XLIB:WIN..
10: (STUMPTRAY::TRAY-INIT #S(STUMPTRAY::TRAY :WIN #<XLIB:WINDOW #1=:0 200037> :SOWIN #<XLIB:WINDOW #1#:0 200039> :FPWIN #<XLIB:WINDOW #1#:0 200038> :VIWIN #<XLIB:WINDOW #1#:0 20003A> :HIWIN #<XLIB:WINDOW ..
11: (STUMPTRAY:STUMPTRAY)
12: (SB-INT:SIMPLE-EVAL-IN-LEXENV (STUMPTRAY:STUMPTRAY) #<NULL-LEXENV>)
13: (EVAL (STUMPTRAY:STUMPTRAY))


Hope this will be helpful.


Roland Everaert
---
Use the F.O.S.S., Luke

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Le vendredi 10 janvier 2020 15:51, MontaroPDF <[hidden email]> a écrit :

> Unfortunately, no such file in my homedir.
>
> Running "(stumpwm:copy-last-message)" in the REPL return
>
> "(:PRIMARY)"
>
> But "xclip -selection p -o", in a terminal, returns "Error: target STRING not available" and not the error I see. So I suppose this is not related to my current issue.
>
> Roland Everaert
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Use the F.O.S.S., Luke
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> Le vendredi 10 janvier 2020 15:35, Stefan Reichör [hidden email] a écrit :
>
> > Hi Roland,
> > perhaps you find something of interest in ~/.xsession-errors
> > Stefan.
> >
> > > Hello Stefan,
> > > Unfortunately, none of those commands seems to catch anything, at least when called interactively.
> > > copy-lass-message does not return anything, even in the clipboard history. And copy-unhandled-error tells me that there is no unhandled errors.
> > > Roland Everaert
> > >
> > > Use the F.O.S.S., Luke
> > > Sent with ProtonMail Secure Email.
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > Le vendredi 10 janvier 2020 13:23, Stefan Reichör [hidden email] a écrit :
> > >
> > > > Hi Roland,
> > > > the commands copy-last-message, copy-unhandled-error should do what you want...
> > > > Stefan.
> > > >
> > > > > Hello,
> > > > > First of all best wishes for this new year.
> > > > > While I am using StumpWM for, maybe, a year, I just recently
> > > > > subscribed to this ML.
> > > > > Recently, I got an exception with stumptray regarding a value of an
> > > > > invalid type.
> > > > > I would like to know how I can get any message copied to the
> > > > > clipboard or how to display the messages log of the current stumpwm
> > > > > session in a text editor, for example.
> > > > > This will allow me to open issue in github or seek for assistance on
> > > > > this ML.
> > > > > Environment:
> > > > >
> > > > > -   OS: Fedora Linux 31
> > > > > -   StumpWM version: master branch of the github repository
> > > > > -   Configuration: https://github.com/montaropdf/stumpwm-config
> > > > >
> > > > > Regards,
> > > > > Roland Everaert
> > > > > Use the F.O.S.S., Luke
> > > > > Sent with ProtonMail Secure Email.



Reply | Threaded
Open this post in threaded view
|

Re: Retrieving exceptions displayed thourgh the message "buffer"

MontaroPDF
It seems that the error was due to an issue with a fedora package.

The last update of fedora seems to have fix the issue.

The systray is now displaying properly.

Anyway, having a way to browse the messages like in emacs with the *Messages* buffer would be neat.

Regards,


Roland Everaert
---
Use the F.O.S.S., Luke

Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Le vendredi 10 janvier 2020 16:19, MontaroPDF <[hidden email]> a écrit :

> I have been able to reproduce the error through the REPL with SLY. Below you can find all the informations.
>
> ** In the REPL **
>
> CL-USER> (in-package :stumpwm)
> #<PACKAGE "STUMPWM">
> STUMPWM> (stumptray::stumptray)
> NIL
> STUMPWM> (load-module "stumptray")
> #<ASDF/LISP-ACTION:LOAD-OP >
> #<ASDF/PLAN:SEQUENTIAL-PLAN {1005072E03}>
> STUMPWM> (stumptray::stumptray)
> ; Debugger entered on #<TYPE-ERROR expected-type: (UNSIGNED-BYTE 32) datum: NIL>
> [1] STUMPWM>
> ; Evaluation aborted on #<TYPE-ERROR expected-type: (UNSIGNED-BYTE 32) datum: NIL>
> STUMPWM>
>
> ** Backtraces **
>
> The value
> NIL
> is not of type
> (UNSIGNED-BYTE 32)
> [Condition of type TYPE-ERROR]
>
> Restarts:
> 0: [RETRY] Retry SLY mREPL evaluation request.
> 1: [*ABORT] Return to SLY's top level.
> 2: [ABORT] abort thread (#<THREAD "sly-channel-1-mrepl-remote-1" RUNNING {1005CAC683}>)
>
> Backtrace:
> 0: (XLIB::WRITE-VECTOR-CARD32 #<XLIB:DISPLAY :0 (Fedora Project R12006000)> 24 #(NIL 408 2097209 0 0) 0 5)
> 1: (XLIB::WRITE-SEQUENCE-CARD32 #<XLIB:DISPLAY :0 (Fedora Project R12006000)> 24 #(NIL 408 2097209 0 0) 0 5 NIL)
> 2: (XLIB::CLIENT-MESSAGE-EVENT-PUT #<XLIB:DISPLAY :0 (Fedora Project R12006000)> :FORMAT 32 :SEQUENCE NIL :EVENT-WINDOW NIL :WINDOW #<XLIB:WINDOW :0 187> :TYPE :MANAGER :DATA #(NIL 408 2097209 0 0))
> 3: ((FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK :IN XLIB:SEND-EVENT))
> 4: ((FLET "WITHOUT-INTERRUPTS-BODY-29" :IN SB-THREAD::CALL-WITH-RECURSIVE-LOCK))
> 5: (SB-THREAD::CALL-WITH-RECURSIVE-LOCK #<CLOSURE (FLET SB-THREAD::WITH-RECURSIVE-LOCK-THUNK :IN XLIB:SEND-EVENT) {7FB51F95C70B}> #<SB-THREAD:MUTEX "CLX Buffer Lock" owner: #<SB-THREAD:THREAD "sly-channe..
> 6: (XLIB:SEND-EVENT #<XLIB:WINDOW :0 187> :CLIENT-MESSAGE 131072 :WINDOW #<XLIB:WINDOW :0 187> :TYPE :MANAGER :FORMAT 32 :DATA #(NIL 408 2097209 0 0) :PROPAGATE-P NIL)
> 7: (XLIB:SEND-EVENT #<XLIB:WINDOW :0 187> :CLIENT-MESSAGE 131072 :WINDOW #<XLIB:WINDOW :0 187> :TYPE :MANAGER :FORMAT 32 :DATA #(NIL 408 2097209 0 0) :PROPAGATE-P NIL) [more]
> 8: (STUMPTRAY::FDO-TRAY-SEND-MANAGER-NOTIFICATION #S(STUMPTRAY::TRAY :WIN #<XLIB:WINDOW #1=:0 200037> :SOWIN #<XLIB:WINDOW #1#:0 200039> :FPWIN #<XLIB:WINDOW #1#:0 200038> :VIWIN #<XLIB:WINDOW #1#:0 2000..
> 9: (STUMPTRAY::FDO-TRAY-INIT #S(STUMPTRAY::TRAY :WIN #<XLIB:WINDOW #1=:0 200037> :SOWIN #<XLIB:WINDOW #1#:0 200039> :FPWIN #<XLIB:WINDOW #1#:0 200038> :VIWIN #<XLIB:WINDOW #1#:0 20003A> :HIWIN #<XLIB:WIN..
> 10: (STUMPTRAY::TRAY-INIT #S(STUMPTRAY::TRAY :WIN #<XLIB:WINDOW #1=:0 200037> :SOWIN #<XLIB:WINDOW #1#:0 200039> :FPWIN #<XLIB:WINDOW #1#:0 200038> :VIWIN #<XLIB:WINDOW #1#:0 20003A> :HIWIN #<XLIB:WINDOW ..
> 11: (STUMPTRAY:STUMPTRAY)
> 12: (SB-INT:SIMPLE-EVAL-IN-LEXENV (STUMPTRAY:STUMPTRAY) #<NULL-LEXENV>)
>
> 13: (EVAL (STUMPTRAY:STUMPTRAY))
>
> Hope this will be helpful.
>
> Roland Everaert
>
> ------------------------------------------------------------------------------
>
> Use the F.O.S.S., Luke
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> Le vendredi 10 janvier 2020 15:51, MontaroPDF [hidden email] a écrit :
>
> > Unfortunately, no such file in my homedir.
> > Running "(stumpwm:copy-last-message)" in the REPL return
> > "(:PRIMARY)"
> > But "xclip -selection p -o", in a terminal, returns "Error: target STRING not available" and not the error I see. So I suppose this is not related to my current issue.
> > Roland Everaert
> >
> > Use the F.O.S.S., Luke
> > Sent with ProtonMail Secure Email.
> > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > Le vendredi 10 janvier 2020 15:35, Stefan Reichör [hidden email] a écrit :
> >
> > > Hi Roland,
> > > perhaps you find something of interest in ~/.xsession-errors
> > > Stefan.
> > >
> > > > Hello Stefan,
> > > > Unfortunately, none of those commands seems to catch anything, at least when called interactively.
> > > > copy-lass-message does not return anything, even in the clipboard history. And copy-unhandled-error tells me that there is no unhandled errors.
> > > > Roland Everaert
> > > > Use the F.O.S.S., Luke
> > > > Sent with ProtonMail Secure Email.
> > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > Le vendredi 10 janvier 2020 13:23, Stefan Reichör [hidden email] a écrit :
> > > >
> > > > > Hi Roland,
> > > > > the commands copy-last-message, copy-unhandled-error should do what you want...
> > > > > Stefan.
> > > > >
> > > > > > Hello,
> > > > > > First of all best wishes for this new year.
> > > > > > While I am using StumpWM for, maybe, a year, I just recently
> > > > > > subscribed to this ML.
> > > > > > Recently, I got an exception with stumptray regarding a value of an
> > > > > > invalid type.
> > > > > > I would like to know how I can get any message copied to the
> > > > > > clipboard or how to display the messages log of the current stumpwm
> > > > > > session in a text editor, for example.
> > > > > > This will allow me to open issue in github or seek for assistance on
> > > > > > this ML.
> > > > > > Environment:
> > > > > >
> > > > > > -   OS: Fedora Linux 31
> > > > > > -   StumpWM version: master branch of the github repository
> > > > > > -   Configuration: https://github.com/montaropdf/stumpwm-config
> > > > > >
> > > > > > Regards,
> > > > > > Roland Everaert
> > > > > > Use the F.O.S.S., Luke
> > > > > > Sent with ProtonMail Secure Email.