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

[TW-250] Opening parenthesis in description gets padded in task 2.0.0 bet 2 #293

Closed
taskwarrior opened this issue Feb 12, 2018 · 5 comments
Labels
type:bug Something isn't working
Milestone

Comments

@taskwarrior
Copy link

Michelle Crane on 2011-09-27T12:02:24Z says:

I tend to use parentheses/brackets occasionally in task descriptions. I noticed that when I add them, the opening bracket gets padded with an extra space after it. See trace - I input @(brackets)@ and got back @( brackets)@. This doesn't happen in 1.9.4.

F:\Dropbox\TextFiles>task200beta2\bin\task add Testing with (brackets) here
Created task 90.

F:\Dropbox\TextFiles>task200beta2\bin\task new

ID Project ! Due        Count   * + R Dep Description                                                                       Age
* - ------- - ---------- ------- - - - --- --------------------------------------------------------------------------------- ---
90                                        Testing with ( brackets) here                                                      7s
@taskwarrior taskwarrior added this to the 2.4.0 milestone Feb 12, 2018
@taskwarrior taskwarrior added type:bug Something isn't working fixed labels Feb 12, 2018
@taskwarrior
Copy link
Author

Migrated metadata:

Created: 2011-09-27T12:02:24Z
Modified: 2014-06-08T14:29:25Z

@taskwarrior
Copy link
Author

Paul Beckingham on 2011-09-29T02:53:02Z says:

Wow, looks like you found a Redmine markup bug too. You can't stop, can you?

@taskwarrior
Copy link
Author

Paul Beckingham on 2012-02-26T19:16:31Z says:

No workaround yet.

It's ugly, but this is a fundamental parser issue that means this will likely be deferred.m

@taskwarrior
Copy link
Author

Paul Beckingham on 2012-02-26T22:48:40Z says:

Deferring.

This is a consequence of moving towards being able to perform math, such as "due:today + 3". Now it should be possible to have the parser decide it is not math, and revert to other interpretations, but that isn't possible yet. There are several parser-related issues that cannot be addressed yet.

Recategorized to 'parser'.

@taskwarrior
Copy link
Author

Paul Beckingham on 2012-10-19T04:23:07Z says:

Parsing issues will be addressed after the task server support release.

djmitche added a commit to djmitche/taskwarrior that referenced this issue May 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant