Steve Youngs <steve@xxxxxxxxxxx> writes:
> * Johann Oskarsson <Johann> writes:
>
> > Steve Youngs <steve@xxxxxxxxxxx> writes:
> >> * Johann Oskarsson <Johann> writes:
> >>
> >> > Steve Youngs <steve@xxxxxxxxxxx> writes:
>
> > 3) Display a SO/OO doc in a SXEmacs window/buffer. Do not
> > use any SO specific keybindings and do everything with UNO
> > bindings.
>
> What is "UNO"?
IIRC, Universal Network Object. It's sorta interprocess communication
stuff used in OpenOffice. I was thinking of using the OO features
directly through lisp, and only use OO as such to display the
reasults.
>
> > Btw, does gnus allow you to auto-fill the numbers like you put
> > them?
>
> No. But filladapt-mode does.
I don't seem to have it (yet another package I'm missing, I guess).
> >> You're 6 years too late. We've been able to do this since 1999
> >> when mmm-mode.el first came into being. :-) There's an XE
> >> package of the same name, "mmm-mode". Check it out.
>
> > Well, what I mean is, that the mode is locally bound in the
> > buffer, and ditch the notion of a major mode as it is. I do
> > know about mmm mode, but I've also heard it doesn't work too
> > well all the time.
>
> I've only played with it once or twice, but I don't recall ever
> hearing any complaints about it.
I have, on #emacs. But it's been a while since, maybe as long as 1.5
years ago though.
> > What I'm thinking is: text mode in comments, main language most
> > of the time, and a 2nd language some of the time, sometimes in
> > comments I suppose. I don't know what PHP sources look like,
> > but I suppose that'll be one such language, and maybe there's a
> > need for a java mode with it too (3rd language). That'll mean 4
> > modes in a buffer.
>
> I sort of agree with this. But I'm not sure of the benefits of text
> mode in comments over and above what exists already.
That depends on the mode. I think cc-mode has more or less text-mode
behaviour in comments (not sure at the moment right now thouth).
The problem isn't as much as technology (providing keybindings/mode by
extents or something) but how it affects users. Good visualization
through font-lock/something better or something else is paramount to
success. If it isn't there already, I propose providing the
technology (but I'm not volunteering for anything yet) and see what
ppl want to use it for.
> >> I'm not sure what you are getting at here? We already have
> >> gutters.
>
> > Yes, frame specific, not per-window, there's a difference.
>
> Ah, so you want to multiply the ugliness. :-)
Yes. I have a few reasons though, and there's plenty of stuff that I
can visualize for it. I just don't want to go into details right now.
> >> > Also, we need to drop the current implementation of the
> >> > modeline, I think. The code is horrible and buggy, and has
> >> > been buggy for years.
> >>
> >> I don't agree with that (at least not yet). Specifically, why
> >> is it horrible? What/where are the bugs.
>
> > 1) There's a horrible reqursion depth bug. If you nest stuff
> > too deeply in the modeline, the deep stuff disappears.
> > Increasing the recursion depth may fix it, but I'm sure
> > there's a better way somehow.
>
> To understand the recursion you must first understand the recursion.
True, but the implementation (in this case) does seem pretty stupid to
me.
> > 2) The modeline doesn't merge faces.
>
> Huh? What do you mean by that?
I don't know, but it *is* in a comment, and (maybe foolishly) belive
it.
> > You should be aware that I have fiddled with the code, and I've
> > seen the comments, they're horrible. Maintainance wise, it's also
> > an utter nightmare, I think.
>
> Cool. I'm still not convinced.
No problem, but I do find it tough when ppl ask me about apparent bugs
in window-number, when the trouble lies in the implementation of the
modeline (yes, it has happened).
> >> > I think my idea about different kinds of buffers would
> >> > facilitate this. Also, we need to be aware of what happens
> >> > when somebody brings forth a video buffer on tty.
> >>
> >> Simple, don't allow it to happen.
>
> > Or make use of AA lib, do you know what it does? It displays
> > images by rendering them in ascii (not art though).
>
> Oh yuck. That'd be awful for anything more complicated than simple
> cartoons. No thank you.
Shouldn't users be allowed to make that choice? I do think AA lib
should be an option, at compile time, if nothing else - if ever
someone wants to do it.
> > You may not be aware of it, but XE doesn't have any visible menu
> > in the tty.
>
> Talk to Evgeny, he can prove you wrong. :-)
OOh, I will, hopefully soon.
>
> > Of course, I should look at what the rats are all about before I
> > complain anymore.
>
> It's just what I call a mouse.
I know. It reminds me of my sister Anna, when she was young, she
wanted a computer so big, that it couldn't use mice, only rats.
Johann
--
This line is left blank intentionally
|