On 22/02/2022 23:12, Celejar wrote:
Hello,
I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
to "Lock screen before sleep" (in Session and Startup / General), but
when I use xscreensaver, when resuming from suspend the screen is often
visible for a brie
Hello,
I'm running Xfce4 on a recent install of Sid. I have configured Xfce4
to "Lock screen before sleep" (in Session and Startup / General), but
when I use xscreensaver, when resuming from suspend the screen is often
visible for a brief period before xscreensaver kicks in. I hav
On Mon, 21 Feb 2022 12:07:44 -0700
Charles Curley wrote:
> It looks like a lot of the touchpad's capabilities have been turned
> off (??). How do I turn them on again?
A bit of searching lead me to
https://linuxhint.com/change_mouse_touchpad_settings_xinput_linux/ and
https://www.mankier.com/4/l
On Sun, 20 Feb 2022 21:58:14 -0600
David Wright wrote:
> >
> > Is there a program I can use to examine the touch screen's setup?
>
> $ xinput
Interesting. I get:
root@ideapc:~# xinput
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST poin
On Sun 20 Feb 2022 at 15:49:18 (-0700), Charles Curley wrote:
> I am bringing up Debian 11 on a Lenovo IdeaPad Yoga 13. It has a touch
> screen, and Debian Installer installed the driver, ELAN Touchscreen.
> There is also a touchpad. Both sort of work. I am using an external
> mou
I am bringing up Debian 11 on a Lenovo IdeaPad Yoga 13. It has a touch
screen, and Debian Installer installed the driver, ELAN Touchscreen.
There is also a touchpad. Both sort of work. I am using an external
mouse, and that works just fine.
The buttons on the touch pad do not work. I can get
cat /sys/class/drm/card0/device/hwmon/hwmon0/temp1_input
Should give temperature:
Mine right now is:
29000
which apparently is 29C.
/sys/class/drm/card0/device/hwmon/hwmon0/pwm1
is the power management.
I returned home yesterday.
It seems the temperature here isn't out of the ordinary:
$ c
;> cable.
>>
>> During that 1-2s, the machine response is fine. Whatever I type during
>> that time goes there as input, and visible when the monitor comes back.
>
> Further diagnosing the problem, I could find out these messages in the
> log immediately after the scre
achine response is fine. Whatever I type during
> that time goes there as input, and visible when the monitor comes back.
Further diagnosing the problem, I could find out these messages in the
log immediately after the screen goes blank:
[31915.382609] [drm] PCIE GART of 256M enabled (table
On 2/5/22, Nicholas Geovanis wrote:
> On Sat, Feb 5, 2022, 3:15 PM c. marlow wrote:
>>
>> Subject: Screen not blanking
>> Date: Saturday 05 February 2022, 03:13:19 pm
>> From: "c. marlow"
>> To: us...@trinitydesktop.org
>>
>> Fresh instal
On Sat, Feb 5, 2022, 3:15 PM c. marlow wrote:
> Sending this message to both groups:
>
> -- Forwarded Message --
>
> Subject: Screen not blanking
> Date: Saturday 05 February 2022, 03:13:19 pm
> From: "c. marlow"
> To: us...@trinitydesktop.
Sending this message to both groups:
-- Forwarded Message --
Subject: Screen not blanking
Date: Saturday 05 February 2022, 03:13:19 pm
From: "c. marlow"
To: us...@trinitydesktop.org
Fresh install of Debian 11 ( as of yesterday)
Trinity Desktop 14
My screen is no
On Fri, Jan 28, 2022 at 05:05:56PM +0100, hdv@gmail wrote:
> On 2022-01-28 16:53, Andrew M.A. Cater wrote:
>
> > Wherever possible, it's easier if you are using Debian stable: more people
> > will hae experience / be running that at any one time.
> >
> > All the very best, as ever,
> >
> > Andy
On 2022-01-28 16:53, Andrew M.A. Cater wrote:
Wherever possible, it's easier if you are using Debian stable: more people
will hae experience / be running that at any one time.
All the very best, as ever,
Andy Cater
I know. But testing is more convenient for me. I need to test current
softwa
On 2022-01-28 16:48, Bijan Soleymani wrote:
On 2022-01-28 10:16, hdv@gmail wrote:
About the fan: I seem to remember I had to install amdgpu-fan (needed
to look that up, forgot the name) when I got this setup. Not sure if
it still is needed or that the driver can control the fan reliably
nowada
On Fri, Jan 28, 2022 at 04:16:19PM +0100, hdv@gmail wrote:
> On 2022-01-28 15:31, Bijan Soleymani wrote:
> > On 2022-01-28 08:40, hdv@gmail wrote:
> > > I am reasonably sure the problem lies in some form or combination of
> > > software. Sadly, my expertise in that area is insufficient to find
> >
On 2022-01-28 10:16, hdv@gmail wrote:
About the fan: I seem to remember I had to install amdgpu-fan (needed
to look that up, forgot the name) when I got this setup. Not sure if
it still is needed or that the driver can control the fan reliably
nowadays. I need to check that out too when I get h
On 2022-01-28 15:31, Bijan Soleymani wrote:
On 2022-01-28 08:40, hdv@gmail wrote:
I am reasonably sure the problem lies in some form or combination of
software. Sadly, my expertise in that area is insufficient to find out
what it is exactly.
What kernel/OS/driver are you using if it is softwa
On 2022-01-28 08:40, hdv@gmail wrote:
I am reasonably sure the problem lies in some form or combination of
software. Sadly, my expertise in that area is insufficient to find out
what it is exactly.
What kernel/OS/driver are you using if it is software I can try to
reproduce since I have a pre
On 2022-01-28 14:12, Pankaj Jangid wrote:
Pankaj Jangid writes:
UPDATE:
I have changed the HDMI cable and since last 6hrs I have not faced that
event again. Will update in the thread if it re-appears.
Another thing happened when I was replacing the cable. I heard the
sparking noise in the po
Pankaj Jangid writes:
> UPDATE:
>
> I have changed the HDMI cable and since last 6hrs I have not faced that
> event again. Will update in the thread if it re-appears.
>
> Another thing happened when I was replacing the cable. I heard the
> sparking noise in the power socket of monitor. So I tight
Pankaj Jangid writes:
> Dan Ritter writes:
>
>> Pankaj Jangid wrote:
>>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>>> facing a very strange problem. The monitor goes blank for a brief time,
>>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>>>
On 2022-01-27 5:30 a.m., hdv@gmail wrote:
Sadly I do not have access to this machine remotely. I do have my own
VPN server, but that does not help when the machine in question is
turned off. ;-)
I'll check the temperature when I am back, and when it happens again.
I played around a tiny bi
Tim Woodall writes:
> For a while I was using a mac (running macOS) plugged into a dock with
> two HDMI screens connected and I was having this problem occasionally.
> The mac was clearly thinking the screens had "gone away" because it
> would move windows around. I've now switched to a windows l
Vincent Lefevre writes:
> So it could be a hardware problem, with this monitor or something
> else, possibly specific to HDMI.
>
> I suggest that you try with another machine, another cable, etc. if
> possible. Or the same machine with another monitor.
I have multiple cables and an extra laptop.
"hdv@gmail" writes:
> You are not the only one. I see the exact same here. The system this
> happens on has an RX560 graphics card. I have been seeing these
> blackouts from the start on this configuration (more than 2 years
> now).
>
> I can confirm it is not a mechanical issue (not of cable's
>
Dan Ritter writes:
> Pankaj Jangid wrote:
>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>> facing a very strange problem. The monitor goes blank for a brief time,
>> like 1-2s and then comes back. It is connected with the GPU using HDMI
>> cable.
>>
>> During that 1-2s,
Bijan Soleymani writes:
> On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file
> any bug report till I have some concrete data. So
>> my question is - how do I diagnose such an issue and produce some data
>> for debugging. So that I can hand it over to maintainers.
>
> This one lin
David Wright writes:
> On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
>> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
>> facing a very strange problem. The monitor goes blank for a brief time,
>> like 1-2s and then comes back. It is connected with the GPU using
Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
>
> During that 1-2s, the machine response is fine.
On Thu, 27 Jan 2022, Vincent Lefevre wrote:
On 2022-01-27 11:41:44 +0100, Vincent Lefevre wrote:
On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-
On 2022-01-27 11:41:44 +0100, Vincent Lefevre wrote:
> On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
> > Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> > facing a very strange problem. The monitor goes blank for a brief time,
> > like 1-2s and then comes back. It is conne
On 2022-01-27 10:05:16 +0530, Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
I had a similar proble
On 2022-01-27 11:16, Bijan Soleymani wrote:
On 2022-01-27 5:00 a.m., hdv@gmail wrote:
My guess is about once every week. The display is on for roughly 16
hours each day. There seems to be no discernable relation to "load".
At least not that I could confirm. I haven't found a link to a
specific
On 2022-01-27 5:00 a.m., hdv@gmail wrote:
My guess is about once every week. The display is on for roughly 16
hours each day. There seems to be no discernable relation to "load". At
least not that I could confirm. I haven't found a link to a specific
application either. This system is a general
emory is corrupt as soon as I can. Who knows?
Maybe I am using HDMI after all.
Two other cases:
https://www.reddit.com/r/AMDHelp/comments/o1r0y9/screen_goes_to_black_randomly_while_gaming_rx_570/
That one says upgrading the power supply fixed it.
https://forums.tomshardware.com/threads/s
cases:
https://www.reddit.com/r/AMDHelp/comments/o1r0y9/screen_goes_to_black_randomly_while_gaming_rx_570/
That one says upgrading the power supply fixed it.
https://forums.tomshardware.com/threads/screen-goes-black-for-3-5-seconds-then-goes-back.3397019/
This one said they had the card replaced
On 2022-01-27 4:06 a.m., hdv@gmail wrote:
You are not the only one. I see the exact same here. The system this
happens on has an RX560 graphics card. I have been seeing these
blackouts from the start on this configuration (more than 2 years now).
Interesting, I just checked and it turns out I
On 2022-01-27 05:35, Pankaj Jangid wrote:
Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-2s and then comes back. It is connected with the GPU using HDMI
cable.
During that 1-2s, the machine respons
width
so:
resize -s 24 80
Also adding this:
termcapinfo xterm WS=\E[8;%d;%dt
to:
/etc/screenrc
Allows screen to resize the putty session (with the :width and :height
commands).
But when quitting/restarting screen it puts the putty and the screen session
back to the original size.
Thanks
On Wed, 26 Jan 2022, Bijan Soleymani wrote:
On 2022-01-26 1:45 p.m., Tim Woodall wrote:
I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.
Therefore I run screen so after reconnecting I can recover to
On 2022-01-26 11:35 p.m., Pankaj Jangid wrote> I don’t want to file any
bug report till I have some concrete data. So
my question is - how do I diagnose such an issue and produce some data
for debugging. So that I can hand it over to maintainers.
This one line script will sleep for 0.01 seconds
On Thu 27 Jan 2022 at 10:05:16 (+0530), Pankaj Jangid wrote:
> Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
> facing a very strange problem. The monitor goes blank for a brief time,
> like 1-2s and then comes back. It is connected with the GPU using HDMI
> cable.
>
> During t
Since I have setup a new hardware - x570 chipset, rx570 GPU - I am
facing a very strange problem. The monitor goes blank for a brief time,
like 1-2s and then comes back. It is connected with the GPU using HDMI
cable.
During that 1-2s, the machine response is fine. Whatever I type during
that time
:
termcapinfo xterm WS=\E[8;%d;%dt
to:
/etc/screenrc
Allows screen to resize the putty session (with the :width and :height
commands).
But when quitting/restarting screen it puts the putty and the screen
session back to the original size.
Bijan
On 2022-01-26 5:42 p.m., Bijan Soleymani wrote:
As far as I know this is not a screen feature. Putty controls the window
size, it is determined by the default or whatever is saved for that
session. You can change what happens when you resize the putty window on
the machine running putty. There
On 2022-01-26 1:45 p.m., Tim Woodall wrote:
I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.
Therefore I run screen so after reconnecting I can recover to whereever
I was at.
However, the PuTTY window does
On Mi, 26 ian 22, 18:45:41, Tim Woodall wrote:
> I have to use PuTTY to connect to a debian server. For reasons that are
> outwith my control the ssh session disconnects every 24 hrs.
>
> Therefore I run screen so after reconnecting I can recover to whereever
> I was at.
>
&g
I have to use PuTTY to connect to a debian server. For reasons that are
outwith my control the ssh session disconnects every 24 hrs.
Therefore I run screen so after reconnecting I can recover to whereever
I was at.
However, the PuTTY window does not resize to whatever it was previously.
I can
"Andrew M.A. Cater" writes:
> On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
>> I am currently running Debian 10.
>>
>> sudo lspci|grep VGA
>> 01:05.0 VGA compatible controller: Advanced Micro Devices,
>> Inc. [AMD/ATI] RS780 [Radeon
On Sat, Jan 08, 2022 at 06:52:32PM +, Richmond wrote:
> I am currently running Debian 10.
>
> sudo lspci|grep VGA
> 01:05.0 VGA compatible controller: Advanced Micro Devices,
> Inc. [AMD/ATI] RS780 [Radeon HD 3200]
>
> sudo xrandr
>
> Screen 0: minimum 320 x 200,
I am currently running Debian 10.
sudo lspci|grep VGA
01:05.0 VGA compatible controller: Advanced Micro Devices,
Inc. [AMD/ATI] RS780 [Radeon HD 3200]
sudo xrandr
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 8192 x 8192
VGA-0 connected primary 1440x900+0+0 (normal left inverted
Hi there,
How to setup setup on screen keyboard on LXDM? I added /usr/bin/florence
to /etc/lxdm/LoginReady unfortunately, in the /var/log/lxdm.log I get:
(florence:2825): Gtk-WARNING **: 14:21:06.181: cannot open display: :0
Florence version 0.6.3
Any suggestions?
On 11/20/21, Dan Ritter wrote:
> riveravaldez wrote:
>> Hi,
>>
>> I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
>> and I need to rotate the display (both physically and GUI)
>> which I do with:
>>
>> $ xrandr --output LVDS-1 --rotate inverted
>>
>> But then the input (trackpad/mouse, st
Le sam. 20 nov. 2021 à 13:03, Dan Ritter a écrit :
> riveravaldez wrote:
> > Hi,
> >
> > I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
> > and I need to rotate the display (both physically and GUI)
> > which I do with:
> >
> > $ xrandr --output LVDS-1 --rotate inverted
> >
> > But then
easons. The xinput is extracted from
my bin/xinput-xsession, which itself is called from .xsession
because keeping it separate allows you to call it at any time,
nut just when X starts.
Anyway, they're both attached, lightly anonymised, The
reference to viewports may only make sense if you use fvwm
riveravaldez wrote:
> Hi,
>
> I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
> and I need to rotate the display (both physically and GUI)
> which I do with:
>
> $ xrandr --output LVDS-1 --rotate inverted
>
> But then the input (trackpad/mouse, stylus, touchscreen, etc.)
> doesn't rota
Hi,
I'm on Debian 11 in a ThinkPad X220 Tablet (convertible)
and I need to rotate the display (both physically and GUI)
which I do with:
$ xrandr --output LVDS-1 --rotate inverted
But then the input (trackpad/mouse, stylus, touchscreen, etc.)
doesn't rotate accordingly, so it gets unusable...
I
Thanks all, I have changed the source.list
I need to reboot the computer but I'm still waiting for some jobs to finish
before I can reboot.
Thanks all, lina
On Fri, Oct 22, 2021 at 5:12 PM David Wright
wrote:
> On Fri 22 Oct 2021 at 11:40:28 (+0200), lina wrote:
> > # dmesg | grep -i nouveau
>
On Fri 22 Oct 2021 at 11:40:28 (+0200), lina wrote:
> # dmesg | grep -i nouveau
> [1.656164] fb0: switching to nouveaufb from EFI VGA
> [1.656250] nouveau :01:00.0: vgaarb: deactivate vga console
> [1.657164] nouveau :01:00.0: NVIDIA GK208B (b06070b1)
> [1.766995] nouveau 00
On Fri, Oct 22, 2021 at 11:55:12AM +0200, Jerome BENOIT wrote:
> My mistake, you are using the stable Debian:
> you may replace the buster-backports by bullseye-backports
If she's running bullseye (or trying to do so), she'll need to change
the security line as well. It's still in the old "buste
On Fri, Oct 22, 2021 at 11:38:56AM +0200, lina wrote:
> ## Debian Main Repos
> deb http://deb.debian.org/debian/ stable main contrib non-free
> deb-src http://deb.debian.org/debian/ stable main contrib non-free
>
> deb http://deb.debian.org/debian/ stable-updates main contrib non-free
> deb-sr
Hans wrote:
> Am Freitag, 22. Oktober 2021, 11:38:56 CEST schrieb lina:
> If you do not want to use the nvidia-drivers, then make sure, the driver
> correct GPU is adressed. There are sometimes notebooks with 2 graphics cards:
> one is built within the cpu (especially intel and amd), and the oth
able to force things.
When you have got a blank screen only at boot time but then it is ok when
starting X, then two reasons might be reponsible: 1. Your graphics card or
mnonitor can not switch to vesa-mode (this problem appeared at my system), or
your monitor can not work the choosen resolution
> (crit = +94.8°C)
> >
> > nouveau-pci-0100
> > Adapter: PCI adapter
> > GPU core: 912.00 mV (min = +0.80 V, max = +1.19 V)
> > temp1: +34.0°C (high = +95.0°C, hyst = +
My mistake, you are using the stable Debian:
you may replace the buster-backports by bullseye-backports
Jerome
On 22/10/2021 11:47, Jerome BENOIT wrote:
Hi Lina,
your Debian is actually the old-stable (Buster).
You may consider to upgrade to the new stable (Bullseye)
since you seem to use recen
+62.6°C
> > > Tccd1: +45.2°C
> > > Tccd2: +62.8°C
> > > Tccd3: +60.8°C
> > > Tccd4: +45.8°C
> > > Tccd5: +43.8°C
> > > Tccd6: +45.2°C
> > > Tccd7:
you boot on Windows/MacOS to see if the
> same thing happens ?
> > Knowing your hardware may help a lot.
> > hth,
> > Jerome
> >
> > On 21/10/2021 10:51, lina wrote:
> > > k10temp-pci-00c3
> > > Adapter: PCI adapter
> >
decodeassists pausefilter pfthreshold
> avic
> > v_vm
> > save_vmload vgif umip rdpid
> overflow_recov
> > succ
> > or smca
> >
> >
> > On Thu, Oct 21, 2021 at 11:04 AM J
aca...@einval.com> <mailto:amaca...@einval.com
<mailto:amaca...@einval.com>>> wrote:
>
> On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > Hi all,
> >
> > After using the computer fo
c3
> > > Adapter: PCI adapter
> > > Tctl: +62.6°C
> > > Tdie: +62.6°C
> > > Tccd1:+45.2°C
> > > Tccd2: +62.8°C
> > > Tccd3:+60.8°C
> > > Tccd4:+45.8°C
> > > Tc
(emerg = +135.0°C, hyst = +5.0°C)
> >
> > On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater <mailto:amaca...@einval.com>> wrote:
> >
> > On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > > Hi all,
> > >
> aptitude full-upgrade - you shouldn't see those sorts of inconsistencies.
>
> Bullseye - Debian 11 - OK.
>
> Temperature issue - only thinking that if it was something that only
> happens after a long time, it might be because a componetn inside your
> screen warms up / misbeh
= +5.0°C)
(emerg = +135.0°C, hyst = +5.0°C)
On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater mailto:amaca...@einval.com>> wrote:
On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> Hi all,
>
> After using the computer for a long while,
those sorts of inconsistencies.
Bullseye - Debian 11 - OK.
Temperature issue - only thinking that if it was something that only
happens after a long time, it might be because a componetn inside your
screen warms up / misbehaves.
Does anything else happen just before it all locks up?
All the very
)
(emerg = +135.0°C, hyst = +5.0°C)
On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater
wrote:
> On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > Hi all,
> >
> > After using the computer for a long while, my screen will blink.
> >
> >
issue?
On Wed, Oct 20, 2021 at 3:22 PM Andrew M.A. Cater
wrote:
> On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> > Hi all,
> >
> > After using the computer for a long while, my screen will blink.
> >
> > It has been months since the last time I upgraded
On Wed, Oct 20, 2021 at 02:42:11PM +0200, lina wrote:
> Hi all,
>
> After using the computer for a long while, my screen will blink.
>
> It has been months since the last time I upgraded the system.
>
> I don't know how to start checking, every time I have to reboot
Hi all,
After using the computer for a long while, my screen will blink.
It has been months since the last time I upgraded the system.
I don't know how to start checking, every time I have to reboot the
computer,
would be great to get your advice,
thanks,
On Saturday 02 October 2021 16:02:52 Brian wrote:
> On Sat 02 Oct 2021 at 15:43:33 -0400, Gene Heskett wrote:
> > On Saturday 02 October 2021 11:13:09 Brian wrote:
> > > On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote:
> > > > On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:
> > >
Anyone tried ansifilter -i bash.1 -o bash.2 yet?
On Sat, 2 Oct 2021, Gene Heskett wrote:
> On Saturday 02 October 2021 11:13:09 Brian wrote:
>
> > On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote:
> > > On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:
> >
> > [...]
> >
> > > > We
On Sat 02 Oct 2021 at 15:43:33 -0400, Gene Heskett wrote:
> On Saturday 02 October 2021 11:13:09 Brian wrote:
>
> > On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote:
> > > On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:
> >
> > [...]
> >
> > > > We still don't know why you want th
On Saturday 02 October 2021 11:13:09 Brian wrote:
> On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote:
> > On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:
>
> [...]
>
> > > We still don't know why you want this. I guess we'll never know.
> >
> > We apparently don't speak the same d
On Sat 02 Oct 2021 at 16:51:59 +0100, Eric S Fraga wrote:
> On Saturday, 2 Oct 2021 at 15:39, Brian wrote:
> > BTW, I do not think gv accepts an output piped to it.
>
> Well, it does on my Debian system. YMMV, of course.
>
> I did try the command before posting. ;-)
Eyesight. Many apologies.
On Saturday, 2 Oct 2021 at 15:39, Brian wrote:
> BTW, I do not think gv accepts an output piped to it.
Well, it does on my Debian system. YMMV, of course.
I did try the command before posting. ;-)
--
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.0
On Saturday, 2 Oct 2021 at 09:03, Greg Wooledge wrote:
> This appears to produce a Postscript stream.
Yes; I was basing my post on the specified need for "dead wood" output.
--
Eric S Fraga via Emacs 28.0.60 & org 9.5 on Debian 11.0
On Fri 01 Oct 2021 at 17:32:37 -0400, Gene Heskett wrote:
> On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:
[...]
> > We still don't know why you want this. I guess we'll never know.
>
> We apparently don't speak the same dialect of english Greg. I wanted a
> dead tree (aka paper) cop
; > gunzip -c /usr/share/man/man1/chmod.1.gz | groff -man | lp
> >
> > (or replace "lp" with "gv -" to see on screen).
>
> This appears to produce a Postscript stream. I'm pretty sure that isn't
> what Gene wanted (but who knows, since the ques
lace "lp" with "gv -" to see on screen).
This appears to produce a Postscript stream. I'm pretty sure that isn't
what Gene wanted (but who knows, since the question was apparently "how
do I save a man page's text, without markup, into a file" and the
On Sat, Oct 02, 2021 at 07:23:45AM -0400, Gene Heskett wrote:
> On Friday 01 October 2021 22:52:59 David Wright wrote:
> > Like others, I tried to guess what Gene really wanted (I can barely
> > believe the answer) and to come up with a suitable method. I also
> > tried out others' suggestions. We
quot;lp" with "gv -" to see on screen).
>
> Replace chmod with specific command and note that there is a different
> folder for each section of the Unix manual, man1 being for commands,
> man2 for system libraries, ...
>
> troff is how us old-timers used to write before
man pages are written in troff/nroff (which can be compiled using groff)
using the man style. You can do the following, for instance:
gunzip -c /usr/share/man/man1/chmod.1.gz | groff -man | lp
(or replace "lp" with "gv -" to see on screen).
Replace chmod with specific c
On Friday 01 October 2021 22:52:59 David Wright wrote:
> On Fri 01 Oct 2021 at 20:53:26 (-0400), Greg Wooledge wrote:
> > On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> > > man command | col -b > command.txt
> >
> > Curious.
> >
> > unicorn:~$ man ls > ls1
> > unicorn:~$ man ls | col -b >
On Friday 01 October 2021 20:53:26 Greg Wooledge wrote:
> On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> > man command | col -b > command.txt
>
> Curious.
>
> unicorn:~$ man ls > ls1
> unicorn:~$ man ls | col -b > ls2
> unicorn:~$ ls -l ls1 ls2
> -rw-r--r-- 1 greg greg 8299 Oct 1 20:49 l
On Friday 01 October 2021 20:44:41 Fred wrote:
> On 10/1/21 1:59 PM, Gene Heskett wrote:
> > On Friday 01 October 2021 12:34:16 Larry Martell wrote:
> >
> > man -t /path/to/man/file >file.txt
> > groff -mandoc /path/to/man/file > file.txt, both quadrupled the size
> > with lots more markup.
> >
>
e a care what the
width of your window is set to. Too narrow and you get hyphena‐
tion hell; too wide and you have to shrink it down to fit the paper.
$ man -t man > /tmp/man.txt (wrong)
$ man -t man > /tmp/man.ps
Good for people who still have a PostScript workflow.
Myself, I prefer
On Fri, Oct 01, 2021 at 05:44:41PM -0700, Fred wrote:
> man command | col -b > command.txt
Curious.
unicorn:~$ man ls > ls1
unicorn:~$ man ls | col -b > ls2
unicorn:~$ ls -l ls1 ls2
-rw-r--r-- 1 greg greg 8299 Oct 1 20:49 ls1
-rw-r--r-- 1 greg greg 7745 Oct 1 20:49 ls2
Glancing at the diff -u
On 10/1/21 1:59 PM, Gene Heskett wrote:
On Friday 01 October 2021 12:34:16 Larry Martell wrote:
man -t /path/to/man/file >file.txt
groff -mandoc /path/to/man/file > file.txt, both quadrupled the size with
lots more markup.
Not what I want obviously.
Thanks Larry.
Cheers, Gene Heskett.
man c
On Friday 01 October 2021 17:17:53 Greg Wooledge wrote:
> On Fri, Oct 01, 2021 at 05:05:44PM -0400, Gene Heskett wrote:
> > On Friday 01 October 2021 12:43:00 Cindy Sue Causey wrote:
> > > man lilo > manLILO
> >
> > did exactly what I wanted it to do. Thank you Cindy. ;o)
>
> On Fri, Oct 01, 2021
On Fri, Oct 01, 2021 at 05:21:54PM -0400, Gene Heskett wrote:
> What I wanted on dead tree, was exactly what I see on screen.
> With the manpage markup gobbled up, leaving only the text I see on screen
> when I type man 9 filename.
So you wanted to print a man page on paper, but you
201 - 300 of 4563 matches
Mail list logo
