The chapter on Manual forms states:
The scribble/manual name can also be used as a library with require, in which case it provides all of the same bindings, but without setting the reader or setting the default rendering format to the Racket manual format.
How would a minimal example look, if it had to set the reader and the rendering format? I don't know where I'd look this up.
Related
For my debugger extension I'd like to implement a functionality from the following image where a step can ask a debugger client to show an inlined text with the result of the step.
I've read the DAP documentation thoroughly but still don't have a clue how this can be implemented or if it's even possible to implement. What request or event do I have to implement?
By the way, how is this function of debbuger client called?
With vscode v1.54, see Inline value provider
Today the Show Inline Values feature of VS Code's debugger is based on
a generic implementation in VS Code core, and doesn't provide
customizability through settings or extensibility via extensions. As a
consequence, it is not a perfect fit for all languages and sometimes
shows incorrect values because it doesn't understand the underlying
source language. For this reason, we are working on an extension API
that allows to replace the built-in implementation completely or to
replace parts of the implementation with custom code.
In this milestone we've made a first implementation of the proposed
API available.
And much more at the first link including sample code. So vscode is adding a true API for inline values rather than depending on Decorations anymore.
I have an iPhone app with interface languages in Toki Pona and Dothraki, which do not have ISO 639-3 codes. According to the ISO 639-3 standard, you can use the range qaa-qtz to represent languages for local use, which I have done (Toki Pona = qtp, Dothraki = qdt), but still get the warning from XCode "Unrecognized Locale".
It seems like I might be able to extend the main bundle class, but looking over the documentation, nothing seems to relate to adding non-ISO languages. I'm also aware of the text "If necessary, you can use a language or locale code that is not known to the NSBundle class or Core Foundation bundle functions. For example, you could create your own language designators for a language that is not yet listed in the ISO conventions or available as a language in Xcode." at the end of https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPInternational/LanguageandLocaleIDs/LanguageandLocaleIDs.html
In any case, I mostly want to get rid of this warning. Any help would be greatly appreciated!
https://forums.swift.org/t/proposal-ns-locale-identifiers-etc-should-have-custom-types/9367/8
have a look at the above link.
Check if the languages are added as Localizations
I believe I have a solution however slightly complicated one. You would need to create a setting option within the app to use those made up languages and to load them manually from a file when a user sets them. For example, let's say your app consists of one label and the user sets the option to the made-up language you would call a method to set the language and the text on that label would update accordingly. I don't know whether this makes sense to you?? Basically, if the user uses the made-up languages that would override any system localization they have. It is doable it would just take time to implement it.
We need to write a complex documentation of the API use in Typo3 6.x, but entering the code samples through RTE is very error-prone, and using just HTML element defeats the purpose of CMS.
Is there any way for nice (for editors) entering of text wrapped around code samples in various programming languages, for Typo3?
Another alternative is to use the extensions restdoc (for display) and sphinx (for generation) to make use of restructured text to write the documentation the same way the documentation of TYPO3 is created.
You could try to use Markdown content elements. I've never tried it, but there is an extension for it (markdown_content_reloaded).
I use org mode to store shortcuts for my projects. Such org files contain mostly links which I create using org-insert-link. But sometimes the simple link is not sufficient so I have to use lisp functions. This works fine but it does not look very nice.
Is there a way to create a link which would call a lisp function?
you can define new "link types" in org-mode with the function org-add-link-type to which you tell what elisp function you want to call for a particular protocol. So, in your case, you could define new protocols for "http-ie" and "load-xml-dirs" and write wrapper functions to process the parameters right. Then you would write your links as normal org links, but with a protocol prefix.
The example from the documentation page is quite straightforward I guess, let me know if it's not enough.
I'm just starting to play around with GTK+ and I wanted to stop bad habits before they happen. I see that GTK+ seems to be a little based in HTML/CSS and I was wondering if there are any reasons to avoid using tables for layout.
The widget structure should reflect the logical structure to help screen readers correctly present the window (sorry - I don't remember the name but it is standard GNOME tool).
If the logical structure is of table form then sure - use it. However if other would reflect them better - use them.
PS. Similarly to HTML where <table> should reflect the tabular data (not necessary so much in GTK+ but still) and should not be used only for layout.
GTK+ is not based on HTML nor CSS, but (lib)Glade and gtkbuilder does use an XML based file format for storing user interfaces. GTK+ is a software library and application programming interface -- it is not a scripting nor layout language.
If you want to avoid bad habits, read the GNOME Human Interface Guidelines, the Windows Human Interface Guidelines or the equivalent for the user interface you are targeting.