unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>,
	Will Monroe <wtmonroe.ls@gmail.com>,
	help-gnu-emacs@gnu.org
Subject: RE: Advice on troubleshooting function to "unscroll"
Date: Sun, 25 Jan 2015 17:06:57 -0800 (PST)	[thread overview]
Message-ID: <c1cf1236-da66-43e1-9580-075830fedc06@default> (raw)
In-Reply-To: <87ppa2flao.fsf@wmi.amu.edu.pl>

> meant to ask (more or less) "why weren't the Emacs Devs satisfied
> with scroll-up, which did work after all".

It was thought good to give users a choice (via option
`scroll-error-top-bottom') of what happens when a scrolling error
is raised.  I use the default value of the option (`nil'), so for
me the behavior is exactly the same as for command `scroll-up'.
But you might prefer an option value of `t'.

> I think we really need Sacha Chua to do an Emacs Chat with you.  I,
> personally, would love to learn a bit about your workflow and Emacs
> config.  (Not that I would necessarily like to copy it: I strongly
> disagree with you on the window/frame issue, for instance!)

Sorry.  I've told Sacha that there are tons of others to be
interviewed before and instead of me.  And I don't really have a
workflow.  And my config is pretty much the code I've made available
here and there.  I've used Emacs for a long time, but that doesn't
mean that I use it particularly well or in any particularly
interesting way.

In particular, I no longer develop software (apart from futzing
around with Emacs Lisp), so my use of Emacs is hardly helpful to
anyone wanting to program: most Emacs users and use cases.

I don't use Emacs for anything, apart from playing with Emacs.



  reply	other threads:[~2015-01-26  1:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25 20:52 Advice on troubleshooting function to "unscroll" Will Monroe
2015-01-25 21:35 ` Marcin Borkowski
2015-01-25 21:43   ` Will Monroe
2015-01-25 21:55     ` Marcin Borkowski
2015-01-25 22:01       ` Will Monroe
2015-01-25 21:45 ` Marcin Borkowski
2015-01-25 22:03   ` Will Monroe
2015-01-25 22:09     ` Marcin Borkowski
2015-01-25 22:45     ` Drew Adams
2015-01-25 22:56       ` Will Monroe
2015-01-25 23:15         ` Marcin Borkowski
2015-01-26  0:03         ` Drew Adams
2015-01-26  0:16           ` Marcin Borkowski
2015-01-26  1:06             ` Drew Adams [this message]
2015-01-26  1:17             ` Will Monroe
2015-01-26  1:21               ` Marcin Borkowski
2015-01-26  1:33               ` Drew Adams
     [not found] <mailman.18583.1422219396.1147.help-gnu-emacs@gnu.org>
2015-01-25 21:35 ` Joost Kremers
2015-01-25 21:57   ` Will Monroe

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=c1cf1236-da66-43e1-9580-075830fedc06@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    --cc=wtmonroe.ls@gmail.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).