public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: blinux-list at redhat.com (Linux for blind general discussion)
Subject: screen in Ubintu shell question?
Date: Sun, 2 Oct 2022 17:06:44 -0400 (EDT)	[thread overview]
Message-ID: <mailman.4825.1664744808.6081.blinux-list@redhat.com> (raw)
In-Reply-To: <mailman.4860.1664744302.6080.blinux-list@redhat.com>

Hi,
no idea what the gnu is about..at all.
still, I discovered my error.
My source for the command added a dash, which I was typing before the 
letter  h.
Once I stopped doing that the hardcopy process began, allowing me to 
capture.
Thanks, problem solved.
Kare



On Sun, 2 Oct 2022, Linux for blind general discussion wrote:

> On 2022-10-02 16:33, Linux for blind general discussion wrote:
>> There is a reason why I want to use links the chain here, documenting a
>> dreamhost issue for dreamhost instead of shellworld.
>> Still your wisdom is sound.
>> now, if I can just get the hardcopy creation process to work.
>
> It should work with any interactive program that waits for
> user-interaction.  While it's waiting, you hit GNU-screen's prefix
> key (control+a) and then the letter "h" to indicate you want a
> hardcopy of the screen.  It should save that to a file in the current
> directory called "hardcopy.0" (I think if you do more than one of
> them, it numbers them sequentially).  You can continue to use the
> program as normal (possibly taking multiple screen-captures as you
> perform various actions) and then when you quit, GNU screen quits
> too.
>
> Alternatively, you can launch GNU screen, which puts you in a
> sub-shell inside screen.  You can then launch multiple programs
> (either each in their own screen window, or serially) just as you
> normally would, using the <prefix>h to capture a hardcopy of the
> screen to a file.
>
> -Tim
>
>
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list at redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
>


      reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 blinux-list
 ` blinux-list
   ` blinux-list
     ` blinux-list
       ` blinux-list [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mailman.4825.1664744808.6081.blinux-list@redhat.com \
    --to=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).