From: Carlos Sosa <gnusosa@gnusosa.net>
To: emacs-orgmode@gnu.org
Subject: Re: Working on iPad Pro
Date: Sat, 06 Feb 2016 22:38:51 -0800 [thread overview]
Message-ID: <87fux5m3d0.fsf@gnusosa.net> (raw)
In-Reply-To: 56AE6B79.1000508@pfdstudio.com
Peter Davis <pfd@pfdstudio.com> writes:
> For now, this seems an adequate, though not ideal, solution. I'll have
> to use it more to see how well it works for authoring blog posts.
>
> One irksome limitation of any ssh solution is that I can't just export
> my org files to HTML and preview the results automatically. I'm sure
> I'll find other issues as I start using this workflow more heavily.
I might be a little bit late, but I will like to add my input on the
experience with the semi-remote terminal experience with Emacs.
I make use of Emacs in 4 machines that I keep in-sync with a mix of
git and git-annex. I would recommend git-annex for your newsrc files
and your org-mode files. One of this machines is a Chromebook, that is
not run in developer mode, this means I don't have a typical Unix
machine. Because of that restriction, I make use of mosh to connect to
one of my "boxes" that has Emacs running. So everything I
export/publish in one of this "boxes", has to be served by an HTTP
server. That's how I overcome the restriction of the documents
preview. Since the Chromebook already has a working browser, having a
terminal that's able to copy/paste between the terminal (ssh/mosh) and
the browser is crucial. I would say that's how I read my feeds from
Gnus and other elements that can be rendered through Emacs on a
terminal.
The key is to be able to synchronize your "Emacs box" files and your
Terminal(IPad, Tablet, Chromebook...) files, and to be able to copy/paste
between both. I know of a friend that writes everything in org-mode in
his tablet, and later pushes the content to his "Emacs box" were he
renders, and later exports the final document.
I'm about to try out a similar setup like the Kangaroo PC but with the
Beaglebone Black. I've haven't had a problem with Emac's performance on
different sizes machines, more CPUs, less CPUs, it really hasn't
matter, it's more about the lantency of your network.
prev parent reply other threads:[~2016-02-07 6:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 17:27 Working on iPad Pro Peter Davis
2016-01-31 17:51 ` Ido Magal
2016-01-31 17:52 ` John Hendy
2016-01-31 17:54 ` John Hendy
2016-01-31 19:51 ` Ido Magal
2016-01-31 20:15 ` Peter Davis
2016-02-07 6:38 ` Carlos Sosa [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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fux5m3d0.fsf@gnusosa.net \
--to=gnusosa@gnusosa.net \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).