Re: [e-users] screen setup reset

2022-02-07 Thread gary
On 2022-02-07 13:02, Ross Vandegrift wrote: On Sat, Feb 05, 2022 at 04:48:08PM -0800, gary wrote: I see that 25 has already made it to debian bookworm. Any chance that it will get into bullseye backports any time soon? It's possible, depending on my time. I haven't historically

Re: [e-users] screen setup reset

2022-02-07 Thread Ross Vandegrift
On Sat, Feb 05, 2022 at 04:48:08PM -0800, gary wrote: > I see that 25 has already made it to debian bookworm. Any chance that it > will get into bullseye backports any time soon? It's possible, depending on my time. I haven't historically maintained backports packages, but it could be nice in

Re: [e-users] screen setup reset

2022-02-05 Thread gary
I see that 25 has already made it to debian bookworm. Any chance that it will get into bullseye backports any time soon? On 2022-02-03 11:47, Ross Vandegrift wrote: Hi Pierre, On Thu, Feb 03, 2022 at 10:27:52AM +0100, Pierre Couderc via enlightenment-users wrote: e25.1 has arrived to me

Re: [e-users] screen setup reset

2022-02-03 Thread Pierre Couderc via enlightenment-users
On 2/3/22 20:47, Ross Vandegrift wrote: Hi Pierre, On Thu, Feb 03, 2022 at 10:27:52AM +0100, Pierre Couderc via enlightenment-users wrote: e25.1 has arrived to me thanks to sid debian package. Well, honestly, I shall not say it is a catastrophe, even if I am not sure to like flat look...But

Re: [e-users] screen setup reset

2022-02-03 Thread Ross Vandegrift
Hi Pierre, On Thu, Feb 03, 2022 at 10:27:52AM +0100, Pierre Couderc via enlightenment-users wrote: > e25.1 has arrived to me thanks to sid debian package. > > Well, honestly, I shall not say it is a catastrophe, even if I am not sure > to like flat look...But I had to fully reinitialize my

[e-users] screen setup reset

2022-02-03 Thread Pierre Couderc via enlightenment-users
e25.1 has arrived to me thanks to sid debian package. Well, honestly, I shall not say it is a catastrophe, even if I am not sure to like flat look...But I had to fully reinitialize my environment before being able to start see it running, removing all previous ~/.e* . So I had to declare