From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [off-topic] E-readers and Org-Mode
Date: Fri, 28 Oct 2022 00:20:46 +0700 [thread overview]
Message-ID: <tjeelg$b9d$1@ciao.gmane.io> (raw)
In-Reply-To: <CAFdBzEq++gHNL3QXVuEMa8ntDqNC16Ny36CkoRr=cnMK2vfVdA@mail.gmail.com>
I am impressed, but I still believe that UI optimized for e-ink may be
more convenient for specific tasks involving org files than generic
Emacs build for Android. Perhaps conversion of handwritten notes to text
should be delegated to a laptop or a PC.
On 25/10/2022 23:59, Ken Mankoff wrote:
> See also Dasung NotEReader. Full Android tablet, no lockdown like the
> ReMarkable. Looks fast - can watch YouTube videos for example. If it's
> really full Android, then it should be able to install and run emacs
> natively. 10.3 or 7.8 inch versions.
I see that definitely it is possible, but I am unsure it is more
convenient than OLED or LCD tablet. 4 regimes for screen is an indicator
of some complications. Choice of Android may be a way to avoid
development of custom UI. I have not checked if it is possible to build
custom Android variant, unlock bootloader and still get comparable
performance.
Where was a period when LCD monitors were slow in comparison to CRT ones
and people complained concerning annoying trails on dynamic images...
> On Tue, Oct 25, 2022, 08:27 Fraga, Eric wrote:
>
> On Tuesday, 25 Oct 2022 at 21:37, Max Nikulin wrote:
> > E-ink displays are slow (my device was manufactured 15 years ago
..
> E-ink displays are getting significantly faster, with some claiming 60
> Hz refresh rates (cf. the PineNote). Often, however, they are tied to
> low power and low performance processors given their use case: mostly
> reading with some annotations.
There is no reason to install high performance CPU if the goal is to get
time between battery charging noticeably longer that for regular
gadgets. Highest refresh rate means 5W power consumption in the case of
PineNote.
It is not apparent for not-ereader, but I see the same black and back
flickering magic to fight with ghosts and to achieve uniform background
with high contrast on remarkable. My impression is that change in time
to pass whole cycle is not dramatic. Likely long enough pause is
necessary to let particles orientation to settle.
next prev parent reply other threads:[~2022-10-27 17:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-23 15:16 [off-topic] E-readers and Org-Mode Juan Manuel Macías
2022-10-24 7:09 ` Fraga, Eric
2022-10-24 11:50 ` Juan Manuel Macías
2022-10-24 15:30 ` Fraga, Eric
2022-10-24 16:42 ` Jeffrey DeLeo
2022-10-24 17:16 ` Fraga, Eric
2022-10-24 18:34 ` Juan Manuel Macías
2022-10-25 7:57 ` Fraga, Eric
2022-10-25 12:55 ` Juan Manuel Macías
2022-10-25 13:59 ` Fraga, Eric
2022-10-26 13:31 ` L.C. Karssen
2022-10-26 14:00 ` Quiliro Ordóñez
2022-10-26 16:27 ` Fraga, Eric
2022-10-29 9:03 ` Juan Manuel Macías
2022-10-25 11:06 ` Eduardo Suarez-Santana
2022-10-25 14:03 ` Fraga, Eric
2022-10-25 14:37 ` Max Nikulin
2022-10-25 15:21 ` Fraga, Eric
2022-10-25 16:59 ` Ken Mankoff
2022-10-27 17:20 ` Max Nikulin [this message]
2022-10-27 17:53 ` Juan Manuel Macías
2022-10-28 4:40 ` Ihor Radchenko
2022-10-29 12:54 ` Max Nikulin
2022-10-31 12:18 ` Juan Manuel Macías
-- strict thread matches above, loose matches on Subject: below --
2022-10-23 16:29 Ypo
2022-10-24 7:12 Pedro Andres Aranda Gutierrez
2022-10-24 14:11 ` Juan Manuel Macías
2022-10-25 14:44 Payas Relekar
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='tjeelg$b9d$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).