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
3a446a02
Commit
3a446a02
authored
Jul 08, 2020
by
Eli Zaretskii
1
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
; * src/xdisp.c (decode_mode_spec): Fix commentary.
parent
79f381b4
Pipeline
#6006
failed with stage
in 10 seconds
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
src/xdisp.c
src/xdisp.c
+1
-1
No files found.
src/xdisp.c
View file @
3a446a02
...
...
@@ -26344,7 +26344,7 @@ decode_mode_spec (struct window *w, register int c, int field_width,
height = WINDOW_TOTAL_LINES (w);
/* We cannot cope with w->start being outside of the
accessible portion of the buffer; in particular,
display_count_lines call below
will
infloop if called with
display_count_lines call below
might
infloop if called with
startpos_byte outside of the [BEGV_BYTE..ZV_BYTE] region.
Such w->start means we were called in some "creative" way
when the buffer's restriction was changed, but the window
EMBA bot
@bot
mentioned in commit
398a2680
·
Jul 11, 2020
mentioned in commit
398a2680
mentioned in commit 398a2680616112675afe26478706a3cea9e76158
Toggle commit list
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