Redglyph

> This 404 initiative now 🙂 Would that be this link now? https://github.com/orgs/rust-lang/projects/16/views/1

Sorry to wake up an old PR, is this currently supported? I have source code with callouts but I can't seem to use them in anything other than a list...

Thanks for your reply @ggrossetie > As mentioned by Dan in [#1077 (comment)](https://github.com/asciidoctor/asciidoctor/issues/1077#issuecomment-234064793), you can write an inline macro but this feature is not available in core (since this issue...

> It's odd, another ast explorer works. https://astexplorer.net/#/gist/fc7356a18684fd9d898a048034044263/3d8e01de427ca159edd904827886d9b6e6bb1b6e This one is the old version of syn (see at the top right: it's version 1). My issue is about version 2:...

@jade-nl Interesting that you get the same number for both lenses. I found that data by extracting the EXIF with exiv2: ``` Exif.NikonLd4.LensIDNumber Byte 1 253 ``` That means this...

Here's a [relevant part of the code](https://github.com/darktable-org/darktable/blob/e4ce86816380db875db42f4fe965c86d8f99af91/src/common/exif.cc#L1667-L1675) that someone else had spotted when I discussed that issue on pixls.us: ```c else if(Exiv2::testVersion(0,27,4) && FIND_EXIF_TAG("Exif.NikonLd4.LensID") && pos->toLong() == 0) { //...

I don't understand any more. Now, not only using `.exiv2` in my home directory doesn't work any more, but I have to put either "253" or "0". I'm **sure** that...

> The "1 0" you had was nonsense for .exiv2 - the "1" came from the _count_ of values in a tag (i.e. the "c" option in the default -Pkyct...

When I see [the list of models](https://github.com/Exiv2/exiv2/blob/v0.27.5-RC1/src/nikonmn_int.cpp#L1898) just in the case of Nikon, in the exiv2 project... I wonder if there's a simple exiv2 command to print out those columns...

> The best thing to do here in the meantime is I guess to ensure the `Exif.Photo.LensModel` fallback still happens w/o the need for a .exiv2 workaround: either add yet...