Describe the bug LookAtMe does not run on M1 Macs

To Reproduce

Install lookatme with pip

python3 -m pip install lookatme

Check the installed version

lookatme --version

Expected behavior …to see the version

Screenshots

Traceback (most recent call last):
  File "/opt/homebrew/bin/lookatme", line 33, in <module>
    sys.exit(load_entry_point('lookatme===-VERSION-', 'console_scripts', 'lookatme')())
  File "/opt/homebrew/bin/lookatme", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/opt/homebrew/Cellar/[email protected]/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/opt/homebrew/Cellar/[email protected]/3.9.4/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 790, in exec_module
  File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
  File "/opt/homebrew/lib/python3.9/site-packages/lookatme/__main__.py", line 17, in <module>
    import lookatme.tui
  File "/opt/homebrew/lib/python3.9/site-packages/lookatme/tui.py", line 16, in <module>
    from lookatme.contrib import shutdown_contribs, contrib_first
  File "/opt/homebrew/lib/python3.9/site-packages/lookatme/contrib/__init__.py", line 15, in <module>
    from . import file_loader
  File "/opt/homebrew/lib/python3.9/site-packages/lookatme/contrib/file_loader.py", line 42, in <module>
    class FileSchema(Schema):
  File "/opt/homebrew/lib/python3.9/site-packages/lookatme/contrib/file_loader.py", line 49, in FileSchema
    default=LineRange().dump(LineRange()),
  File "/opt/homebrew/lib/python3.9/site-packages/marshmallow/schema.py", line 547, in dump
    result = self._serialize(processed_obj, many=many)
  File "/opt/homebrew/lib/python3.9/site-packages/marshmallow/schema.py", line 515, in _serialize
    value = field_obj.serialize(attr_name, obj, accessor=self.get_attribute)
  File "/opt/homebrew/lib/python3.9/site-packages/marshmallow/fields.py", line 318, in serialize
    return self._serialize(value, attr, obj, **kwargs)
  File "/opt/homebrew/lib/python3.9/site-packages/marshmallow/fields.py", line 898, in _serialize
    ret = self._format_num(value)  # type: _T
  File "/opt/homebrew/lib/python3.9/site-packages/marshmallow/fields.py", line 873, in _format_num
    return self.num_type(value)
TypeError: int() argument must be a string, a bytes-like object or a number, not 'Integer'

Environment (please complete the following information):

• OS: OS X — Big Sur
• Lookatme Version [e.g. lookatme --version] 👈🏾 👈🏾 👈🏾 this is the issue 😅

Additional context n/a

This PR adds a way to separate a slide into multiple parts and show them progressively. Parts are separated by creating a ::: line.

Here is an example. This presentation:

# This is a normal slide

With some content.

---

# This is a multi-part slide

- This is the first part.

:::

- And this is the second part.

:::

- Parts are separated by a `:::` paragraph.

Looks like this:

This feature provides a way to do #80, except numbered list won't work :/

I picked ::: as the part delimiter because it looks similar to the --- slide delimiter and I felt it was unlikely to cause conflicts with real content, but I am happy to change it to anything else if you prefer.

Describe the bug

Setting theme to light/dark with -t light and -t dark doesn't seem to have any effect.

Screenshots

lookatme slides.md with dark background terminal:

lookatme slides.md with light background terminal:

lookatme -t light slides.md with light background terminal:

It sounded from the help text like -t light should make the colors more readable on a light background, but it doesn't seem to have any effect.

Environment (please complete the following information):

• OS: Arch Linux
• Lookatme Version: 2.3.2
• Terminal: Alacritty

Hi,

Sorry if this was something obvious but I couldn't find it in the documentation, is it possible to have a single slide only?

I use it this when I write documentation in MD and sometimes having to scroll through all the slides is a bit annoying.

Thanks lp

lookatme.log Describe the bug Loading the second slide in the examples/tour.md document causes lookatme to crash with the following error:

Error rendering slide 2: 'DequeCommandTransmitter' object has no attribute 'transmitter'
See /tmp/lookatme.log for traceback
Aborted!

I get that it's probably really weird to be using this over SSH, but my work laptop's display output doesn't work with my KVM, so I tend to just SSH into it from my desktop. I've attached a log after running lookatme --debug tour.md

To Reproduce

1. Connect to a remote host over SSH
2. lookatme tour.md

Expected behavior

Either the slideshow should run (which given the Ueberzug and Terminal extensions is probably unrealistic) , or should gracefully handle errors caused by being run over SSH.

Environment (please complete the following information):

• OS: Arch Linux (btw)
• Lookatme Version: 2.3.2 installed via pip

lookatme.log

Describe the bug A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

1. Go to examples cd examples/file_loader_ext
2. Show the slide lookatme example.md

Expected behavior A embedded terminal as in the screencast in the README.

Screenshots What I see is:

Environment (please complete the following information):

• OS: arch (5.11.14-arch1-1)
• Lookatme Version: 2.3.0

Additional context My first time trying out lookatme so not sure I missed something

Describe the bug numbered lists are rendered as bullet lists

To Reproduce

• create a md file with

1. a
2. b
3. c

• run lookatme on it

Expected behavior should render a numbered list

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: Linux 5.8.6-1-MANJARO
• Lookatme Version: 1.2.0

This isn't really a bug or a feature request. But, I noticed that building this package on NixOS as provided by nixpkgs introduces 3 binaries which seem referenced in your setup.py but which appear redundant, there. However, it appears that these nixpkgs build outputs have different SHAs, so they're different somehow.

$ md5sum result/bin/*                                                
27e4ed6a63db72685e78134d658c8030  result/bin/lam
00061159564841356ae9f5a91fc2405a  result/bin/lookatme
a5b7324681c66ed3a427fa48dc9b2f36  result/bin/witnessme

Could you please shed some light on how they're different or why there are other outputs beyond only ./result/bin/lookatme?

Describe the bug I'm trying to update the Debian package of lookatme to 2.3.2, but the build fails because of failing unit tests (with 2.3.0 it still succeeds):

I: pybuild base:232: cd /home/reiner/Source/debian/lookatme/lookatme/.pybuild/cpython3_3.9_lookatme/build; python3.9 -m pytest tests
============================= test session starts ==============================
platform linux -- Python 3.9.2, pytest-6.0.2, py-1.10.0, pluggy-0.13.0
rootdir: /home/reiner/Source/debian/lookatme/lookatme
plugins: cov-2.10.1, mock-1.10.4
collected 31 items

tests/test_cli.py ...                                                    [  9%]
tests/test_contrib.py .                                                  [ 12%]
tests/test_file_loader.py ....                                           [ 25%]
tests/test_markdown.py ...........                                       [ 61%]
tests/test_parse.py .....                                                [ 77%]
tests/test_schemas.py .FF.                                               [ 90%]
tests/test_table.py ...                                                  [100%]

=================================== FAILURES ===================================
__________________ test_sanity_check_that_errors_are_detected __________________

    def test_sanity_check_that_errors_are_detected():
        """Perform a sanity check that we can actually catch errors in generating
        the default schema values.
        """
        schema = MetaSchema()
    
        # force a discrepancy in the
        gend_default = MetaSchema().dump(None)
        gend_default["styles"]["padding"]["left"] = 100
    
        with pytest.raises(AssertionError) as excinfo:
>           _validate_field_recursive("__root__.styles", schema.styles.nested(), gend_default['styles'])
E           AttributeError: 'MetaSchema' object has no attribute 'styles'

tests/test_schemas.py:64: AttributeError
_____________________________ test_styles_defaults _____________________________

    def test_styles_defaults():
        """Ensure that style value defaults are generated correctly
        """
        schema = MetaSchema()
        gend_default = MetaSchema().dump(None)
>       _validate_field_recursive("__root__.styles", schema.styles.nested(), gend_default['styles'])
E       AttributeError: 'MetaSchema' object has no attribute 'styles'

tests/test_schemas.py:73: AttributeError
=============================== warnings summary ===============================
/usr/lib/python3/dist-packages/marshmallow/fields.py:173: 72 warnings
  /usr/lib/python3/dist-packages/marshmallow/fields.py:173: RemovedInMarshmallow4Warning: The 'default' argument to fields is deprecated. Use 'dump_default' instead.
    warnings.warn(

/usr/lib/python3/dist-packages/marshmallow/fields.py:181: 16 warnings
  /usr/lib/python3/dist-packages/marshmallow/fields.py:181: RemovedInMarshmallow4Warning: The 'missing' argument to fields is deprecated. Use 'load_default' instead.
    warnings.warn(

/usr/lib/python3/dist-packages/marshmallow/fields.py:218
  /usr/lib/python3/dist-packages/marshmallow/fields.py:218: RemovedInMarshmallow4Warning: Passing field metadata as a keyword arg is deprecated. Use the explicit `metadata=...` argument instead.
    warnings.warn(

.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
.pybuild/cpython3_3.9_lookatme/build/tests/test_schemas.py::test_meta_defaults
  /usr/lib/python3/dist-packages/marshmallow/fields.py:438: RemovedInMarshmallow4Warning: The 'default' attribute of fields is deprecated. Use 'dump_default' instead.
    warnings.warn(

-- Docs: https://docs.pytest.org/en/stable/warnings.html
=========================== short test summary info ============================
FAILED tests/test_schemas.py::test_sanity_check_that_errors_are_detected - At...
FAILED tests/test_schemas.py::test_styles_defaults - AttributeError: 'MetaSch...
================== 2 failed, 29 passed, 98 warnings in 1.54s ===================
E: pybuild pybuild:353: test: plugin distutils failed with: exit code=1: cd /home/reiner/Source/debian/lookatme/lookatme/.pybuild/cpython3_3.9_lookatme/build; python3.9 -m pytest tests

Expected behavior Unit tests are passing.

Environment (please complete the following information):

• OS: Debian Linux (unstable)
• Lookatme Version 2.3.2

Hi,

I recently packaged lookatme for Debian, as I think it is a cool presentation tool. :-) I wanted to update the package now to the current release, but noticed that you have included the file examples/napoleon_dynamite.jpg, which is not freely licensed.
Could you please replace it with some picture under a free license? This would make packaging easier, as I could re-use your released tarballs, instead of repacking them (and removing the image).

The -s option flag is used for both style and safe options. It seems the last use wins, so remove -s for style since it was declared first.

Too bad Click does not complain about that.

Describe the Feature Request ' A screenshot utility script should exist in bin/ that is part of the development tools for lookatme. It should be able to take slides and a series of keystrokes, and render a gif of the slides in action.

E.g.

bin/lookatme-screenshot test.md -o slides.gif --gif --keys scroll_down:3,j:1.5,j:1.5,j:1.5 --width X --height Y

This should scroll to the bottom of the first slide over three seconds, and press "j" (or next slide") with a 1.5s delay in between.

Additional notes

One approach:

1. Create presentation from markdown source
2. Generate canvases after each keystroke
3. Convert each canvas to raw html
4. Load each html into chrome via selenium, with browser width/height set to the provided width/height
5. Save screenshot of each html into a folder
6. Create a gif with provided delays from the screenshots (maybe using ImageMagick's convert?)

Describe the Feature Request

Developer documentation should be added via the @tutor decorator, using the "Development" category (or something similar). These shouldn't be shown be default with lookatme --tutorial, but should be when explicitly searched for / pulled up.

Describe the bug

All tokens that are possibly produced form markdown-it-py should be supported.

lookatme should have a unit test that validates that it can handle anything markdown-it-py can produce.

Describe the Feature Request

I don't know if this has another name, but I like to think of it as a grapevine.

Many aspects of lookatme are generated by the current state of the project:

• The version number embedded in a few places
• The current help text in the documentation
• Changelog since the last version
• etc.

These shouldn't be something that actually require a separate commit to update, but should be dynamically inserted into the code, with the updated code itself being treated as an artifact (having placeholders for the version number, help text, etc. be replaced by their current values).

It should go something like this:

    grapevine                  tag-the-current-state

       *                               *
       │ * v1.0.3                      │
       ├─┘                             *─ v1.0.3
       *                               *
       │                               │
       │ * v1.0.2                      │
       ├─┘              vs             *─ v1.0.2
       *                               *
       │                               │
       *                               *
       │ * v1.0.1                      │
       ├─┘                             *─ v1.0.2
       │                               │
       *                               *

Notice how the grapevine approach adds a separate commit that is not part of the main branch that contains the version of the code that has placeholders replaced with their current values.

Describe the Feature Request

Documentation for lookatme should be rendered using lookatme's tutorial. I'm thinking something like render each slide with a set width/height, convert the slide's canvas markup to html, add a table of contents from the slide titles.