From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by lists01.pubmisc.prod.ext.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id v0K4gQ8D008326 for ; Thu, 19 Jan 2017 23:42:26 -0500 Received: from mx1.redhat.com (ext-mx05.extmail.prod.ext.phx2.redhat.com [10.5.110.29]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v0K4gQg8004860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 19 Jan 2017 23:42:26 -0500 Received: from server2.shellworld.net (server2.shellworld.net [66.172.12.120]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 7A4E11555C for ; Fri, 20 Jan 2017 04:42:25 +0000 (UTC) Received: by server2.shellworld.net (Postfix, from userid 1005) id 263C78C048F; Fri, 20 Jan 2017 04:42:30 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by server2.shellworld.net (Postfix) with ESMTP id 237C68C00DC for ; Thu, 19 Jan 2017 23:42:30 -0500 (EST) Date: Thu, 19 Jan 2017 23:42:30 -0500 (EST) From: Karen Lewellen To: Linux for blind general discussion Subject: Re: A challenging question? In-Reply-To: <20170119211203.2b42c1b3@bigbox.christie.dr> Message-ID: References: <20170119211203.2b42c1b3@bigbox.christie.dr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Delayed for 02:22:08 by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 20 Jan 2017 04:42:25 +0000 (UTC) X-Greylist: inspected by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Fri, 20 Jan 2017 04:42:25 +0000 (UTC) for IP:'66.172.12.120' DOMAIN:'server2.shellworld.net' HELO:'server2.shellworld.net' FROM:'klewellen@shellworld.net' RCPT:'' X-RedHat-Spam-Score: 0.501 (BAYES_99, BAYES_999, RP_MATCHES_RCVD) 66.172.12.120 server2.shellworld.net 66.172.12.120 server2.shellworld.net X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 X-Scanned-By: MIMEDefang 2.78 on 10.5.110.29 X-loop: blinux-list@redhat.com X-BeenThere: blinux-list@redhat.com X-Mailman-Version: 2.1.12 Precedence: junk Reply-To: Linux for blind general discussion List-Id: Linux for blind general discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2017 04:42:27 -0000 Hi folks, I do wonder if we have tmox at shellworld. Actually, the printer friendly edition of emails at google will produce fine text, and yes I can save the file with the p function. The challenge is, since this is court evidence, I must gather likely a couple hundred of them. Something to petition the judge regarding. Thanks for the ideas, Kare On Thu, 19 Jan 2017, Tim Chase wrote: > On January 19, 2017, Karen Lewellen wrote: >> Asking just in case there is a simple tool for this process. >> I need to capture several emails from my gmail account. It is >> critical that the e-mails appear, as they do for me, not how they >> might in standard view, i. e. with alt tags visible for anyone. >> Lynx, links, and e-links are the browsers I wish to use for this, I >> would imagine the alt tag would be different even if I had access >> to say Firefox. > > Depending on the target audience, a couple ways come to mind: > > 1) In lynx-the-cat, use the "p" command to print to a file. This is > basically the same thing as doing a "lynx -dump" on a page. In > links-the-chain and elinks, you can use "File, Save formatted > document" to get the same sort of results. > > 2) use your terminal emulator's copy/paste functionality to select > the content of the gmail session in lynx/links/elinks session > > 3) fire up GNU screen or tmux, launch Lynx inside, browse to your > email, and then use the "scrollback" functionality in screen/tmux to > copy text off the screen into a buffer, then use the screen/tmux > scrollback-paste functionality to dump it into a file. > > 4) use the "script" program to record the entire session with > timings: > > $ script --timing=gmail.timings gmail.script > $ lynx https://gmail.com > (do your thing) > $ exit # leaves the "script" recording session > > this will give you two files "gmail.timings" and "gmail.script" which > you can then play back with > > $ scriptreplay gmail.timings gmail.script > > Now on to comparing: > > #1 is easiest choice with some of the best results for the use-case > you are describing. > > #2 & #3 are basically a screen capture of the text that you can dump > into a text file, but don't include any coloration or playback (like > #1). Also, these usually end up being one screen at a time with > full-screen curses applications like lynx/links/elinks, so if your > text is more than one page, it's a bit annoying to capture, save, > scroll, capture, save, repeat. But they do work for any terminal > application, not just relying on browser-specific functionality. > > #4 gives an exact replay of the options, but requires a terminal that > understands it. If you're playing back on the same terminal where > you recorded, this has no issues. But if you're trying to share it, > there may be hurdles involved. Also, while a quick test here > suggests that script doesn't capture passwords in certain modes, it > might if recording a lynx/links session, so I'd either only share it > with someone you trust with your gmail password, or redact the file > before sharing it. > > And if you haven't had a chance to play with screen/tmux, they're > incredibly powerful and well worth the investment of time (I > personally prefer and recommend tmux, but both are substantially > similar to the end user). > > As usual, my verbose replies are likely overkill, but hopefully give > you some options to explore. (grins) > > -tim > > > > > > > > _______________________________________________ > Blinux-list mailing list > Blinux-list@redhat.com > https://www.redhat.com/mailman/listinfo/blinux-list > >