Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match " after embedded expression #1798

Closed
danrubel opened this issue Feb 22, 2012 · 14 comments
Closed

Match " after embedded expression #1798

danrubel opened this issue Feb 22, 2012 · 14 comments
Assignees
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Milestone

Comments

@danrubel
Copy link

[user feedback]
When typing
print("${blah}

when I then type a closing ", the editor puts in two ""

eg,
print("${blah}""

  • I think that it should try to match with the first "

cheers,
Chris.
////////////////////////////////////////////////////////////////////////////////////
Editor Version: 4349
////////////////////////////////////////////////////////////////////////////////////
OS: Windows 7 - amd64 (6.1)
experimental/projectsview = false
experimental/filesview = false
SDK installed = true
Dartium installed = false
////////////////////////////////////////////////////////////////////////////////////

@DartBot
Copy link

DartBot commented Feb 22, 2012

This comment was originally written by bb...@hotmail.com


you don't need to type the closing one...

if you write this: print("

it should be auto-expanded to: print("")

on my pc it actually works (win7/64/dart editor 4349)

@bwilkerson
Copy link
Member

I saw both bugs (not inserting the closing quote and doubling the closing quote) on my Mac using build 4539.

@bwilkerson
Copy link
Member

Issue #1820 has been merged into this issue.

@danrubel
Copy link
Author

danrubel commented Mar 6, 2012

Set owner to @stevemessick.

@stevemessick
Copy link
Contributor

Changing to enhancement since the current behavior is working as intended, but it could use improvement.


Removed Type-Defect label.
Added Type-Enhancement label.

@clayberg
Copy link

clayberg commented Jun 1, 2012

Added this to the Later milestone.

@sethladd
Copy link
Contributor

Confirmed.


Removed this from the Later milestone.
Added this to the M6 milestone.
Removed Type-Enhancement label.
Added Type-Defect label.

@stevemessick
Copy link
Contributor

Removed this from the M6 milestone.
Added this to the Later milestone.
Removed Priority-Low label.
Added Priority-Medium label.

@sethladd
Copy link
Contributor

I put this into M6 with Dan R's approval.


cc @danrubel.
Removed this from the Later milestone.
Added this to the M6 milestone.

@stevemessick
Copy link
Contributor

Removed the owner.
Added PatchesWelcome label.

@sethladd
Copy link
Contributor

As per an above comment, here's a better way to solve it:

type this:

print(

The editor should auto-add this:

print()

Then type this:

print("

The editor should auto-close like this:

print("")

Sublime does this very well, and it's super useful and makes typing much faster.

@stevemessick
Copy link
Contributor

As mentioned in comment #­1, the editor historically did insert pairs of quotes. I recently broke that behavior in argument lists when I made an enhancement to code completion. It will be fixed soon.

I investigated this issue a couple months ago, during an auto-edit bug sweep. I believe the problem reported originally only occurs when you type everything including the closing paren, then backspace over the closing quote. When you re-type the "closing" quote the editor doesn't recognize it as a close-quote and inserts a matched pair.

@sethladd
Copy link
Contributor

I'd be happy to close this issue if we add back the auto-close of ' and " and ( and [

@stevemessick
Copy link
Contributor

I believe the original behavior has been restored. Feel free to re-open this one if it isn't working, modulo the currently open issue of ('') not auto-closing when typed really fast.


Set owner to @stevemessick.
Added NotPlanned label.

@danrubel danrubel added Type-Defect closed-not-planned Closed as we don't intend to take action on the reported issue labels Jun 27, 2013
@danrubel danrubel added this to the M6 milestone Jun 27, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue
Projects
None yet
Development

No branches or pull requests

6 participants