#Simpleimage has no attribute seek for free
#Simpleimage has no attribute seek portable

OSC 1338 options ^G plain-text OSC 1338 base64-data ^G One possibility (I randomly picked 1338): A third is the lack of robustness (fallback) on non-supporting terminals. Another is that extensibility is limited because of the lack of quoting and escaping. A minor awkwardness is that inline=0 is the default.

We could standardize on the iterm2 1337 sequence, but it has some problems. It would be better to use JSON for options. The iterm2 supports key=value pairs, which is somewhat extensible, but the format of values is restricted. Some terminals may allow user switching between the text and the image. It can also be used by screen readers, and as hover text. The plain text is used on terminals that don't understand the image. Is it important to to use an escape sequence that is will safely fallback to plain text on terminals that don't support images? (After all - you probably wouldn't want to send a large image to a terminal that can't handle it.) If so, we need two escape sequences: An initial OSC sequence, followed by optional plain text, followed by a final OSC sequence. If not found, it searches for image URL in data-rsTmb attribute of slide and. This may need some special care (hacks?) in case the image caused scrolling. If you have any problems, looking for some specific solution, or have a. StringIO turns an ordinary string into a file-like object, complete with seek method. But the urlopen gives us something that is missing: seek. Use the StringIO library to fix the problem.

#Simpleimage has no attribute seek portable

The portable way to erase or replace a previously-drawn image would be to save-cursor before writing the image, and then restore-cursor before replacing it. Except that it doesn't have a seek function. However, using an extra-large character cell is preferable, as it does not require padding to an integer number of lines. Both should be allowed when using default options. Other terminals may allocate may allocate as many lines and columns as needed for the image to fit. Inline images could be a less-portable extension.) We can also make it unspecified how many lines are taken by the image: Some terminals may create an image as a single logical line, with a single extra-large character cell. Any others? For interoperability we should focus on png, jpeg, and gif (including animated) images with the data encoded in base64.īasic support could be restricted to images starting at the left column, with no further output to the right of the image. DomTerm has a more general escape sequence where you can send arbitrary (sanitized) HTML: to display an image: just send an element. There is the sixel format but that is long obsolete. The setup: 2 columns (1/3 + 2/3) first column includes one simple image with 7px border and no other propertie second column includes on text.

#Simpleimage has no attribute seek for free

Prior art that I know of includes item2 ( ). New issue FileObject instance has no attribute 'seek' 344 Closed seanmavley opened this issue on 2 comments seanmavley on vstoykov closed this as completed on vstoykov added the invalid label on Sign up for free to join this conversation on GitHub. It would be useful to standardize an escape sequence for displaying images inline in the terminal output.