On Wed, Apr 7, 2021, at 14:05, Philip Kaludercic wrote:
> I apologize for the empty form, this was the first time I used
> reportbug. I hope it is ok if I answer the question in this message.
That's fine, but please still fill us in on what exactly failed.
If you get a *Backtrace* buffer, please
On Sun, Mar 17, 2019, at 04:51, zieg...@uni-freiburg.de wrote:
> The problem occurs also with the current kernel
> linux-image-4.19.0-4-amd64.
Could you please share your `locale' settings? Does a file with this name exist
in the current directory? Is it possible to create a file with this
On Wed, Jan 3, 2018, at 03:45, H.-Dirk Schmitt wrote:
> On Mi, 2018-01-03 at 02:06 +0200, era eriksson wrote:
> > Code outline for an emacs batch wrapper
>
> I do not insist on bash – you are free to fix it in any programming
> language ;-)
A fair amon
print something?
> then# oops run in timeout>
> … add error handling here
> else# emacs terminates
> without timeout
>cat ${catchFile} # forward console
>output>exi
This also affects Ubuntu and has been reported in the wild by users
upgrading from earlier versions of the distro.
https://bugs.launchpad.net/debian/+source/oneliner-el/+bug/1586145
(Notice also the recent duplicate if you have trouble with the error
messages being in German.)
The problem might
things for him. (If the elisp sources
are required, I would sort of expect it to be the other way around? Or
does elpa also only install elc files?)
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
and mu4e. Maybe emacs24-el just happened to set
things up to happen in the proper order as well, and is not a true
requirement?
Sorry for talking to myself here ...
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
--
To UNSUBSCRIBE, email to debian-bugs-rc
to
emacsen-common as the likely source for whatever exposes this, although
it may well be that the root cause for the bug is in the xemacs21
packaging.
#313511 looks similar, maybe the changes discussed there are actually
relevant for this case?
/* era */
--
If this were a real .signature, it would suck
merge 597530 397757
thanks
On Mon, 20 Sep 2010 23:49 +0200, Stefan Monnier
monn...@iro.umontreal.ca wrote:
See #397757 why this would be correct.
Agreed. I guess this can be merged with #397757.
Hence.
/* era */
--
If this were a real .signature, it would suck less. Well, maybe
On Tue, 05 Oct 2010 10:51 +, Debian Bug Tracking System
ow...@bugs.debian.org wrote:
reassign 597530 emacs23
Thanks. I was wondering how I should cope with this.
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
--
To UNSUBSCRIBE, email to debian
in the result set.
Hope this helps (-:
/* era */
--
If this were a real .signature, it would suck less. Well, maybe not.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
of assumptions, which don't map
easily to debian
To some extent, it would fix this as well, I guess.
/* era */
PS. Some more secure CGI links for you: http://tinyurl.com/37tbz5
(brian d foy's CGI Meta FAQ) and from there in particular Simson
Garfinkel's http://thinkunix.net/web/cgi-rules.txt
hole allowing access to the accounts of
users who use the package. I'm not sure about introduces (it likely
existed before?) and without an isolated patch, it's hard to assess the
exact scope of the vulnerability, even for someone more skilled than
myself.
/piglet panics
/* era
13 matches
Mail list logo
