11:05 p.m.
The original XEmacs 21.4.9 (Windows) had a problem which resulted from a bad
merge from vanilla XEmacs 21.4.9. This resulted in font-lock displaying
weird configurations of the progress guage. Also the website did not reflect
the new version, nor the CHANGES file. Both problems have now been fixed and
the version updated to 21.4.9-1. The original announcement follows.
* XEmacs 21.4.9 "Informed Management (Windows)" is released.
"Informed Management" is the ninth in the OXYMORON series.
XEmacs 21.4.9 "Informed Management (Windows)" is the fifth in a series of
MS-Windows focused releases of XEmacs. The intent of this release
series is to provide source and binary distributions of the XEmacs
21.4.x series with any additional fixes or enhancements necessary to
provide a pleasurable editing experience on the MS-Windows platform.
Source is available via cvs at cvs.xemacs.org. This release has the
release tag r21-4-9-windows and the most current snapshot will always
have the branch tag windows-21-4.
The binaries for both cygwin and native MS-Windows are available via
the XEmacs netinstaller which can be found at
http://www.xemacs.org/Download/win32/setup.exe This version of the
installer is 1.2.2.11.2.11.
Brief summary of Changes relative to vanilla 21.4.9
- Fix layout of widgets so that the search dialog works.
- Fix focus capture of widgets under X.
4:46 a.m.
New subject: test, please ignore
this is just to test that my messages are getting through. sorry for the
inconvenience
3:33 p.m.
New subject: primitive to fill a buffer
Hello,
Please excuse me if this is the wrong forum for this post. I'm
looking for help in coding primitives. If there is a better forum please
let me know.
I want to open a file with a parser written in C and fill a buffer
with those contents. I don't understand how to do this. I haven't found
any examples in the Xemacs Internals Manual. I briefly looked over
fileio.c, but it's so involved. Where should I start? Are there any
examples of this I could review?
Thanks,
Brian Willkie
2:02 a.m.
New subject: primitive to fill a buffer
On Wed, 28 Aug 2002, Brian Willkie wrote:
Please excuse me if this is the wrong forum for this post. I'm
looking
for help in coding primitives. If there is a better forum please let
me know.
I want to open a file with a parser written in C and fill a buffer
with those contents. I don't understand how to do this. I haven't
found any examples in the Xemacs Internals Manual. I briefly looked
over fileio.c, but it's so involved. Where should I start? Are there
any examples of this I could review?
Make your C parser a stand-alone executable that outputs it's results to
stdout.
Then look at `start-process' or something like that.
Daniel
--
Heu! Tintinnuntius Meus Sonat!
2:57 a.m.
New subject: primitive to fill a buffer
Thanks for the reply. Actually the parser already exists as part of a
stand-alone executable. It has been ported to many platforms including
Classic MacOS (which to the best of my knowledge does not support stdout).
Additionally, I eventually want to select parts of the buffer to pass to
the rest of the program (or process with elisp functions then pass on
etc), which I would also like to call as a primitive (incidentally the
other program is Csound, or a branch of it called icsound).
I want to combine the functionality of csound with Xemacs to create an IDE
for csound. Is this madness?
From the name of it I assume that file-name-handler-alist exists for
this
reason (ie to handle certain files differently from standard text files if
necessary). Am I wrong? If that is its purpose, how is it used?
For more info on Csound:
http://www.csounds.com/faq/index.html#INTRODUCTION
and icsound:
http://leporello.agnula.org/~maurizio/icsound/
On Thu, 29 Aug 2002, Daniel Pittman wrote:
Make your C parser a stand-alone executable that outputs it's
results to
stdout.
Then look at `start-process' or something like that.
Daniel
--
Heu! Tintinnuntius Meus Sonat!
3:26 a.m.
New subject: primitive to fill a buffer
On Wed, 28 Aug 2002, Brian Willkie wrote:
Thanks for the reply. Actually the parser already exists as part of
a
stand-alone executable. It has been ported to many platforms including
Classic MacOS (which to the best of my knowledge does not support
stdout).
*nod* I suspected that it might, but you never know.
Additionally, I eventually want to select parts of the buffer to
pass
to the rest of the program (or process with elisp functions then pass
on etc),
Sure. The simple `start-process' call runs a program as an asynchronous
subprocess of Emacs. You can have it put the output into a buffer or
call a Lisp function when something is written.
That buffer, then, can have anything done to it you want. If you want to
feed that back into the running process, that's pretty easy.
`process-send-string' is probably what you want there.
which I would also like to call as a primitive (incidentally the
other
program is Csound, or a branch of it called icsound).
Sure. I don't quite know what _you_ mean when you say "primitive" here,
though. Do you mean "lisp function" or do you mean something else?
I want to combine the functionality of csound with Xemacs to create
an
IDE for csound. Is this madness?
No, it sounds a perfectly reasonable use of the tool, assuming that the
input and output of Csound &c. is primarily text-based, except for the
sound bit. ;)
If you really want dials and knobs and stuff, Emacs isn't a good
choice, but it looked like Csound deals mostly with text, right?
From the name of it I assume that file-name-handler-alist exists for
this reason (ie to handle certain files differently from standard text
files if necessary). Am I wrong? If that is its purpose, how is it
used?
You are wrong there. It's used to create virtual file systems within
Emacs, not to handle files differently from standard text.
What you probably want is to create a major mode for Csound files. That
will let you create what you want -- a way of editing those files in a
special purpose buffer.
You can also define functionality for sending some or all of the buffer
content to Csound, modifying the content and the like, as part of that
major mode.
Daniel
--
We should forget about small efficiencies, say about 97% of the time:
premature optimization is the root of all evil.
-- Donald E. Knuth, _Structured Programming with go to Statements_
(Computing Surveys, Vol. 6, No. 4, December 1974)
5:04 a.m.
New subject: primitive to fill a buffer
On Thu, 29 Aug 2002, Daniel Pittman wrote:
*nod* I suspected that it might, but you never know.
I'll
double check.
Sure. The simple `start-process' call runs a program as an
asynchronous
That sounds like a good possibility.
Sure. I don't quite know what _you_ mean when you say
"primitive" here,
I mean a function that is callable inside xemacs
(interactive or
not) and written in C rather than eLisp.
input and output of Csound &c. is primarily text-based, except
for the
sound bit. ;)
That is in fact one of its selling points.
If you really want dials and knobs and stuff, Emacs isn't a good
choice, but it looked like Csound deals mostly with text, right?
I don't. I
can't think of anything worse than tying to adjust a knob
with a pointer on a computer screen.
You are wrong there. It's used to create virtual file systems
within
Emacs, not to handle files differently from standard text.
Bummer.
What you probably want is to create a major mode for Csound files.
That
Well, yeah. I was so caught up with re-using C code that I went strait for
the low level details. I'll take a look at developing modes first.
Thanks for taking the time to clear up my misconceptions and for the
advice.
Brian
5:26 a.m.
New subject: primitive to fill a buffer
On Thu, 29 Aug 2002, Brian Willkie wrote:
On Thu, 29 Aug 2002, Daniel Pittman wrote:
[...]
> Sure. I don't quite know what _you_ mean when you say
"primitive"
> here,
I mean a function that is callable inside xemacs (interactive or
not) and written in C rather than eLisp.
Oh. You don't want to do that, really. If you think "I need C", you
probably looked at your problem the wrong way, at least with Emacs.
> input and output of Csound &c. is primarily text-based,
except for
> the sound bit. ;)
That is in fact one of its selling points.
*nod*
[...]
> What you probably want is to create a major mode for Csound
files.
> That
Well, yeah. I was so caught up with re-using C code that I went strait
for the low level details. I'll take a look at developing modes first.
A mode is what you want, really. They are what let you build, for
example, the powerful C or SGML editing facilities in Emacs.
Er, though if you want to look at a functional major mode, the xrdb mode
is my first choice, because it's simple and clear. If you want a working
example, look at that. :)
Thanks for taking the time to clear up my misconceptions and for the
advice.
That's OK. The manuals and the existing major modes made it pretty easy
to pick up how a major mode is put together, I found, the last time I
looked at one.
What you want to do with Csound, though, sounds completely practical and
like a good candidate for running with Emacs. :)
Daniel
--
When the tyrant has disposed of foreign enemies by conquest or treaty, and
there is nothing to fear from them, then he is always stirring up some war or
other, in order that he people may require a leader.
-- Plato
7917
days inactive
7919
days old
7 comments
3 participants
participants (3)
-
Andy Piper -
Brian Willkie -
Daniel Pittman