Add a New Comment (Rich Markup)
Comment Type & Canned Response: None None > Multiple Canned Responses Fixed in development Crash with no stack trace Already fixed in newer version Fixed in stable Bad description Bad description and crash Bad stack trace Obsolete version Duplicate and not fixed Duplicate and needs more info Duplicate and fixed Need info and old
There are no breakpoints on blank lines. Attempting to set a breakpoint on an empty line sets the breakpoint on the next breakable line. This is expected behavior. Closing report.
Dan's patch from comment #1 has been applied. It doesn't seem to fix this completely, but additionally applying file #36533 from bug #46632 seems to fix it.
Retagging release from 4.0.0-rc2 to 4.0.0.
Must save file to set breakpoints. There's a patch here that might be more robust, not sure:
https://savannah.gnu.org/patch/?func=detailitem&item_id=8006
to replicate: - create a new file - enter a single line - set a breakpoint at the first line - save file - now insert more non-blank lines - try to set breakpoints at every line [not all of the lines will have a breakpoint]
(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)
Attach Files: Comment:
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Only project members can vote.
Please enter the title of George Orwell's famous dystopian book (it's a date):
Follow 6 latest changes.
Copyright © 2022 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved. The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team. Source Code
Powered by Savane 3.9