From: Eli Zaretskii <eliz@gnu.org>
To: CHENG Gao <chenggao@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Fiddling with the menus
Date: Sun, 09 Aug 2009 20:38:54 +0300 [thread overview]
Message-ID: <83ocqolwep.fsf@gnu.org> (raw)
In-Reply-To: <m2r5vls4bk.fsf@cyberhut.org>
> From: CHENG Gao <chenggao@gmail.com>
> Date: Sun, 09 Aug 2009 17:51:27 +0800
>
> I think "Emacs Known Problems" should only show outstanding problems in
> CURRENT emacs.
Would you like to volunteer to maintain etc/PROBLEMS along these
lines? Mind you, the task is not as easy as it maybe sounds, because
knowing just which problems are solved and which are not is quite
hard, especially if the problem is about an OS you don't use and don't
have access to.
Let's take a random entry:
** Emacs crashes when you use Bibtex mode.
This happens if your system puts a small limit on stack size. You can
prevent the problem by using a suitable shell command (often `ulimit')
to raise the stack size limit before you run Emacs.
How to know if this still happens? the entry doesn't even say on which
system it was spotted.
> And some problems are caused by third party packages (for example VM).
> It could be put into another file.
I don't think this is a good idea. Someone looking for his/her
problem shouldn't need to scan numerous files.
> My understand is "Emacs Known Problems" is for problems related to
> current Emacs and its bundled packages.
Yes, but Emacs could have problems caused by third-party packages as
well. We don't want to omit the information about that, if it can
help. For example:
*** Emacs says it has saved a file, but the file does not actually
appear on disk.
This can happen on certain systems when you are using NFS, if the
remote disk is full. It is due to a bug in NFS (or certain NFS
implementations), and there is apparently nothing Emacs can do to
detect the problem. Emacs checks the failure codes of all the system
calls involved in writing a file, including `close'; but in the case
where the problem occurs, none of those system calls fails.
Sounds useful, doesn't it?
next prev parent reply other threads:[~2009-08-09 17:38 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D26C2A6A-F1CF-4820-ACBB-97F0592FB9CC@xahlee.org>
[not found] ` <E1MYsVp-0002ps-S1@fencepost.gnu.org>
[not found] ` <C2633D79FA454AE3B8A24E3F8890F67A@xahPC>
2009-08-09 3:36 ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Stefan Monnier
2009-08-09 3:53 ` Lennart Borgman
2009-08-09 5:13 ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs Stefan Monnier
2009-08-09 17:20 ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Eli Zaretskii
2009-08-09 17:56 ` Lennart Borgman
2009-08-09 18:02 ` Eli Zaretskii
2009-08-09 18:10 ` Lennart Borgman
2009-08-09 18:15 ` Eli Zaretskii
2009-08-09 18:21 ` Lennart Borgman
2009-08-09 18:51 ` Eli Zaretskii
2009-08-09 18:54 ` Lennart Borgman
2009-08-09 18:57 ` Eli Zaretskii
2009-08-09 18:55 ` Eli Zaretskii
2009-08-09 19:07 ` Lennart Borgman
2009-08-09 20:36 ` Lennart Borgman
2009-08-09 23:00 ` Fiddling with the menus Jason Rumney
2009-08-09 23:14 ` Lennart Borgman
2009-08-09 23:46 ` Jason Rumney
2009-08-10 1:51 ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Stephen J. Turnbull
2009-08-10 3:03 ` Eli Zaretskii
2009-08-10 3:26 ` Lennart Borgman
2009-08-10 2:27 ` Fiddling with the menus Stefan Monnier
2009-08-10 2:32 ` Lennart Borgman
2009-08-09 5:05 ` Stefan Monnier
2009-08-09 9:51 ` CHENG Gao
2009-08-09 17:38 ` Eli Zaretskii [this message]
2009-08-09 18:06 ` CHENG Gao
2009-08-09 18:17 ` Eli Zaretskii
2009-08-09 18:24 ` Lennart Borgman
2009-08-09 18:54 ` Eli Zaretskii
2009-08-09 18:59 ` Lennart Borgman
2009-08-09 22:54 ` Jason Rumney
2009-08-10 1:12 ` Stefan Monnier
2009-08-09 17:50 ` Eli Zaretskii
2009-08-09 23:14 ` Juri Linkov
2009-08-10 2:32 ` Stefan Monnier
2009-08-10 3:07 ` Eli Zaretskii
2009-08-11 5:06 ` Dan Nicolaescu
2009-08-11 13:03 ` Lennart Borgman
2009-08-09 12:37 ` Fiddling with the menus (was: bug#4043: 23.1; thanks for emacs 23!) Florian Beck
2009-08-09 17:52 ` Eli Zaretskii
2009-08-09 17:26 ` Eli Zaretskii
2009-08-09 18:05 ` Fiddling with the menus Richard Riley
2009-08-09 18:14 ` Eli Zaretskii
2009-08-10 2:09 ` Stefan Monnier
2009-08-10 3:16 ` Eli Zaretskii
2009-08-09 23:09 ` Juri Linkov
2009-08-09 23:29 ` Lennart Borgman
2009-08-10 0:10 ` Drew Adams
2009-08-10 2:22 ` Stefan Monnier
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=83ocqolwep.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=chenggao@gmail.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).