Footnote after exclamation

Vince's Avatar

Vince

21 Oct, 2017 09:21 PM

This doesn't work![^3]

When a footnote comes after an exclamation point, the number in the brackets turns red in the editor window, the display window shows the literal [^3] instead of the superscript 3, and doesn't show the footnote text itself at the bottom. If I delete the exclamation, it works, i.e. the superscript and the footnote text appears in the display window. If I put a space between the exclamation and the [^3], it still doesn't work.

We should obviously be able to have footnotes after exclamations. How do we do so?

  1. Support Staff 1 Posted by Fletcher on 27 Oct, 2017 03:29 PM

    Fletcher's Avatar

    `![foo]` is the Markdown code for an image.

    You would have to escape the `!` if you did not want it to trigger an image:

    \![foo]

    Or you could insert a space between the two:

    !<space>[foo]

    F-

  2. 2 Posted by Vince Rice on 27 Oct, 2017 03:33 PM

    Vince Rice's Avatar
    I'll try escaping it, but as I said, a space doesn't work, either.

    If I put a space between the exclamation and the [^3], it still doesn't work.




    On Oct 27, 2017, at 10:29 AM, Fletcher <[email blocked]> wrote:

    // Please reply above this line 
    ================================================== 

    From: Fletcher (Support staff)

    `![foo]` is the Markdown code for an image.

    You would have to escape the `!` if you did not want it to trigger an image:

    \![foo]

    Or you could insert a space between the two:

    !<space>[foo]

    F-

    On Sat, Oct 21 at 02:21 PM PDT, Vince wrote:

    This doesn't work![^3]

    When a footnote comes after an exclamation point, the number in the brackets turns red in the editor window, the display window shows the literal [^3] instead of the superscript 3, and doesn't show the footnote text itself at the bottom. If I delete the exclamation, it works, i.e. the superscript and the footnote text appears in the display window. If I put a space between the exclamation and the [^3], it still doesn't work.

    We should obviously be able to have footnotes after exclamations. How do we do so?

    Having trouble reading this? View this discussion online: Footnote after exclamation.

    Reply with #ignore to stop receiving notifications for this discussion.


  3. Support Staff 3 Posted by Fletcher on 27 Oct, 2017 04:00 PM

    Fletcher's Avatar

    Yes it does.

    Sent from my iPhone

    > On Oct 27, 2017, at 11:33 AM, Vince Rice <[email blocked]> wrote:
    >
    >
    > // Please reply above this line
    > ==================================================
    >
    > From: Vince Rice <[email blocked]>
    >
    > I'll try escaping it, but as I said, a space doesn't work, either.
    >>
    >> If I put a space between the exclamation and the [^3], it still doesn't work.
    >>
    >
    >
    >
    >> On Oct 27, 2017, at 10:29 AM, Fletcher <[email blocked]> wrote:
    >>

  4. 4 Posted by Vince Rice on 27 Oct, 2017 06:47 PM

    Vince Rice's Avatar

    What are you, three? :) No, it doesn't. It might work for you, but it didn't work for me.

    > On Oct 27, 2017, at 11:00 AM, Fletcher <[email blocked]> wrote:
    >
    > // Please reply above this line
    > ==================================================
    >
    > From: Fletcher (Support staff)
    >
    > Yes it does.
    >
    > Sent from my iPhone
    >
    > > On Oct 27, 2017, at 11:33 AM, Vince Rice <[email blocked]> wrote:
    > >
    > >
    > > // Please reply above this line
    > > ==================================================
    > >
    > > From: Vince Rice <[email blocked]>
    > >
    > > I'll try escaping it, but as I said, a space doesn't work, either.
    > >>
    > >> If I put a space between the exclamation and the [^3], it still doesn't work.
    > >>
    > >
    > >
    > >
    > >> On Oct 27, 2017, at 10:29 AM, Fletcher <[email blocked]> wrote:
    > >>
    >
    > On Fri, Oct 27 at 08:33 AM PDT, Vince Rice wrote:
    >
    > I'll try escaping it, but as I said, a space doesn't work, either.
    >> If I put a space between the exclamation and the [^3], it still doesn't work.
    >>
    >
    >
    >
    >> On Oct 27, 2017, at 10:29 AM, Fletcher <[email blocked] <x-msg://16/***@***>> wrote:
    >>

  5. Support Staff 5 Posted by Fletcher on 27 Oct, 2017 07:38 PM

    Fletcher's Avatar

    I'll make you a wager...

    If I'm right, then when you write for support issues you pause for a
    second before composing your message and consider the fact that you
    could be wrong and that your opinions are just that -- opinions. You
    are entitled to your opinions whether others agree or not (including
    myself). But sometimes you seem to miss the distinction between a
    validly held (but perhaps not always shared) opinion, and an inaccurate
    understanding of a fact. I find when I pause to do this that my messages
    to other developers tend to come across as much more neutral and garner
    a much better response than when I start off on the "offensive" -- which
    is easy to do unintentionally when writing for support after dealing
    with a frustrating issue.

    If you're right, then I will ignore anything in your messages that could
    be (mis)construed as argumentative and respond solely on the facts of
    your question and do my absolute best not to get irritated at my
    (possibly incorrect) interpretation of your tone (especially since tone
    doesn't transmit well via email). As I have stated previously, you have
    discovered more than your share of bugs which has certainly helped
    improve the quality of the program. At times, however, the
    "frustration-to-payoff ratio" of our discussions can stay on the high
    side (a feeling you probably share at times as well).

    Whether you agree with the wager or not, the "answer" to your issue is
    that you are probably typing a space and watching the preview,
    forgetting that space characters do not update the preview (as we have
    previously discussed at length, as I attempted to explain that Apple's
    code does strange things when typing spaces under certain
    circumstances). Manually refresh the preview, and you'll see that it
    does work.

    Or type two spaces and then delete one. It still works.

    Alternatively, paste the following in your document (avoiding the space
    issue altogether), and you'll see that a space character does in fact
    work to trigger a footnote instead of an image:

    test! [^1]

    [^1]: foo

    F-

    PS> Another, but far less likely explanation, since I believe you
    understand this point already -- if you enabled "strict" Markdown mode,
    then footnotes won't work at all. But in this case, they wouldn't work
    following a period either, which you already stated do work. Same with
    disabling the footnote support specifically.

    On 10/27/17 2:48 PM, Vince Rice wrote:
    > // Please reply above this line
    > ==================================================
    >
    > *From*: Vince Rice <[email blocked]>
    >
    > What are you, three? :) No, it doesn't. It might work for you, but it
    > didn't work for me.
    >
    > > On Oct 27, 2017, at 11:00 AM, Fletcher
    > <[email blocked]
    > <mailto:[email blocked]>> wrote:
    > >
    > > // Please reply above this line
    > > ==================================================
    > >
    > > From: Fletcher (Support staff)
    > >
    > > Yes it does.
    > >
    > > Sent from my iPhone
    > >
    > > > On Oct 27, 2017, at 11:33 AM, Vince Rice <[email blocked]> wrote:
    > > >
    > > >
    > > > // Please reply above this line
    > > > ==================================================
    > > >
    > > > From: Vince Rice <[email blocked]>
    > > >
    > > > I'll try escaping it, but as I said, a space doesn't work, either.
    > > >>
    > > >> If I put a space between the exclamation and the [^3], it still
    > doesn't work.
    > > >>
    > > >
    > > >
    > > >
    > > >> On Oct 27, 2017, at 10:29 AM, Fletcher <[email blocked]> wrote:
    > > >>
    > >
    > > On Fri, Oct 27 at 08:33 AM PDT, Vince Rice wrote:
    > >
    > > I'll try escaping it, but as I said, a space doesn't work, either.
    > >> If I put a space between the exclamation and the [^3], it still
    > doesn't work.
    > >>
    > >
    > >
    > >
    > >> On Oct 27, 2017, at 10:29 AM, Fletcher <[email blocked]
    > <x-msg://16/***@***>> wrote:
    > >>
    >
    > On Fri, Oct 27 at 09:00 AM PDT, Fletcher wrote:
    >
    > Yes it does.
    >
    > Sent from my iPhone
    >
    > > On Oct 27, 2017, at 11:33 AM, Vince Rice

  6. 6 Posted by Vince Rice on 27 Oct, 2017 08:54 PM

    Vince Rice's Avatar

    I'm not clear on what the wager is supposed to be, but I'm not much for gambling, anyway…

    To summarize:
    I reported something didn't work, with details, and asked how to get it to work.
    You told me how to get it to work (escape it), which was perfect (I didn't remember that ![] is an image, and don't know how I would have (re)discovered it. I also don't think about escaping anything in an MD document; I don't think I've ever had reason to do so.) But then you told me I could also do something I specifically said in #1 that I had already tried and didn't work.
    I said thanks for the escape hint. I also assumed you hadn't read far enough in the email to see that I'd already tried the space, something all of us do occasionally. Just for completeness, I pointed out, again, that I already tried the space, and it didn't work.
    You replied with nothing more than "Yes it does".
    I replied with a bit of sarcasm, but I included a smiley to indicate I was joking around.
    You wrote a novel how my interaction is lacking.

    #3-6 were unnecessary. All you had to say in your first reply (#2) was, "A space works too; don't forget the space issue in preview," I would have said to my self, "Ahhh, right," and that would have been the end of it. If you really did miss my statement in #1 that I had tried that, then you could have said that in #4 instead of an argumentative "Yes it does", and that would have been the end of it.

    Now that you say it, I do remember the space preview issue. But no, I don't remember that it exists on an ongoing basis, because on an ongoing basis, I don't see it. The fact that it's top of mind to you as a developer doesn't mean it's top of mind for your users. I've seen that issue exactly once in my entire life (anywhere, in any program, not just MMD), two (three?) months ago. I could have reflected from now until Christmas and never would have remembered it. And, as an aside, even now that you bring it up, I thought I remembered that you did some work to fix that during the beta process. Apparently I mis-remembered. That's never happened before… (See, that was a joke. :)

    Regardless, on this particular issue, you had two opportunities to explain and blew past them both. This wasn't a big deal to me at all; I was happy with the escape. (I don't want a space between the two, even if it does work.)

    As to the rest, two things, both of which I believe we've talked about before.
    One, tone is missing from email, but I'll assure you, again, that I'm not mad, upset, etc., in any discussions we've had, including this one (I really wasn't on this one, I was more amused after #4.). I write for clarity, not emotion. If my words convey otherwise, I can only apologize (sincerely) and say maybe one day I'll learn to use better words.
    Two, I'm always going to argue for things I believe in. Just as you do. I have a perspective you don't have — I'm a user. You have a perspective I don't have — you're the developer. I know I'm only one user. But I'm one user with experience in a lot of software and UI/UX. I have, I believe, quit on most issues after a second round of emails. I disagree with several decisions that have been made, but at the end of the day it's your program, not mine, and once it's clear you're not going to be persuaded, I move on. But I'm almost always going to engage in a second round, just to address what you said in the first if it doesn't persuade me (or isn't applicable). And I, of course, am going to think I'm right. (Just as you do. Just as I expect you do.) It wouldn't make much sense for either of us to argue something we don't believe in. The whole point of discussion/debate/whatever you want to call it is to move people off their opinion onto yours. That's what I do, that's what you do, that's what all of us do.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac