unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: Loading local .emacs from remote machine
Date: 05 Feb 2003 17:04:32 +0100	[thread overview]
Message-ID: <x5ptq690j3.fsf@lola.goethe.zz> (raw)
In-Reply-To: Pine.LNX.4.44.0302050814320.16795-100000@heidegger.mousecar.net

gebser@ameritech.net writes:

> = > A string in elisp must be some really strange thing.
> = >
> = > (add-to-list 'tramp-shell-prompt-pattern "abc")
> = >

> = In Lisp, a general type is sequence.  Lists are one subtype of
> = sequence, and vectors are another.  Strings are vectors of characters.
> = 
> = add-to-list can only add to lists, not to arbitrary sequences.
> = 
> = Does this make sense?
> 
> Yes, thanks much.  It's not enough for me write all those gorgeous
> emacs apps I've been hankering to do, but, as said, I like progress.
> 
> I think I remember reading in a book or two that every|some (?) data
> type(s) in elisp contain(s) an element (including perhaps null... or
> nil... I forget, except there's a difference... I think) *and* the
> implication of a subsequent such element-- hence, a sequence.
> 
> That a string is a vector of characters (delimited by double quotes,
> yes?)

A string is basically a vector of characters.  It is not delimited by
double quotes: that is just the input/output syntax of strings, not
the strings themselves.  Strings are not exactly the same as vectors
of characters although very much behaving like the same and allowing
the same access methods: they have different I/O syntax, they can
represent only representable characters (and not key combinations like
M-x), they can carry text properties.

> is simple enough.  Is it also possible to have a list of characters?

Yes.

> If not, why not?  If so, how would it be structurally or
> functionally different or handled differently from a string?

Read the Elisp manual if you are interested in the Elisp data
structures.  No sense in retyping it here.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2003-02-05 16:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1406.1044395706.21513.help-gnu-emacs@gnu.org>
2003-02-04 23:30 ` Loading local .emacs from remote machine Kevin Rodgers
2003-02-05  0:38   ` gebser
2003-02-05  0:50     ` David Kastrup
2003-02-05 12:45       ` gebser
2003-02-05 12:37     ` gebser
2003-02-05 12:51 ` Kai Großjohann
2003-02-05 15:17   ` gebser
2003-02-05 16:04     ` David Kastrup [this message]
2003-02-05 17:06     ` Kevin Rodgers
     [not found] <mailman.1346.1044295047.21513.help-gnu-emacs@gnu.org>
2003-02-03 23:45 ` Kevin Rodgers
2003-02-04  1:08   ` gebser
2003-02-05 16:33     ` bigfaceworm
2003-02-05 19:09       ` gebser
2003-02-07 22:12       ` Brian Palmer
2003-02-04  6:39 ` Kai Großjohann
2003-02-04 16:35   ` gebser
2003-02-04 17:30     ` Kai Großjohann
2003-02-04 21:51       ` gebser
2003-02-06  7:44   ` Mac
2003-02-06 13:42     ` Kai Großjohann
2003-02-06 14:06       ` Glenn Morris
2003-02-06 15:12         ` Kai Großjohann
2003-02-06 15:42           ` Glenn Morris
2003-02-03 17:56 gebser

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=x5ptq690j3.fsf@lola.goethe.zz \
    --to=dak@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).