From: Joakim Hove <hove@bccs.no>
Subject: Re: elisp problem!
Date: Wed, 04 Feb 2004 13:58:18 +0100 [thread overview]
Message-ID: <4yu12757dh.fsf@skjellgran.ii.uib.no> (raw)
In-Reply-To: mailman.1826.1075842117.928.help-gnu-emacs@gnu.org
"hans nieuwenhuizen" <hans@nieuwenhuizen-jk.nl> writes:
> Dear Sirs,
> [...] how to solve this, or --- better --- hear what books may contain
Well, first of all it is less than clear what you want to solve. When
asking for help on a forum like this you should try to formulate a
minimal version of your problem.
> but the best I an do is build ( as shown ) a 126 items Vector and extract element [row][column] as [ 6 * row + column].
> (** `(aref (( aref Filetypes [row] )) [column] )` is flagged as error **)
It seems you are trying to push C-throughts down the throat of the
lisp interpreter. Lisp has much more flexible lists (and builtin
hashes could be maybe be usefull).
> ;;; Find type of file
> (search-forward "Filename")
> (re-search-forward "\\.\\(\\w*\\)$") ;;; (setq postfix "\\1") THIS DOES NOT WORK. Copy One after the other?
I would heavily recommend a function like
(defun getheader (header)
...
)
returns the value of the header "header", or nil if it does not exist.
> Where can I find the needed info?
Well it is all in the manual - but you seem to have started out on a
quite ambitious project. Maybe start with something simpler.
Joakim
--
/--------------------------------------------------------------------\
/ Joakim Hove / hove@bccs.no / (55 5) 84076 | \
| Unifob AS, Avdeling for Beregningsvitenskap (BCCS) | Stabburveien 18 |
| CMU | 5231 Paradis |
\ Thormøhlensgt.55, 5020 Bergen. | 55 91 28 18 /
\--------------------------------------------------------------------/
next parent reply other threads:[~2004-02-04 12:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1826.1075842117.928.help-gnu-emacs@gnu.org>
2004-02-04 12:58 ` Joakim Hove [this message]
2004-02-05 9:02 ` elisp problem! Kai Grossjohann
2004-02-03 21:00 hans nieuwenhuizen
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=4yu12757dh.fsf@skjellgran.ii.uib.no \
--to=hove@bccs.no \
/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).