[EMAIL PROTECTED] skrev:
[t901353]alnx004[101]% pkg-config alsa --libs
-L/usr/lib64 -lasound -lm -ldl -lpthread
[t901353]alnx004[102]%
Config.log:
configure:5642: result: no
configure:5663: checking for pkg-config
configure:5681: found /usr/bin/pkg-config
configure:5694: result: /usr/bin/pkg-
M-TAB is not a Windows-specific problem, so it should be documented in
the common part of the manual, if at all.
Yes. But where? Perhaps the first place that M-TAB is documented
as an Emacs command. What do you think?
___
emacs-pretest-bug
The wrong language is chosen on w32 for the tutorial:
emacs -Q
C-h t
This shows the tutorial in Swedish. It should however be in English
according to my setup on this Windows 2000 pc:
Regional settings:
Your local (location): Swedish
Language setting: x Western Europe and United State (d
Stefan Monnier <[EMAIL PROTECTED]> writes:
>> I've made my decision about this, and I don't want to argue it
>> further.
>
> Does anybody agree with Richard on this one?
Technically I prefer Jason's solution, but I think in practice it's an
extremely minor issue. I've only ever had problems with
Eli Zaretskii wrote:
Date: Wed, 20 Dec 2006 22:13:27 +0100
From: Lennart Borgman <[EMAIL PROTECTED]>
CC: emacs-pretest-bug@gnu.org
cmdproxy is IMO the _only_ level where this should be done, because we
are talking about rewriting commands typed by the user, to make them
palatable to the W
> Date: Wed, 20 Dec 2006 22:13:27 +0100
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: emacs-pretest-bug@gnu.org
>
> > cmdproxy is IMO the _only_ level where this should be done, because we
> > are talking about rewriting commands typed by the user, to make them
> > palatable to the Windows sh
Lennart Borgman wrote:
Why not set (buffer-locally) a different variable (such as
"shell-uses-backslashes") when starting the inferior process? That
seems
more inline with what we usually do, rather than make a global variable
buffer-local because we later (re)compute something that depends o
Stefan Monnier wrote:
The user might be testing new configurations for example and thereby
changing shell-file-name (which now has only a global value). Since w32 is
not that simple when it comes to shell that is a very likely situation, at
least when the user has learned a bit more about emacs.
>> I don't see in which sense this is an example. After all, what harm would
>> there be to use sh-mode for files named .BASH_PROFILE or .ZLOGIN ?
>> Or even .bAsH_PROfilE ?
>> It wouldn't be correct. These file names are case sensitive.
> I've made my decision about this, and I don't want to a
> The user might be testing new configurations for example and thereby
> changing shell-file-name (which now has only a global value). Since w32 is
> not that simple when it comes to shell that is a very likely situation, at
> least when the user has learned a bit more about emacs.
But the user is
Emacs crashes now and then at random without reason.
The error code is:
Segmentation fault - Error 11
It doesn't do this when we run it, so we can't debug it on our own.
Please use GDB to give us backtraces.
___
emacs-pretest-bug mailing li
> I don't see in which sense this is an example. After all, what harm
would
> there be to use sh-mode for files named .BASH_PROFILE or .ZLOGIN ?
> Or even .bAsH_PROfilE ?
> It wouldn't be correct. These file names are case sensitive.
I've made my decision about this
Stefan Monnier wrote:
Anywhere. The point is that those variables may change during the time
the interactive shell exists (or perhaps a non-interactive shell).
In this case I noticed it because the file completion code needs to know
the value of shell-file-name.
Hmm... interesting, I didn
> As Jury corrected me, the problem is not with supporting the new
> format, the problem was that menus in the indices were not decorated
> as normal menus since long ago.
> I agree that we should consider revising this decision now, that the
> machines are so much faster.
We could also let jit/f
> Anywhere. The point is that those variables may change during the time
> the interactive shell exists (or perhaps a non-interactive shell).
> In this case I noticed it because the file completion code needs to know
> the value of shell-file-name.
Hmm... interesting, I didn't think of this case.
[t901353]alnx004[101]% pkg-config alsa --libs
-L/usr/lib64 -lasound -lm -ldl -lpthread
[t901353]alnx004[102]%
Config.log:
configure:5642: result: no
configure:5663: checking for pkg-config
configure:5681: found /usr/bin/pkg-config
configure:5694: result: /usr/bin/pkg-config
configure:5708: checki
Eli Zaretskii wrote:
It autocompletes in the shell buffer with "\" if the shell used has
w32-shell-dos-semantics. When do you not want this?
Personally, I _never_ want to see backslashes, even when I work in
CMD. It makes me saner, since I happen to work simultaneously on Unix
and on W
On 12/20/06, Romain Francoise <[EMAIL PROTECTED]> wrote:
emacs-lock.el seems like a poor man's protbuf.el.
Some shortcomings (most, but not all, fixed in protbuf.el):
- Locking a buffer should be a minor mode.
- There's no emacs-lock entry in minor-mode-alist, so there's no
visual clue in the
[EMAIL PROTECTED] skrev:
> Jan,
>
> I looked in /usr/lib/pkgconfigthe dir is empty. Are files supposed to be
> in there? Where do said files come from?
>
> The new configure.in file did not find the asoundlib.h file...
What does config.log look like (just the alsa relevant parts)?
What d
Jan,
I looked in /usr/lib/pkgconfigthe dir is empty. Are files supposed to be
in there? Where do said files come from?
The new configure.in file did not find the asoundlib.h file...
-tom
Jan Djärv <[EM
> Date: Wed, 20 Dec 2006 20:39:31 +0100
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: emacs-pretest-bug@gnu.org
>
> Can you please explain more exactly what problems you see with my patch?
Backslashes are generally a problem in Emacs, because of their Lisp
interpretation. I don't want us t
Eli Zaretskii wrote:
Date: Wed, 20 Dec 2006 20:34:08 +0100
From: Lennart Borgman <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
Oh, my mind was not there again. There are only subtle but irritating
difficulties with that. As I pointed at somewhere whe
Lennart Borgman wrote:
Can you please explain more exactly what problems you see with my
patch? It autocompletes in the shell buffer with "\" if the shell used
has w32-shell-dos-semantics. When do you not want this?
Why do you think it has to be customizable?
After taking a pause I see tha
> Date: Wed, 20 Dec 2006 20:34:08 +0100
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
>
> Oh, my mind was not there again. There are only subtle but irritating
> difficulties with that. As I pointed at somewhere when I began t
[EMAIL PROTECTED] skrev:
> Is this my system setup that should have this variable set? Or is
> configure.in supposed
> to find it and set it?
Your setup (more specific /usr/lib/pkgconfig/alsa.pc) is supposed to have
Cflags: -I${includedir} -I${includedir}/alsa
I've added a configure check for
> Date: Wed, 20 Dec 2006 11:14:12 -0600
> From: [EMAIL PROTECTED] (Karl Berry)
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
>
> What is this new format?
>
> Yeah, what new format?
The one you mention:
> - [EMAIL PROTECTED]@^H] cookie included in index menus, so
Eli Zaretskii wrote:
That's because, to this day, there's no coherent set of Windows ports
of GNU tools that is sufficiently free of bugs.
Maybe instead of distributing patched Emacs binaries, you could use
the energy to produce such a set of ports. Then the job of building
Emacs would be so mu
Eli Zaretskii wrote:
Date: Wed, 20 Dec 2006 16:14:09 +0100
From: Lennart Borgman <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
Ah, yes, sorry I did not see that the problem with M-TAB when Alt is
used as meta is mentioned neither in the doc string fo
Eli Zaretskii wrote:
Date: Wed, 20 Dec 2006 16:33:00 +0100
From: Lennart Borgman <[EMAIL PROTECTED]>
CC: emacs-pretest-bug@gnu.org
I heard what you said, and I obviously disagree that it's a clear bug.
It is no more a bug than the fact that Emacs uses only forward slashes
in file-name comp
> Date: Wed, 20 Dec 2006 18:33:40 +0100
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: Eli Zaretskii <[EMAIL PROTECTED]>, emacs-pretest-bug@gnu.org
>
> I actually started my distribution because it was so damned
> difficult to get Emacs into a working condition on w32. I recently added
> som
> Date: Wed, 20 Dec 2006 16:33:00 +0100
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: emacs-pretest-bug@gnu.org
> >
> > I heard what you said, and I obviously disagree that it's a clear bug.
> > It is no more a bug than the fact that Emacs uses only forward slashes
> > in file-name completion
> Date: Wed, 20 Dec 2006 16:14:09 +0100
> From: Lennart Borgman <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], [EMAIL PROTECTED], emacs-pretest-bug@gnu.org
>
> Ah, yes, sorry I did not see that the problem with M-TAB when Alt is
> used as meta is mentioned neither in the doc string for
> w32-pa
> "G" == [EMAIL PROTECTED] com <[EMAIL PROTECTED]> writes:
G> I compiled emacs 23.0.0 from CVS and installed on on my
G> centos 4.2 box. The default face looks very nice, but
G> bold, italic, and some menu faces use old fonts
I presume from this that you compiled and are running with
the --en
The font can be specified in command line or .emacs configuration. In command
line use -fn or -font to specify a font, and --enable-font-backend to enable use
of Xft. In .emacs, use set-default-font and set-fontset-font to specify the
default font face and fontset font faces of other encodings.
fo
I compiled emacs 23.0.0 from CVS and installed on on my Centos 4.2 box.
The default face looks very nice, but bold, italic, and some menu faces
use old fonts, which is the same problem posted at EmacsWiki on Aug 16.
It is said that there is already a bug fix and it works well. Can I get
the fix
Juanma Barranquero wrote:
I'm sure my usage pattern is very different from yours (I never print
from inside Emacs, for example), but I don't have any trouble "getting
Emacs into a working condition on w32". There are some rough edges.
Which Is Not The Same Thing :)
Yes, my fingers are probably
On 12/20/06, Lennart Borgman <[EMAIL PROTECTED]> wrote:
Maybe. I actually started my distribution because it was so damned
difficult to get Emacs into a working condition on w32.
I'm sure my usage pattern is very different from yours (I never print
from inside Emacs, for example), but I don't
Juanma Barranquero wrote:
On 12/20/06, Lennart Borgman <[EMAIL PROTECTED]> wrote:
I guess you mean logical relation?
Causal. Arguing for bug fixes does not cause you having to do an
alternate distribution. So the fact that you argue for bugs has no
bearing on whether you do an alternate distri
runs the command ibuffer-forward-filter-group
Which is very disturbing, as I've always felt those arrow keys belong
to me and I don't recall them having been hijacked before. Next thing
you know they'll be usurping trusty C-f.
Anyways, touch a right or left arrow and wham, you're sent to the
bot
On 12/20/06, Lennart Borgman <[EMAIL PROTECTED]> wrote:
I guess you mean logical relation?
Causal. Arguing for bug fixes does not cause you having to do an
alternate distribution. So the fact that you argue for bugs has no
bearing on whether you do an alternate distribution or not. I do argue
f
What is this new format?
Yeah, what new format?
The two latest changes to index formatting in Info output that I can
recall were these:
- line numbers included in index menus, so Info readers can go to
the exact line of an entry, not just a node. Also in plaintext output.
-
Juanma Barranquero wrote:
On 12/20/06, Lennart Borgman <[EMAIL PROTECTED]> wrote:
Yes, and I was not here then. Now instead I am arguing for correcting
the bugs.
No. You're arguing for correcting the bugs (don't we all?) and you're
*also* distributing an alternate version of Emacs. They're se
On 12/20/06, Lennart Borgman <[EMAIL PROTECTED]> wrote:
Yes, and I was not here then. Now instead I am arguing for correcting
the bugs.
No. You're arguing for correcting the bugs (don't we all?) and you're
*also* distributing an alternate version of Emacs. They're separate
actions with no caus
I compiled emacs 23.0.0 from CVS and installed on on my centos 4.2 box.
The default face looks very nice, but bold, italic, and some menu faces
use old fonts, which is the same problem posted at EmacsWiki on Aug 16.
People say there is already a bug fix and it works well. Can I get the
fix?
T
Michael Albinus <[EMAIL PROTECTED]> wrote:
> Sascha Wilde <[EMAIL PROTECTED]> writes:
>
>> Seems to be still buggy:
>>
>> C-x C-f /et TAB
>>
>> results in:
>>
>> Debugger entered--Lisp error: (wrong-type-argument stringp ("etc/"))
>> file-exists-p(("etc/"))
[...]
> Please try the appended patch
Michael Albinus <[EMAIL PROTECTED]> wrote:
> Chris Moore <[EMAIL PROTECTED]> writes:
>
>> I think you've introduced a new bug -
>>
>> lisp/net/ange-ftp.el.gz line 3980:
>> (defun ange-ftp-file-name-completion (file dir)
>> is being called like:
>> (ange-ftp-file-name-completion "" "/a
RMS> That file is in the same directory, /usr/include/alsa/, on my machine
RMS> too. It finds the file because of
RMS> CFLAGS_SOUND= -I/usr/include/alsa
RMS> in src/Makefile. Is that line different in your src/Makefile?
Yes, mine is:
CFLAGS_SOUND=
RMS> If so, please debug why it is filled i
Eli Zaretskii wrote:
Date: Tue, 19 Dec 2006 09:16:42 +0100
From: Lennart Borgman <[EMAIL PROTECTED]>
CC: emacs-pretest-bug@gnu.org
I really don't think we should try to open this can of worms now.
Let's wait until after the release.
As I said this is clearly a bug.
I heard w
On 12/20/06, Romain Francoise <[EMAIL PROTECTED]> wrote:
Try it, emacs-lock.el does that...
I'll certainly try it, I prefer to use standard packages.
But the documentation is misleading. Not even the docstring of
`emacs-lock-check-buffer-lock' discusses protecting against killing
the buffer.
Richard Stallman wrote:
> M-TAB is taken by many modern window managers, so this is not an
> MS-Windows only issue anymore. If it should be mentioned, that should
> be in the main body of the manual, not in a Windows specific appendix.
>
Yes, that is right. Does not most
"Juanma Barranquero" <[EMAIL PROTECTED]> writes:
> Because they don't do the same thing.
> - emacs-lock.el "prevents you from exiting Emacs if a buffer is locked"
> - protbuf.el "protect buffers from accidental killing"
> The killing I'm protecting buffers against is not exiting Emacs, but
> bei
Richard Stallman wrote:
> M-TAB is taken by many modern window managers, so this is not an
> MS-Windows only issue anymore. If it should be mentioned, that should
> be in the main body of the manual, not in a Windows specific appendix.
>
Yes, that is right. Does not most
On 12/20/06, Romain Francoise <[EMAIL PROTECTED]> wrote:
Is there any reason why you don't use the built-in package?
Because they don't do the same thing.
- emacs-lock.el "prevents you from exiting Emacs if a buffer is locked"
- protbuf.el "protect buffers from accidental killing"
The killin
Dieter Wilhelm <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Michaël Cadilhac) writes:
>
>> Dan Jacobson <[EMAIL PROTECTED]> writes:
>>
>>> Nope, it's time the *scratch* buffer should go for experienced user
>>> me.
>>
>>> (kill-buffer "*scratch*");in .emacs
>>
>> I don't see what you're doing
"Juanma Barranquero" <[EMAIL PROTECTED]> writes:
> I use Noah Friedman's protbuf.el
> (http://www.emacswiki.org/cgi-bin/wiki/ProtectingBuffers)
This package looks very similar to emacs-lock.el, which is included
in Emacs. Is there any reason why you don't use the built-in
package?
Thanks,
--
> Date: Wed, 20 Dec 2006 12:49:51 +0100
> From: Mats <[EMAIL PROTECTED]>
>
> True, you cannot be sure that cygwin is installed there, but then what about
> the other directories on Info-default-directory-list?
>
> ("c:/emacs/info/" "/usr/local/info/" "/usr/local/share/info/"
> "/usr/local/gnu/inf
On 12/20/06, Dieter Wilhelm <[EMAIL PROTECTED]> wrote:
It seems that *scratch* is not necessary any longer (in 22) but I wish
there were a command for re-creating it
I use a variant of the following in my .emacs:
(defun switch-to-scratch ()
(interactive)
(let ((exists (get-buffer "*scratc
Richard Stallman <[EMAIL PROTECTED]> writes:
> Does this fix the bug? I don't want to add any features now.
Yes it does fix the "bug", thank you.
>
> *** simple.el 04 Dec 2006 09:25:30 -0500 1.837
> --- simple.el 13 Dec 2006 13:56:29 -0500
> ***
> *** 707,713
> (d
Richard Stallman <[EMAIL PROTECTED]> writes:
> Yes I realised that and I wondered why he didn't use your patch, maybe
> he has just overlooked it, I'll ask.
>
> I did not use that patch because I decided not to add a new feature.
I'm sorry for the confusion I caused. (I thought it were ac
[EMAIL PROTECTED] (Michaël Cadilhac) writes:
> Dan Jacobson <[EMAIL PROTECTED]> writes:
>
>> Nope, it's time the *scratch* buffer should go for experienced user
>> me.
>
>> (kill-buffer "*scratch*");in .emacs
>
> I don't see what you're doing with that. AFAIK, the *scratch* buffer
> never dies,
Sascha Wilde <[EMAIL PROTECTED]> writes:
> Seems to be still buggy:
>
> C-x C-f /et TAB
>
> results in:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp ("etc/"))
> file-exists-p(("etc/"))
> try-completion("et" (("etc/")) file-exists-p)
> tramp-completion-handle-file-name-com
> M-TAB is taken by many modern window managers, so this is not an
> MS-Windows only issue anymore. If it should be mentioned, that should
> be in the main body of the manual, not in a Windows specific appendix.
>
Yes, that is right. Does not most users get hit by this prob
emacs -Q
(global-set-key "\C-b" 'ignore)
C-h C-t
It now contains this misplaced advice (with C-b in read):
C-x C-b List buffers
** The key C-b has been rebound, but you can use instead [More
information] **
(notice also that the info line is >80 chars long).
--
Kim F. Storm <[EMAI
BTW, as `magic-mode-alist' takes precedence over `auto-mode-alist',
perhaps we should make some of the regexps in
`image-type-header-regexp' somewhat less trigger-happy. I'm thinking
mostly of the one for pbm, which matches any file that starts with
P[1-6].
Thanks for noticing
Actually, the thing that doesn't work is:
(defalias 'yes-or-no-p 'y-or-n-p)
Yes, but I don't think the problem with this is in y-or-n-p. y-or-n-p
is meant for smaller decisions, and yes-or-no-p for larger decisions
which might have more serious consequences.
I don't think we should add
Yes I realised that and I wondered why he didn't use your patch, maybe
he has just overlooked it, I'll ask.
I did not use that patch because I decided not to add a new feature.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http:/
Thanks for noticing this error. I think the fix should make the current
state of affairs more prominent, not relegate it to a footnote.
I just did that.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
http://lists.gnu.org/mailman/listinf
I think it's a bug: it looks like Emacs doesn't support the new format
of Index menus introduced with the latest versions of Texinfo.
What is this new format?
We can make Emacs 22 support it, but people will keep using Emacs 21
for a long time. So this could be a long-lasting problem.
Type M-x dired RET, then M-` o m c
and you'll see it.
Thanks, now I do see it. But I think it is correct that this is
blanked out.
Reverting a Dired buffer makes sense, but reverting it with a
different coding system does not. This isn't a matter of reading
a textual directory and decod
prefix, when I run make it fails to compile sound.c, because if can't find
asoundlib.h. If I hardcode the path to the file, all compiles fine and
sound
files play.
Please don't call a file name a "path". In GNU we use the term "path"
only for lists of directories to search.
That fi
-- Forwarded message --
From: Mats <[EMAIL PROTECTED]>
Date: Dec 20, 2006 12:30 PM
Subject: Re: Please add directory to Info-default-directory-list
To: Eli Zaretskii <[EMAIL PROTECTED]>
True, you cannot be sure that cygwin is installed there, but then what about
the other director
> Date: Tue, 19 Dec 2006 16:46:19 +
> From: Jason Rumney <[EMAIL PROTECTED]>
> Cc: emacs-pretest-bug@gnu.org, [EMAIL PROTECTED]
> >
> > Discussing an idea in a useful way does not include continuing to
> > pressure me after I've made a decision.
> >
> I'm sorry if you felt pressured
FWIW, I
Jason Rumney <[EMAIL PROTECTED]> writes:
> Richard Stallman wrote:
>> > The answer is no, and I've chosen a different solution.
>> > Please drop the subject.
>> >
>>
>> If a developers mailing list cannot be used for discussing
>> development ideas, then I think I might as w
> Date: Wed, 20 Dec 2006 10:04:37 +0100
> From: Mats <[EMAIL PROTECTED]>
>
> If I add this to my .emacs, I can use emacs to browse my cygwin info files:
>
> (setq Info-default-directory-list (append Info-default-directory-list
> (list
> "c:/cygwin/usr/sha
I'm sorry for the late response.
> In <[EMAIL PROTECTED]> Kenichi Handa wrote:
> I found what is wrong. In x_load_resources (xrdb.c),
> default values of several X resources are set, but fontSet
> is not set. But, in x_update_menu_appearance (xfaces.c)
> which is called when you set `menu'
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing
list.
Please describe exactly what actions triggered the bug
and the precise symptoms of th
76 matches
Mail list logo
