On 17 feb 2005, at 10.43, Kim F. Storm wrote:
Martin Fredriksson <[EMAIL PROTECTED]> writes:
I have now verified the abort also in Linux. The abort happens when
invoking outline-minor-mode 'show-all' after a previous 'hide-body',
when part of the buffer is not visible (scrolled). The abort only
h
Drew Adams wrote:
3. Why not add `dired-mark-symlinks' (`*@') to the Mark
menu? It could be called "Mark Symlinks".
It is already there.
Not in my Emacs -q, it isn't.
It is in my emacs -q.
What are you doing, to get it in the menu?
Nothing.
4.
In merging the CVS trunk changes into the unicode branch, there were many
conflicts in src/w32select.c.
I "forced" the patch to fit (by manually merging each hunk and ignoring
seemingly minor differences between the trunk and the unicode branch) but I
expect that the result won't be quite correct,
Why not add this command to the Mark menu? It could be called "Mark
Extension...".
Because it is not part of Dired.
Well, the exact command I described (prefix arg means unmark) is not the
existing command in dired-x either - it doesn't exist yet. It could be
_added_ to dired,
I already debugged it as in my other post in this thread:
(forward-sexp -1) errors when it is in the middle of a sexp.
Since `forward-sexp' calls a user-defined function which can
behave unpredictably, I think the best thing is to wrap something
(i.e. `find-tag-default' or all i
Why not add this command to the Mark menu? It could be called "Mark
Extension...".
Because it is not part of Dired.
3. Why not add `dired-mark-symlinks' (`*@') to the Mark menu? It could be
called "Mark Symlinks".
It is already there.
4. Why not add `dired-unmark-all-files'
Graphviz is free software now, so what do people think of this mode?
--- Start of forwarded message ---
From: Pieter <[EMAIL PROTECTED]>
Newsgroups: gnu.emacs.sources
Date: Wed, 16 Feb 2005 17:33:30 +0100
Organization: -= Belgacom Usenet Service =-
Xref: shelby.stanford.edu gnu.emacs.sourc
Kim Storm wrote:
Both of us seem to primarily customize one option at a time --
so it's mostly a matter of how far you have to move the mouse
to active that changes...
We all seem to usually set one option at a time. There is no need in
that case to have to worry about thirty other opti
- Original Message -
From: "Kim F. Storm" <[EMAIL PROTECTED]>
> > But of course, you cannot activate it with your mouse.
> >
> > We could make the header line mouse-sensitive, as in Info.
> >
>
> That was the intention -- I meant "keyboard" not "mouse".
Hm. I never noticed this befor
Yes, this has the advantage that Outline minor mode doesn't consider
an autoload cookie as part of the previous top-level sexp anymore.
(Hiding the body of such a preceding top-level sexp would also hide
the autoload cookie.)
If you like the results, then this is a good change. Th
"Drew Adams" <[EMAIL PROTECTED]> writes:
>
> But of course, you cannot activate it with your mouse.
>
> We could make the header line mouse-sensitive, as in Info.
>
That was the intention -- I meant "keyboard" not "mouse".
--
Kim F. Storm <[EMAIL PROTECTED]> http://www.cua.dk
___
[EMAIL PROTECTED] (Kim F. Storm) writes:
> "Lennart Borgman" <[EMAIL PROTECTED]> writes:
>
>>
>>> A simpler interface with a "one line" button bar (prefeably in
>>> the header line when supported) like this
>>>
>>> [Set] [Save] [Load] [Finish]
>>>
>>> would be ideal IMO.
>>
>> Most other ap
The reason the header line is nice is that it will remain on
the screen even when you scroll the customize window.
Yes. Of course, the same operations are also available in the menu-bar
menu, which stays put like a header line.
But of course, you cannot activate it with your mouse.
the whole-buffer buttons are _very_ seldom used.
We could poll the users and see. If users generally use the
single-item button and not the whole-buffer buttons, I would
not mind simplifying things by eliminating the latter.
For the poll - Like Luc, I use the single-item oper
"Lennart Borgman" <[EMAIL PROTECTED]> writes:
>
>> A simpler interface with a "one line" button bar (prefeably in
>> the header line when supported) like this
>>
>> [Set] [Save] [Load] [Finish]
>>
>> would be ideal IMO.
>
> Most other applications have the buttons at the bottom. The idea as
- Original Message -
From: "Kim F. Storm" <[EMAIL PROTECTED]>
> My main objection to the customize interface is the long babble
> at the start of the buffer and the long text on the buttons.
>
> IMO, this is VERY dissimilar to other applications, and sort of
> indicates to the movice user
> Miles Bader writes:
> (2) One must hit `C-c C-c' for changes to take effect; this seems a
> bit heavy-weight -- why not just RET (which seems to be what other
> systems use)?
I agree that this makes sense if you want to edit one filename at a
time, and then commit this change immediately
> Even if size_byte == size, it may contain eight-bit-graphic
> characters, and decoding such a string is a valid operation.
> And even if size_byte > size, it may contain only ASCII,
> eight-bit-graphic, and eight-bit-control charactes. It's
> also a valid operation to decode it.
I think it shou
Richard Stallman <[EMAIL PROTECTED]> writes:
> Here's a case of someone who really wants the whole-buffer buttons.
>
> If the two of you can figure out what basic difference leads you to
> prefer these different modes of use, we might learn something from
> that.
Both of us seem to primarily cust
Hi.
Richard Stallman said:
> Therefore some visual extra warning should appear when
> dired-do-shell-command will act on a marked file and not the one under
> the cursor.
>
> It is a reasonable idea in principle. Any suggestions for how
> to show the distinction?
How about to do the
I've noted the current discussion on Emacs coding.
I am experiencing a strange problem with Emacs encoding which I
thought I might share.
I'm reading the tcpd package's hosts_acccess man page with Emacs man
from this version of Emacs:
GNU Emacs 21.3.50.22 (i686-pc-linux-gnu, GTK+ Version 2.4.
> --- /usr/local/stow/emacs-cvs/share/emacs/22.0.50/lisp/.backup/subr.el.~1~
> 2005-02-09 07:50:41.0 -0800
> +++ /usr/local/stow/emacs-cvs/share/emacs/22.0.50/lisp/subr.el
> 2005-02-16 19:50:57.0 -0800
> @@ -1969,13 +1969,15 @@
> (re-search-forward "\\(\\sw\\|\
>Older releases bring leim-M.N.tar.gz with same version number.
>leim-21.3.tar.gz is exaracted to emacs-21.3/leim/ directory
>by default.
>
>I guess we should make a 21.4 leim file that extracts into
>emacs-21.4/leim. Francesco, could you do that?
Done.
_
In article <[EMAIL PROTECTED]>, Stefan Monnier <[EMAIL PROTECTED]> writes:
>> Is it reasonable to operate with decode-coding-string on a multibyte
>> string? If that is nonsense, maybe we should make it get an error,
>> to help people debug such problems.
> I think it would indeed make sense
Try this: do dired on a large directory of lots of similarly named
files. Now mark one of the files with "m", and move it off the screen
with a C-v. Now use ! (dired-do-shell-command) on the file under the
cursor. Note how easy it is to think that the file under the cursor
is
I have now verified the abort also in Linux.
Please don't call our system "Linux". The name we gave it is GNU.
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
I wrote that reverting is "workaround", not a "solution". I didn't
mean to suggest to revert your change(s) in CVS.
Whatever you call it, it is the wrong way to be helpful.
We need to ask people to debug the problem, not to avoid it.
___
Emacs
I'm actually running right now with an Emacs that does signal such errors.
I've changed the notion of "multibyte/unibyte" string by saying:
- [same as now] if size_byte < 0, it's UNIBYTE.
- [same as now] if size_byte > size, it's MULTIBYTE.
- [changed] if size_byte == size,
I think that it would be a very bad idea to move away from being able to
manipulate (e.g. edit, set, reset, & save) individual options. A given
custom buffer will perhaps have many options in several different states.
There must be a way to save one or more options in the buffer but
Older releases bring leim-M.N.tar.gz with same version number.
leim-21.3.tar.gz is exaracted to emacs-21.3/leim/ directory
by default.
I guess we should make a 21.4 leim file that extracts into
emacs-21.4/leim. Francesco, could you do that?
__
I would guess that the whole-buffer
buttons are _very_ seldom used.
We could poll the users and see. If users generally use the
single-item button and not the whole-buffer buttons, I would
not mind simplifying things by eliminating the latter.
Most often, I just customize a specific
I like the _current_ Custom interface. I believe that its _general
design_, including the button structure, is hard to improve on.
I can't argue with your taste, but there seems to be a lot of indication
that it is too complex and hard to understand for beginners.
__
BTW, I noticed that wdired seems to be a bit unintuitive:
(1) The function name "wdired-change-to-wdired-mode" is bizarre; why
not just `wdired-mode' Is there another way one is supposed to
enter it?
(2) One must hit `C-c C-c' for changes to take effect; this seems a
Martin Fredriksson <[EMAIL PROTECTED]> writes:
> I have now verified the abort also in Linux. The abort happens when
> invoking outline-minor-mode 'show-all' after a previous 'hide-body',
> when part of the buffer is not visible (scrolled). The abort only
> happens when using keys, not when invo
34 matches
Mail list logo
