@@ -292,14 +292,19 @@ prefix them with =<insert>=. Example: =<insert>-= inserts a =-= and
292
292
To draw a rectangle in one shot, select a rectangular region with
293
293
=C-SPC= or =C-x SPC= and move the cursor.
294
294
295
+ You may also use =S-<arrow>= (=<arrow>= beeing any of the 4
296
+ directions) to extend the selection. The buffer grows as needed with
297
+ white spaces to accomodate the selection. Selection extension mode is
298
+ active when =shift-select-mode= is non-nil.
299
+
295
300
If needed, change the brush with any of
296
301
=- + = # <delete>=
297
302
298
303
then hit
299
304
- = r= to draw a rectangle inside the selection
300
- - = S-R= to draw a rectangle ouside the selection
305
+ - = S-R= to draw a rectangle outside the selection
301
306
- = C-r= to overwrite a rectangle inside the selection
302
- - =C-S-R= to overwrite a rectangle ouside the selection
307
+ - =C-S-R= to overwrite a rectangle outside the selection
303
308
304
309
[[file:images/draw-rectangle.png]]
305
310
@@ -556,14 +561,51 @@ Why activate =whitespace-mode= while in =uniline-mode=? Because
556
561
=uniline-mode= creates a lot of white-spaces to implement an infinite
557
562
buffer. And it is funny to look at this activity.
558
563
559
- To make them fully compatible, disable the newline visualization:
564
+ To make =uniline-mode= and =whitespace-mode= fully compatible, disable
565
+ the newline visualization:
560
566
561
567
- =M-x customize-variable whitespace-style=
562
568
- uncheck =(Mark) NEWLINEs=
563
569
564
570
This is due to a glitch in =move-to-column= when a visual property is
565
571
attached to newlines. And =uniline-mode= makes heavy use of =move-to-column=.
566
572
573
+ ** Compatibility with Org Mode
574
+ You may want to customize the shift extension mode in =Org Mode=. This
575
+ is because =Org Mode= preempts =shift-select-mode= for other useful
576
+ purposes. Just type:
577
+
578
+ #+begin_example
579
+ M-x customize-variable org-support-shift-select
580
+ #+end_example
581
+
582
+ and choose "when outside special context", which sets it to =t=.
583
+
584
+ You then get the shift-selection from =Org Mode=, not from =Uniline=. The
585
+ difference is that the =Uniline='s one handles the infinite-ness of the
586
+ buffer.
587
+
588
+ Other than that, =Uniline= is compatible with =Org Mode=
589
+
590
+ ** What about =\t= tabs?
591
+ Some files may contain tabs (the character =\t=). Those include
592
+ programming code (Python, Perl, C++, D, Rust, JavaScript and so on).
593
+
594
+ When =Uniline= draws something in the middle of a tab, it first
595
+ converts it to spaces, then proceeds as usual. This process is
596
+ invisible. So be cautious if tabs have a special meaning in the file.
597
+
598
+ One way to see what is going on, is to activate the =whitespace-mode=.
599
+
600
+ ** What about =^L= page separation?
601
+ =Uniline= does not work well with =^L= (page separation)
602
+ character. Nore with similar characters, like =^T=. When trying to
603
+ draw a line over such a character, the cursor may get stuck. This is
604
+ because those characters occupy twice the width of a normal character.
605
+
606
+ Just try to get away from =^L=, =^T= and such when drawing with
607
+ =Uniline=.
608
+
567
609
* Exotic environments
568
610
** Emacs on the Linux console
569
611
Linux consoles are the 7 non-graphic screens which can be accessed
@@ -598,13 +640,13 @@ for =C-<insertchar>=, for example with =use-package= in your
598
640
#+end_example
599
641
600
642
** Emacs on Windows
601
- On Windows the only native monospaced fonts are Lucida Console and
602
- Courier New. They are not monospaced for the Unicodes used by
643
+ On Windows the only native monospaced fonts are = Lucida Console= and
644
+ = Courier New= . They are not monospaced for the Unicodes used by
603
645
=Uniline=.
604
646
605
- Often, the Cosolas font is present on Windows. It supports quite well
647
+ Often, the =Consolas= font is present on Windows. It supports quite well
606
648
the required Unicodes to draw lines. A few glyphs produce unaligned
607
- result though. They should be avoided under Consolas: =△▶▹◇◆=
649
+ result though. They should be avoided under = Consolas= : =△▶▹◇◆=
608
650
609
651
Of course, other fonts may be installed. It is quite easy.
610
652
@@ -703,6 +745,12 @@ In this example, =C-<insert>= was choosen. You can use whatever keys combination
703
745
- =ibm-box-drawing-hydra.el=: keyboard interface to insert UNICODE
704
746
box-drawing characters one at a time
705
747
748
+ - =org-excalidraw=: integrate SVG images generated by excalidraw into
749
+ Org Mode
750
+
751
+ - =rcd-box=: create tables surrounded by box-drawing characters from
752
+ Lisp descriptions
753
+
706
754
* Author, contributors
707
755
- Thierry Banel, author
708
756
- Joost Kremers https://github.com/joostkremers found a bug in the
0 commit comments