Re: Back quote typo in error messages (?)
On 16 February 2017 at 19:02, Jeff King wrote: > Try the "Quoted Text" section of the original asciidoc user manual: > > http://www.methods.co.nz/asciidoc/userguide.html#X51 > > Asciidoctor has introduced some new syntax (almost certainly because the > original asymmetric formulations have a bunch of ambiguous corner > cases). By default, it disables the asymmetric versions, but they work > in "compat" mode (and the newer ones do not). I can't say I had the pleasure of using Asciidoctor 0.1.4 or earlier! :) > Git's documentation is all written for the original asciidoc. If you > build it with asciidoctor, it must be done in compat mode. This is the > default when asciidoctor sees a two-line (i.e., underlined) section > title, which all of our manpages have. And I definitely didn't know that, but now I'm glad we went OT! :) Thanks a lot for the clarifications.
Re: Back quote typo in error messages (?)
On 15 February 2017 at 21:56, Jeff King wrote: > Grep for "``" in Git's documentation directory, and you will see many > examples (asciidoc only accepts the double-quote form, not singles). > > You can also try: > > echo "this is \`\`quoted'' text" >foo.txt > asciidoc foo.txt > > and then open "foo.html" in your browser. We are probably going a bit OT here :) but AFAIK there is no such thing as non-symmetric start/end quotes in AsciiDoc. Even enclosing something in curved quotes is done as follows: '`single curved quotes`' "`double curved quotes`" (http://asciidoctor.org/docs/asciidoc-syntax-quick-reference/) > I think patches would be welcome, but as Junio said, it probably should > wait for the next cycle. It can definitely wait and I would be glad to contribute!
Re: Back quote typo in error messages (?)
On 15 February 2017 at 21:21, Jeff King wrote: > On Wed, Feb 15, 2017 at 09:06:46PM +0000, Fabrizio Cucci wrote: >> Shouldn't the wrong flag be surrounded by two single quotes instead of >> a back quote and a single quote? > > Some people use the matched backtick/single-quote to emulate the > non-symmetric start/end quotes used in traditional typography (and in > fact, ``foo'' in languages like asciidoc are typically rendered using > smart-quotes). I definitely didn't know about the use of them in traditional typography! But I couldn't find any example of non-symmetric quotes in AsciiDoc... > So I think what you are seeing is not wrong in the sense of being > unintended by the author of the message. I had the opposite impression from the quick search in the GitHub repo, this is why I wrote here looking for some confirmation. > I don't know how much we care about standardizing that punctuation. I mentioned it was very minor but, still, in my opinion a project like Git deserves consistent punctuation! :)
Back quote typo in error messages (?)
Hello everyone, it's been a couple of days that I keep noticing something (very minor) that my OCD for symmetric things can't really stand. If you run the following command: $ git branch --i-dont-exists you should get: error: unknown option `i-dont-exists' Shouldn't the wrong flag be surrounded by two single quotes instead of a back quote and a single quote? For the sake of completeness, I'm on Mac running Git 2.10.1. Thanks, Fabrizio
error: Can't cherry-pick into empty head
Hello everyone, I'm trying to understand why I'm getting the error as per subject. The scenario is the following: I'm on the master branch (which contains several commits) and I would like to create a new empty branch (let's call it new-orphan) and cherry-pick only the commits related to a specific folder (let's call it my-folder) from the master branch. So, I tried the following command sequence: master $ git checkout --orphan new-orphan new-orphan $ git rm --cached -r . new-orphan $ git clean -df After confirming that I'm in a clean state (with "$ git status") I tried: new-orphan $ git rev-list --reverse master -- my-folder/ | git cherry-pick --stdin as suggested https://git-scm.com/docs/git-cherry-pick, but what I get is "error: Can't cherry-pick into empty head". What I don't really understand is: 1) if I cherry-pick a single commit instead of multiple commits, everything works fine: new-orphan $ git cherry-pick 2) if I commit something before trying the above command, everything works fine: new-orphan $ touch README new-orphan $ git add README new-orphan $ git commit -m "added README" new-orphan $ git rev-list --reverse master -- my-folder/ | git cherry-pick --stdin Can someone please help me understand this? Thanks, Fabrizio -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html