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
emacs
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
1
Issues
1
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Operations
Operations
Incidents
Environments
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
CI / CD
Repository
Value Stream
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
emacs
emacs
Commits
9a39b306
Commit
9a39b306
authored
Jul 04, 2010
by
Tetsurou Okazaki
Committed by
Stefan Monnier
Jul 04, 2010
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
* src/lread.c (read1): Fix up last change to not mess up `c'.
Fixes: debbugs:6490
parent
e6cb2cbb
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
32 additions
and
24 deletions
+32
-24
src/ChangeLog
src/ChangeLog
+5
-0
src/lread.c
src/lread.c
+27
-24
No files found.
src/ChangeLog
View file @
9a39b306
2010-07-04 Tetsurou Okazaki <okazaki@be.to> (tiny change)
Stefan Monnier <monnier@iro.umontreal.ca>
* lread.c (read1): Fix up last change to not mess up `c'.
2010-07-04 Juanma Barranquero <lekktu@gmail.com>
* strftime.c: Revert conversion to standard C (2010-07-04T07:50:25Z!dann@ics.uci.edu).
...
...
src/lread.c
View file @
9a39b306
...
...
@@ -2645,32 +2645,35 @@ read1 (register Lisp_Object readcharfun, int *pch, int first_in_list)
}
case
'`'
:
/* Transition from old-style to new-style:
If we see "(`" it used to mean old-style, which usually works
fine because ` should almost never appear in such a position
for new-style. But occasionally we need "(`" to mean new
style, so we try to distinguish the two by the fact that we
can either write "( `foo" or "(` foo", where the first
intends to use new-style whereas the second intends to use
old-style. For Emacs-25, we should completely remove this
first_in_list exception (old-style can still be obtained via
"(\`" anyway). */
if
(
first_in_list
&&
(
c
=
READCHAR
,
UNREAD
(
c
),
c
==
' '
))
{
Vold_style_backquotes
=
Qt
;
goto
default_label
;
}
else
{
Lisp_Object
value
;
new_backquote_flag
++
;
value
=
read0
(
readcharfun
);
new_backquote_flag
--
;
{
int
next_char
=
READCHAR
;
UNREAD
(
next_char
);
/* Transition from old-style to new-style:
If we see "(`" it used to mean old-style, which usually works
fine because ` should almost never appear in such a position
for new-style. But occasionally we need "(`" to mean new
style, so we try to distinguish the two by the fact that we
can either write "( `foo" or "(` foo", where the first
intends to use new-style whereas the second intends to use
old-style. For Emacs-25, we should completely remove this
first_in_list exception (old-style can still be obtained via
"(\`" anyway). */
if
(
first_in_list
&&
next_char
==
' '
)
{
Vold_style_backquotes
=
Qt
;
goto
default_label
;
}
else
{
Lisp_Object
value
;
return
Fcons
(
Qbackquote
,
Fcons
(
value
,
Qnil
));
}
new_backquote_flag
++
;
value
=
read0
(
readcharfun
);
new_backquote_flag
--
;
return
Fcons
(
Qbackquote
,
Fcons
(
value
,
Qnil
));
}
}
case
','
:
if
(
new_backquote_flag
)
{
...
...
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