Karthik Chikmagalur writes:
>> Probably, we can extend the regexp to treat things like px/pt as pixel
>> width as well.
>>
>> I suggest doing it in a separate patch rather than making many changes
>> together with introducing a new feature as you suggested. Having too
>> many things in a single c
> Probably, we can extend the regexp to treat things like px/pt as pixel
> width as well.
>
> I suggest doing it in a separate patch rather than making many changes
> together with introducing a new feature as you suggested. Having too
> many things in a single commit can lead to confusion.
Okay.
Karthik Chikmagalur writes:
> Due to the change in 50be048ad0cbe0e9150ca2351b894b041ae7cf49, image
> display specifications like
>
> #+attr_org: 300px
>
> don't work. From the commit message, it looks like the intent was to
> ignore specifications like :width 4in. I'm not sure if ignoring "px"
> Due to the change in 50be048ad0cbe0e9150ca2351b894b041ae7cf49, image
> display specifications like
>
> #+attr_org: 300px
>
> don't work. From the commit message, it looks like the intent was to
> ignore specifications like :width 4in. I'm not sure if ignoring "px"
> specifications was intentio
Due to the change in 50be048ad0cbe0e9150ca2351b894b041ae7cf49, image
display specifications like
#+attr_org: 300px
don't work. From the commit message, it looks like the intent was to
ignore specifications like :width 4in. I'm not sure if ignoring "px"
specifications was intentional.
If this
