This is a feature. The idea is that you start the commit log with header
lines (eg Author: whoever), then have a blank line,
then have the commit message. The blank line is font-locked as a thin bar to
indicate it separates the header from the body.
IIUC, this should be fixed in Emacs 24.3.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
This was fixed upstream.
(To contact Emacs upstream, always mail bug-gnu-emacs@gnu rather than the
original file author, who in many cases
is no longer the maintainer.)
Ref: http://lists.gnu.org/archive/html/emacs-diffs/2013-10/msg00165.html
--
To UNSUBSCRIBE, email to
This is fixed upstream.
See http://lists.gnu.org/archive/html/emacs-diffs/2013-10/msg00204.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tags 592802 wontfix
close 592802
stop
That's just how Emacs works. Adding a directory to the load-path does not cause
everything in there to be loaded.
You have to load (or require) the relevant library as a separate step.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
tags 690317 moreinfo
stop
PGG is obsolete since Emacs 24.1, replaced by EasyPG.
In any case, without a recipe to reproduce this state, nothing can be done.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
severity 681392 wishlist
stop
The files in /etc/emacs/site-start.d/ are tiny files that mainly just
(auto)load other files.
Compiling them would bring no visible benefit, and introduce extra complication.
Since Debian compiles separate elc files for each Emacs version, you would need
to add
Note that the default value of mail-interactive changed from nil to t
in Emacs 23.1.
If you still feel there is something more that needs to be done, I'd suggest
reporting it directly to bug-gnu-em...@gnu.org (and closing this Debian report).
--
To UNSUBSCRIBE, email to
For libpng12, you previously reported https://bugs.debian.org/766809 .
I think I had 1.2.54-4 installed, but maybe the spurious /usr/lib link was
still present.
Thanks for the quick response.
>> FATAL ERROR:>> Both /lib/x86_64-linux-gnu/libpng12.so.0 and
>> /usr/lib/x86_64-linux-gnu/libpng12.so.0 exist.
> This is weird, because I see nothing in the package which would create
> this link.
I don't think that was due to usrmerge, I think it was
PS It's surprising that this tool does not default to a dry-run mode of
operation, or at least check that there are no name clashes before it starts
moving things.
Package: usrmerge
Version: 16
Severity: important
On testing, I ran:
sudo apt-get install usrmerge
In hindsight, this was a mistake...
It aborted partway through with:
FATAL ERROR:
Both /lib/x86_64-linux-gnu/libpng12.so.0 and
/usr/lib/x86_64-linux-gnu/libpng12.so.0 exist.
Now my
Emacs 25.2 was uploaded some time ago. This report should be closed.
This bug is blocking the migration of the Emacs 25 package. It was apparently
fixed in
https://packages.qa.debian.org/e/emacs25/news/20170729T201922Z.html
but the wrong bug number was cited in the upload message.
Maybe you have psgml installed? Ref: https://debbugs.gnu.org/24538#19
It's a bad test, please don't waste your time trying to debug it. It fails
randomly on other platforms too, and upstream don't know why; ref
https://debbugs.gnu.org/24503
You should probably just ignore/disable it.
I'd guess that in a GTK Emacs, the GTK scrollbar ignores X resources. Try
emacs25-lucid?
I think your expectation is incorrect, and that you should add the -c argument
to get a new frame.
This is not an Emacs bug (or a bug at all) IMO. See eg bug#766464 and its many
duplicates, or the summary from bug#827639:
The problem is that you are using su to start a X/GNOME application as
root. su does not clear the environment, so XDG_RUNTIME_DIR points to
your users path, and
reassign 903436 wnpp
stop
It's bad practice to bundle add-ons into the actual Emacs package, so this is
better interpreted as a request for a new standalone tramp package. Personally
I think this is extremely low priority, since the Tramp maintainer very
actively syncs the latest Tramp release
Just ignore this test. See https://bugs.debian.org/879020 .
By experiment, this issue is present since Emacs 23.1.
Perhaps it therefore does not have to hold up the testing migration of Emacs 25.
This is a libotf bug. See https://debbugs.gnu.org/30193
According to ldd, gedit does not use libotf.
The crash is (probably) a libotf bug, see https://debbugs.gnu.org/30193, and
debian bug#909699.
> It's a question about the Unicode data file license. I've contacted
> unicode.org, and finally referred it to the ftp-masters. We'll see what
> they determine.
> I noticed it while looking at the changes in Emacs 26. For example
> IVD_Sequences.txt
But this same issue about IVD_Sequences
On Wednesday, 5 December 2018, 09:31:09 GMT-8, Rob Browning
wrote:
> I believe I did, but additional files have been added to Emacs 26
Please could you list all the files that concern you?
Maybe this helps?
http://lists.gnu.org/r/emacs-diffs/2018-12/msg00377.html
reassign 898550 dictionaries-common
stop
Your backtrace indicates that the error comes from
debian-ispell-preprocess-dicts-alist, which is provided by
debian-ispell.el from the dictionaries-common package. This is corroborated by
the fact that the error disappears with -Q, which prevents
I wonder if this report is no longer relevant and could be closed?
There is no standalone Gnus package any more, and no versioned emacs21 etc
packages, so the comments from message#27 no longer seem relevant.
forwarded 916012 https://debbugs.gnu.org/30045
stop
Please note that the upstream report #30045 I referenced is only marked as
fixed in Emacs 26.2, not 26.1.
The filenotify tests are flaky, and often seem to fail for non-Emacs reasons. I
suggest you mark that one as unstable if it causes you problems.
tags 910231 moreinfo unreproducible
stop
I can't reproduce this. Does it happen with emacs -Q?
tags 883683 moreinfo unreproducible
stop
/usr/bin/emacs --xrm 'Emacs.verticalScrollBars:off'
seems to work fine for me with GTK Emacs 26.
See https://debbugs.gnu.org/30045 and similar.
See https://debbugs.gnu.org/30045 (fixed in Emacs 26.2).
You've misundertood the points being made both in Emacs bug 37156 and Debian
bug 916227.
LANG=zh_TW aspell -c README
Error: No word lists can be found for the language "zh_TW"
This is nothing to do with Emacs.
Not reproducible. (Obviously Debian isn't going to choose to disable font-lock
by default in Emacs.)
It's disappointing to see Emacs 26.3 fail to propagate to Debian testing for
the best part of six months due to this issue.
This "FTBS" is a single test failure on mips, in test set-process-filter-t.
This test is not present prior to Emacs 26.3.
It was added for https://debbugs.gnu.org/36591 , so
I can't reproduce this.
I'd guess it is a font-related crash like https://debbugs.gnu.org/30045
If it still happens to you with Emacs 27.1, I suggest you report it upstream
with M-x report-emacs-bug.
13 years on, if you are still interested in this feature, I suggest you ask for
it on the cc-mode mailing list:
https://sourceforge.net/p/cc-mode/mailman/cc-mode-help/
where the cc-mode maintainer can hopefully give a definitive answer.
No development of cc-mode happens on Debian.
Using the recipe from the OP, it works fine for me in Emacs 27.1.
This was 8 years and 4 Emacs major releases ago.
If this is still an issue with Emacs 27.1, I suggest opening a new report with
upstream directly.
I can't reproduce this.
This report is 10 years old, refers to an Emacs 4 major versions ago, and has
seen no comments.
I suggest closing it, and opening a new report with upstream Emacs if this is
still an issue.
The emacs-bin-common package does recommend mailutils.
That seems an appropriate level of dependency, given that many won't use Emacs
for mail at all.
Presumably this is https://bugs.debian.org/968955 , an issue in
dictionaries-common that was fixed last August.
I was unable to reproduce this.
If it still happens with Emacs 27.1, I encourage you to report it to the Emacs
developers with M-x report-emacs-bug. They will need:
1) A complete, minimal example that shows the problem (eg lists exactly which
version of helm and its dependencies you
This report was forwarded to https://sourceforge.net/p/docutils/bugs/283/,
where it received the comment:
"Indeed this feature isn't implemented yet and probably won't be anytime soon."
Is there any value in keeping the Debian bug report open, or can it be closed?
I was unable to reproduce this.
If it still happens with Emacs 27.1, I encourage you to report it to the Emacs
developers with M-x report-emacs-bug.
I can reproduce this with current Emacs master.
I encourage you to report this to the Emacs developers using M-x
report-emacs-bug.
"X protocol error: BadLength (poly request too large or internal Xlib length
error) on protocol request 139"
is https://debbugs.gnu.org/37895 (amongst others)
This is marked as fixed in Emacs 27.1.
If the issue still occurs for you with Emacs 27.1, I suggest reporting it using
M-x
Gnus no longer exists outside of Emacs.
I suggest you report this with M-x report-emacs-bug.
I note that `article' is not documented as one of the variables one can use in
`gnus-summary-highlight'.
I was unable to reproduce this.
If it still happens with Emacs 27.1, I encourage you to send a complete,
minimal example to the Emacs developers using M-x report-emacs-bug.
Package: libqt4-core
Version: 4.2.1-2+b1
My application fails to build when the QT_NO_DEBUG_OUTPUT define is
made. This was a known bug in Qt 4.2 which was fixed in v4.2.2; see
this Trolltech tracker issue:
http://www.trolltech.com/developer/task-tracker/index_html?method=entryid=133796
This bug also affects phpbb, which uses dbconfig-common.
Thanks,
Stephen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Source: linux
Severity: normal
CrashPlan is a backup product:
http://crashplan.com
They're unusual in this space in that their cloud backup hosting service is a
bazillion times cheaper than everyone else's, and they have full Linux support.
The downside is that you have to use their
Package: awscli
Version: 1.2.9-2
Severity: grave
Justification: renders package unusable
Any attempt to run 'aws' crashes with the following traceback:
~$ aws --version
Traceback (most recent call last):
File /usr/bin/aws, line 23, in module
sys.exit(main())
File /usr/bin/aws, line 19,
Source: linux
Version: 3.16.0-4-amd64
Severity: important
After running a dist-upgrade yesterday (for the first time in a few weeks), the
intel graphics driver on my laptop (Thinkpad T440s) has started spewing tons of
WARNINGs into my kernel logs, e.g. at suspend/resume (but also other times).
Source: linux
Version: 4.0.8-1
Severity: important
On my thinkpad T440s (Intel graphics), I often use an external (HDMI) monitor
via a docking station. With the 3.16.7-ckt11 version of the kernel, this works
great. With 4.0.8-1 (current in testing), it doesn't work at all -- it detects
that the
Package: src:linux
Version: 5.3.15-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
Had been having lockup with swiotlb getting overloaded, added
iommu=force, intel_iommu=on, swiotlb=noforce to fix. Have reduced
the swiotlb lockup, but now get a freeze on system
Package: gramps
Version: 5.1.3-1
Severity: minor
X-Debbugs-Cc: jsmith+debb...@alum.mit.edu
Dear Maintainer,
* What led up to the situation?
Trying to install the PostgreSQL addon for Gramps
* What exactly did you do (or not do) that was effective (or
ineffective)?
Ran the
60 matches
Mail list logo
