unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>
Cc: emacs-devel@gnu.org, Marcelo Toledo <marcelo@marcelotoledo.org>,
	miles@gnu.org
Subject: Re: arch-tag lines in tutorials.
Date: Fri, 15 Apr 2005 11:04:39 +0200	[thread overview]
Message-ID: <877jj4pg0o.fsf@xs4all.nl> (raw)
In-Reply-To: <fc339e4a050414160359089a79@mail.gmail.com> (Miles Bader's message of "Fri, 15 Apr 2005 08:03:46 +0900")

Miles Bader <snogglethorpe@gmail.com> writes:

> On 4/15/05, Marcelo Toledo <marcelo@marcelotoledo.org> wrote:
>> For a newbie user the arch tag and the local variables will be something
>> that he doesn't know about. I don't think that only this will fix the
>> problem of having not know things in the buffer. If we're going to think
>> about it I think we need to think about a convention and a global
>> solution.
>
> Is having things a newbie "doesn't know about" in the file actually
> harmful (especially considering, it's more or less just a text file,
> and this funny stuff is at the end)?
>
> Maybe it's actually _good_, in that it might might peak their
> curiousity, and make them aware (if often only peripherally) of a
> feature they might not have thought about otherwise.

I agree with you when it comes to local variables.  They must seem
strange to a new user.  But someone reading the tutorial wants to
learn about Emacs, so exposure to local variables is a good thing.

Arch-tag lines seem a bit too far off-topic to me, though.  (But I
don't think they are very harmful.)

Lute.

  reply	other threads:[~2005-04-15  9:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 12:00 arch-tag lines in tutorials Lute Kamstra
2005-04-14 20:34 ` Marcelo Toledo
2005-04-14 23:03   ` Miles Bader
2005-04-15  9:04     ` Lute Kamstra [this message]
2005-04-15 12:32       ` Miles Bader
2005-04-15 15:12     ` Richard Stallman

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=877jj4pg0o.fsf@xs4all.nl \
    --to=lute.kamstra.lists@xs4all.nl \
    --cc=emacs-devel@gnu.org \
    --cc=marcelo@marcelotoledo.org \
    --cc=miles@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.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).