Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
emacs
emacs
Commits
9d8b24a2
Commit
9d8b24a2
authored
Dec 04, 2006
by
Kim F. Storm
Browse files
*** empty log message ***
parent
5945f1f4
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
15 additions
and
4 deletions
+15
-4
lisp/ChangeLog
lisp/ChangeLog
+5
-0
lispref/ChangeLog
lispref/ChangeLog
+5
-0
src/ChangeLog
src/ChangeLog
+5
-4
No files found.
lisp/ChangeLog
View file @
9d8b24a2
2006-12-04 Kim F. Storm <storm@cua.dk>
* bindings.el (global-map): Bind [signal t] to ignore, to have
user signals ignored by default.
2006-12-04 Juanma Barranquero <lekktu@gmail.com>
* descr-text.el (describe-char-unicode-data): Use a hidden buffer for
lispref/ChangeLog
View file @
9d8b24a2
2006
-
12
-
04
Kim
F
.
Storm
<
storm
@
cua
.
dk
>
*
commands
.
texi
(
Misc
Events
):
Update
signal
events
.
(
Event
Examples
):
Add
signal
example
.
2006
-
11
-
29
Richard
Stallman
<
rms
@
gnu
.
org
>
*
frames
.
texi
(
Visibility
of
Frames
):
Explain
visible
windows
...
...
src/ChangeLog
View file @
9d8b24a2
...
...
@@ -9,12 +9,13 @@
if first event in [signal xxx] sequence.
(lispy_user_signals, Qusr1_signal, Qusr2_signal): Remove.
(syms_of_keyboard): Don't intern and staticpro them.
(Qsignal, Qusr1, Qusr2): Declare.
(syms_of_keyboard): Intern and staticpro them.
(make_lispy_event): Return them for USER_SIGNAL_EVENTs.
(Qsignal): Declare here.
(syms_of_keyboard): Intern and staticpro it.
(make_lispy_event): Use it. Intern symbols on the fly for other
USER_SIGNAL_EVENTs events.
* process.c (Qsignal): Declare extern.
(syms_of_process): Don't intern/staticpro t
hem
here.
(syms_of_process): Don't intern/staticpro
i
t here.
* process.c (read_process_output): Abort if carryover < 0.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment