That's a nice trick Eric. I didn't now about it, it formats well in ExDoc, with the exception that ">" is not hightlighted and it is selectable., but I can create a feature request for MakeUp.
So far the only way I knew to disable it is not to use `iex>` altogether. Thank you On Fri, 10 Dec 2021 05:07:49 -0800 (PST) Eric Meadows-Jönsson <eric.meadows.jons...@gmail.com> wrote: > I don't think this is needed since if you don't want to use doctests > you don't have to use the doctest syntax. > > For example, instead of: > > iex> 1 + 1 > 2 > > you can do: > > > 1 + 1 > 2 > > On Thursday, December 9, 2021 at 3:44:55 PM UTC+1 eksperimental wrote: > > > Hi list, > > documenting functions made me realize the need to be able to disable > > doctests per documentation entry. So I would like to propose the > > addition of support for: > > > > `@doc doctest: false` > > `@moduledoc doctest: false` > > `@typedoc doctest: false` > > > > (In the same fashion as we declare guards with `@doc guard: true`) > > > > To indicate and to disable doctests for the given documentation > > entry within the module being defined. > > > > While currenty this can be done from the test file, passing the > > :exclude or :only options to `doctest`, I find it inconvenient to > > define what gets doctested in another file and have to switch back > > and forth to make sure of this. > > I would like to focus on my module and know whether I can write > > invalid doc tests or not. > > > > > > Please let me know what you thing about this, > > - Eksperimental > > > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to elixir-lang-core+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/61b358c1.1c69fb81.a4117.8339SMTPIN_ADDED_MISSING%40gmr-mx.google.com.
