unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: James Taylor <james@openmail.cc>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs for forums?
Date: Fri, 06 Jul 2018 17:35:23 -0600	[thread overview]
Message-ID: <87r2kg2b0k.fsf@openmail.cc> (raw)
In-Reply-To: 87va9s2o1p.fsf@openmail.cc

James Taylor <james@openmail.cc> writes:

> Hikaru Ichijyo <ichijyo@macross.sdf.jp> writes:
>
>> We just don't want to take on so much of this browser functionality that
>> Emacs starts to have some of the same security problems that big GUI
>> browsers tend to have.
>
> Oh, I completely agree with that concern. This would undoubtedly, if it
> ever happens, need to be a "bare minimum" approach that doesn't make
> Emacs an interesting target.
>
> One thought I had was to make a small external program (in a container,
> maybe?) that does nothing more than take the requested webpage and make
> it more palatable to Emacs, with the ability to update and change pages
> on demand and no direct route to Emacs' files from that external
> program. Maybe there could be editable fields that the external program
> sends in a text interface for Emacs, processes after editing, and pushes
> to the current forum site.
>
> Combining that with a password manager like pass that integrates with
> GPG might be interesting as well.
>
> Of course, I don't have the ability to do any of this, it's idle musing
> and no doubt reinventing the wheel in a lot of ways.

And not long after writing this, it occurred to me that what I was
suggesting was not, in any way, "small" if it has to parse Javascript
like that. :P Still, to keep Emacs away from all the heavy lifting is
probably on the right track.


  reply	other threads:[~2018-07-06 23:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 23:26 Emacs for forums? James Taylor
2018-07-03 23:48 ` HASM
2018-07-04  0:37   ` James Taylor
2018-07-05  0:53     ` Garreau, Alexandre
2018-07-05  3:25       ` Stefan Huchler
     [not found]       ` <mailman.3096.1530761126.1292.help-gnu-emacs@gnu.org>
2018-07-05  3:53         ` James Taylor
2018-07-05  4:57           ` Devin Prater
2018-07-05 20:01             ` Bob Newell
     [not found]             ` <mailman.3119.1530820926.1292.help-gnu-emacs@gnu.org>
2018-07-05 23:26               ` James Taylor
2018-07-05 23:37                 ` Skip Montanaro
2018-07-06  0:48                   ` Eric Abrahamsen
     [not found]                   ` <mailman.3129.1530838301.1292.help-gnu-emacs@gnu.org>
2018-07-06  2:47                     ` James Taylor
2018-07-06  5:27                       ` Eric Abrahamsen
     [not found]                       ` <mailman.3133.1530855048.1292.help-gnu-emacs@gnu.org>
2018-07-06 16:05                         ` Hikaru Ichijyo
2018-07-06 18:53                           ` James Taylor
2018-07-06 23:35                             ` James Taylor [this message]
2018-07-06 19:35                       ` Bob Newell
2018-07-06 19:59                         ` Eric Abrahamsen
2018-07-06  5:27                   ` tomas
     [not found]                   ` <mailman.3132.1530854845.1292.help-gnu-emacs@gnu.org>
2018-07-08 18:32                     ` Emanuel Berg
     [not found]     ` <mailman.3093.1530753915.1292.help-gnu-emacs@gnu.org>
2018-07-05  1:43       ` James Taylor
2018-07-05  2:02         ` Emanuel Berg
2018-07-05  2:57           ` Stefan Huchler
2018-07-05  3:07           ` James Taylor
     [not found]           ` <mailman.3095.1530759497.1292.help-gnu-emacs@gnu.org>
2018-07-05 12:56             ` Emanuel Berg
  -- strict thread matches above, loose matches on Subject: below --
2018-07-08  3:55 Jude DaShiell

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87r2kg2b0k.fsf@openmail.cc \
    --to=james@openmail.cc \
    --cc=help-gnu-emacs@gnu.org \
    /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).