| blob | 14287ce5342b0d81d6aeee483c14043e26aeba8d |
1 ;;; align --- align text to a specific column, by regexp
3 ;; Copyright (C) 1999, 2000 Free Sofware Foundation
5 ;; Author: John Wiegley <johnw@gnu.org>
6 ;; Keywords: convenience languages lisp
7 ;; X-URL: http://www.emacs.org/~johnw/emacs.html
9 ;; This file is part of GNU Emacs.
11 ;; GNU Emacs is free software; you can redistribute it and/or modify
12 ;; it under the terms of the GNU General Public License as published by
13 ;; the Free Software Foundation; either version 2, or (at your option)
14 ;; any later version.
16 ;; GNU Emacs is distributed in the hope that it will be useful,
17 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
18 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
19 ;; GNU General Public License for more details.
21 ;; You should have received a copy of the GNU General Public License
22 ;; along with GNU Emacs; see the file COPYING. If not, write to the
23 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
24 ;; Boston, MA 02111-1307, USA.
26 ;;; Commentary:
28 ;; This mode allows you to align regions in a context-sensitive fashion.
29 ;; The classic use is to align assignments:
30 ;;
31 ;; int a = 1;
32 ;; short foo = 2;
33 ;; double blah = 4;
34 ;;
35 ;; becomes
36 ;;
37 ;; int a = 1;
38 ;; short foo = 2;
39 ;; double blah = 4;
41 ;;; Usage:
43 ;; There are several variables which define how certain "categories"
44 ;; of syntax are to be treated. These variables go by the name
45 ;; `align-CATEGORY-modes'. For example, "c++" is such a category.
46 ;; There are several rules which apply to c++, but since several other
47 ;; languages have a syntax similar to c++ (e.g., c, java, etc), these
48 ;; modes are treated as belonging to the same category.
49 ;;
50 ;; If you want to add a new mode under a certain category, just
51 ;; customize that list, or add the new mode manually. For example, to
52 ;; make jde-mode a c++ category mode, use this code in your .emacs
53 ;; file:
54 ;;
55 ;; (setq align-c++-modes (cons 'jde-mode align-c++-modes))
57 ;; In some programming modes, it's useful to have the aligner run only
58 ;; after indentation is performed. To achieve this, customize or set
59 ;; the variable `align-indent-before-aligning' to t.
61 ;;; Module Authors:
63 ;; In order to incorporate align's functionality into your own
64 ;; modules, there are only a few steps you have to follow.
66 ;; 1. Require or load in the align.el library.
67 ;;
68 ;; 2. Define your alignment and exclusion rules lists, either
69 ;; customizable or not.
70 ;;
71 ;; 3. In your mode function, set the variables
72 ;; `align-mode-rules-list' and `align-mode-exclude-rules-list'
73 ;; to your own rules lists.
75 ;; If there is any need to add your mode name to one of the
76 ;; align-?-modes variables (for example, `align-dq-string-modes'), use
77 ;; `add-to-list', or some similar function which checks first to see
78 ;; if the value is already there. Since the user may customize that
79 ;; mode list, and then write your mode name into their .emacs file,
80 ;; causing the symbol already to be present the next time they load
81 ;; your package.
83 ;; Example:
84 ;;
85 ;; (require 'align)
86 ;;
87 ;; (defcustom my-align-rules-list
88 ;; '((my-rule
89 ;; (regexp . "Sample")))
90 ;; :type align-rules-list-type
91 ;; :group 'my-package)
92 ;;
93 ;; (put 'my-align-rules-list 'risky-local-variable t)
94 ;;
95 ;; (add-to-list 'align-dq-string-modes 'my-package-mode)
96 ;; (add-to-list 'align-open-comment-modes 'my-package-mode)
97 ;;
98 ;; (defun my-mode ()
99 ;; ...
100 ;; (setq align-mode-rules-list my-align-rules-list))
101 ;;
102 ;; Note that if you need to install your own exclusion rules, then you
103 ;; will also need to reproduce any double-quoted string, or open
104 ;; comment exclusion rules that are defined in the standard
105 ;; `align-exclude-rules-list'. At the moment there is no convenient
106 ;; way to mix both mode-local and global rules lists.
108 ;;; History:
110 ;; Version 1.0 was created in the earlier part of 1996, using a very
111 ;; simple algorithm that understand only basic regular expressions.
112 ;; Parts of the code were broken up and included in vhdl-mode.el
113 ;; around this time. After several comments from users, and a need to
114 ;; find a more robust, performant algorithm, 2.0 was born in late
115 ;; 1998. Many different approaches were taken (mostly due to the
116 ;; complexity of TeX tables), but finally a scheme was discovered
117 ;; which worked fairly well for most common usage cases. Development
118 ;; beyond version 2.8 is not planned, except for problems that users
119 ;; might encounter.
121 ;;; Code:
124 "Align text to a specific column, by regexp."
127 ;;; User Variables:
130 "*Hook that gets run after the aligner has been loaded."
135 "*If non-nil, indent the marked region before aligning it."
140 "*An integer that represents the default amount of padding to use.
141 If `align-to-tab-stop' is non-nil, this will represent the number of
142 tab stops to use for alignment, rather than the number of spaces.
143 Each alignment rule can optionally override both this variable. See
144 `align-mode-alist'."
149 "*If non-nil, alignments will always fall on a tab boundary.
150 It may also be a symbol, whose value will be taken."
155 "*If non-nil, used as a heuristic by `align-current'.
156 Since each alignment rule can possibly have its own set of alignment
157 sections (whenever `align-region-separate' is non-nil, and not a
158 string), this heuristic is used to determine how far before and after
159 point we should search in looking for a region separator. Larger
160 values can mean slower perform in large files, although smaller values
161 may cause unexpected behavior at times."
166 "*The face to highlight with if changes are necessary."
171 "*The face to highlight with if no changes are necessary."
177 If nil,then no messages will ever be printed to the minibuffer."
182 "*A list of modes whose syntax resembles C/C++."
187 "*A list of modes where perl syntax is to be seen."
193 "*A list of modes whose syntax resembles Lisp."
199 "*A list of modes whose syntax resembles TeX (and family)."
204 "*A list of modes whose content is plain text."
209 align-c++-modes
210 align-perl-modes)
211 "*A list of modes where double quoted strings should be excluded."
216 "*A list of modes where single quoted strings should be excluded."
221 align-c++-modes
222 align-perl-modes
224 "*A list of modes with a single-line comment syntax.
225 These are comments as in Lisp, which have a beginning but, end with
226 the line (i.e., `comment-end' is an empty string)."
231 "*Select the method by which alignment sections will be separated.
232 If this is a symbol, that symbol's value will be used.
234 For the sake of clarification, consider the following example, which
235 will be referred to in the descriptions below.
237 int alpha = 1; /* one */
238 double beta = 2.0;
239 long gamma; /* ten */
241 unsigned int delta = 1; /* one */
242 long double epsilon = 3.0;
243 long long omega; /* ten */
245 The possible settings for `align-region-separate' are:
247 `entire' The entire region being aligned will be considered as a
248 single alignment section. Assuming that comments were not
249 being aligned to a particular column, the example would
250 become:
252 int alpha = 1; /* one */
253 double beta = 2.0;
254 long gamma; /* ten */
256 unsigned int delta = 1; /* one */
257 long double epsilon;
258 long long chi = 10; /* ten */
260 `group' Each contiguous set of lines where a specific alignment
261 occurs is considered a section for that alignment rule.
262 Note that each rule will may have any entirely different
263 set of section divisions than another.
265 int alpha = 1; /* one */
266 double beta = 2.0;
267 long gamma; /* ten */
269 unsigned int delta = 1; /* one */
270 long double epsilon;
271 long long chi = 10; /* ten */
273 `largest' When contiguous rule sets overlap, the largest section
274 described will be taken as the alignment section for each
275 rule touched by that section.
277 int alpha = 1; /* one */
278 double beta = 2.0;
279 long gamma; /* ten */
281 unsigned int delta = 1; /* one */
282 long double epsilon;
283 long long chi = 10; /* ten */
285 NOTE: This option is not supported yet, due to algorithmic
286 issues which haven't been satisfactorily resolved. There
287 are ways to do it, but they're both ugly and resource
288 consumptive.
290 regexp A regular expression string which defines the section
291 divider. If the mode you're in has a consistent divider
292 between sections, the behavior will be very similar to
293 `largest', and faster. But if the mode does not use clear
294 separators (for example, if you collapse your braces onto
295 the preceding statement in C or perl), `largest' is
296 probably the better alternative.
298 function A function that will be passed the beginning and ending
299 locations of the region in which to look for the section
300 separator. At the very beginning of the attempt to align,
301 both of these parameters will be nil, in which case the
302 function should return non-nil if it wants each rule to
303 define its own section, or nil if it wants the largest
304 section found to be used as the common section for all rules
305 that occur there.
307 list A list of markers within the buffer that represent where
308 the section dividers lie. Be certain to use markers! For
309 when the aligning begins, the ensuing contract/expanding of
310 whitespace will throw off any non-marker positions.
312 This method is intended for use in Lisp programs, and not
313 by the user."
317 ; (const largest)
338 repeat)
349 case-fold)
353 tab-stop)
357 valid)
361 run-if)
366 integer symbol))
372 justify)
374 ;; make sure this stays up-to-date with any changes
375 ;; in `align-region-separate'
378 separate)
382 ; (const largest)
383 regexp function)))))))
462 ; (valid
463 ; . ,(function
464 ; (lambda ()
465 ; (memq (caar (c-guess-basic-syntax))
466 ; '(brace-list-intro
467 ; brace-list-entry
468 ; brace-entry-open))))))
470 ;; With a prefix argument, comma delimiter will be aligned. Since
471 ;; perl-mode doesn't give us enough syntactic information (and we
472 ;; don't do our own parsing yet), this rule is too destructive to
473 ;; run normally.
494 ; (valid
495 ; . ,(function
496 ; (lambda ()
497 ; (memq (caar (c-guess-basic-syntax))
498 ; '(cpp-macro cpp-macro-cont))))))
541 ;; With a numeric prefix argument, or C-u, space delimited text
542 ;; tables will be aligned.
553 ;; With a negative prefix argument, lists of dollar figures will
554 ;; be aligned.
562 "*An list describing all of the available alignment rules.
563 The format is:
565 ((TITLE
566 (ATTRIBUTE . VALUE) ...)
567 ...)
569 The following attributes are meaningful:
571 `regexp' This required attribute must be either a string describing
572 a regular expression, or a function (described below).
573 For every line within the section that this regular
574 expression matches, the given rule will be applied to that
575 line. The exclusion rules denote which part(s) of the
576 line should not be modified; the alignment rules cause the
577 identified whitespace group to be contracted/expanded such
579 immediately following the identified parenthesis group),
580 occurs in the same column for every line within the
581 alignment section (see `align-region-separate' for a
582 description of how the region is broken up into alignment
583 sections).
585 The `regexp' attribute describes how the text should be
586 treated. Within this regexp, there must be at least one
587 group of characters (typically whitespace) identified by
588 the special opening and closing parens used in regexp
590 the syntax of regular expressions for more info).
592 If `regexp' is a function, it will be called as a
593 replacement for `re-search-forward'. This means that it
594 should return nil if nothing is found to match the rule,
595 or it should set the match data appropriately, move point
596 to the end of the match, and return the value of point.
598 `group' For exclusion rules, the group identifies the range of
599 characters that should be ignored. For alignment rules,
600 these are the characters that will be deleted/expanded for
602 always the first character immediately following this
603 parenthesis group. This attribute may also be a list of
604 integer, in which case multiple alignment characters will
605 be aligned, with the list of integer identifying the
606 whitespace groups which precede them. The default for
607 this attribute is 1.
609 `modes' The `modes' attribute, if set, should name a list of
610 major modes -- or evaluate to such a value -- in which the
611 rule is valid. If not set, the rule will apply to all
612 modes.
614 `case-fold' If `regexp' is an ordinary regular expression string
615 containing alphabetic character, sometimes you may want
616 the search to proceed case-insensitively (for languages
617 that ignore case, such as pascal for example). In that
618 case, set `case-fold' to nil, and the regular expression
619 search will ignore case. If `regexp' is set to a
620 function, that function must handle the job of ignoring
621 case by itself.
623 `tab-stop' If the `tab-stop' attribute is set, and non-nil, the
624 alignment character will always fall on a tab stop
625 (whether it uses tabs to get there or not depends on the
626 value of `indent-tabs-mode'). If the `tab-stop' attribute
627 is set to nil, tab stops will never be used. Otherwise,
628 the value of `align-to-tab-stop' determines whether or not
629 to align to a tab stop. The `tab-stop' attribute may also
630 be a list of t or nil values, corresponding to the number
631 of parenthesis groups specified by the `group' attribute.
633 `repeat' If the `repeat' attribute is present, and non-nil, the
634 rule will be applied to the line continuously until no
635 further matches are found.
637 `valid' If the `valid' attribute is set, it will be used to
638 determine whether the rule should be invoked. This form
639 is evaluated after the regular expression match has been
640 performed, so that it is possible to use the results of
641 that match to determine whether the alignment should be
642 performed. The buffer should not be modified during the
643 evaluation of this form.
645 `run-if' Like `valid', the `run-if' attribute tests whether the
646 rule should be run at all -- even before any searches are
647 done to determine if the rule applies to the alignment
648 region. This can save time, since `run-if' will only be
649 run once for each rule. If it returns nil, the rule will
650 not be attempted.
652 `column' For alignment rules, if the `column' attribute is set --
653 which must be an integer, or a symbol whose value is an
654 integer -- it will be used as the column in which to align
655 the alignment character. If the text on a particular line
656 happens to overrun that column, a single space character,
657 or tab stop (see `align-to-tab-stop') will be added
658 between the last text character and the alignment
659 character.
661 `spacing' Alignment rules may also override the amount of spacing
662 that would normally be used by providing a `spacing'
663 attribute. This must be an integer, or a list of integers
664 corresponding to the number of parenthesis groups matched
665 by the `group' attribute. If a list of value is used, and
666 any of those values is nil, `align-default-spacing' will
667 be used for that subgroup. See `align-default-spacing'
668 for more details on spacing, tab stops, and how to
669 indicate how much spacing should be used. If TAB-STOP is
670 present, it will override the value of `align-to-tab-stop'
671 for that rule.
673 `justify' It is possible with `regexp' and `group' to identify a
674 character group that contains more than just whitespace
675 characters. By default, any non-whitespace characters in
676 that group will also be deleted while aligning the
677 alignment character. However, if the `justify' attribute
678 is set to a non-nil value, only the initial whitespace
679 characters within that group will be deleted. This has
680 the effect of right-justifying the characters that remain,
681 and can be used for outdenting or just plain old right-
682 justification.
684 `separate' Each rule can define its own section separator, which
686 within the region to be aligned. Setting the `separate'
687 attribute overrides the value of `align-region-separate'
688 (see the documentation of that variable for possible
689 values), and any separation argument passed to `align'."
690 :type align-rules-list-type
709 repeat)
720 case-fold)
760 "*An list describing text that should be excluded from alignment.
761 See the documentation for `align-rules-list' for more info."
762 :type align-exclude-rules-list-type
767 ;;; Internal Variables:
770 "Alignment rules specific to the current major mode.
776 "Alignment exclusion rules specific to the current major mode.
784 ;; Sample extension rule set, for vhdl-mode. This should properly be
785 ;; in vhdl-mode.el itself.
818 "*Alignment rules for `vhdl-mode'. See `align-rules-list' for more info."
819 :type align-rules-list-type
825 "Setup the `align-mode-rules-list' variable for `vhdl-mode'."
833 ;;; User Functions:
835 ;;;###autoload
837 "Attempt to align a region based on a set of alignment rules.
838 BEG and END mark the region. If BEG and END are specifically set to
839 nil (this can only be done programmatically), the beginning and end of
840 the current alignment section will be calculated based on the location
841 of point, and the value of `align-region-separate' (or possibly each
842 rule's `separate' attribute).
844 If SEPARATE is non-nil, it overrides the value of
845 `align-region-separate' for all rules, except those that have their
846 `separate' attribute set.
848 RULES and EXCLUDE-RULES, if either is non-nil, will replace the
849 default rule lists defined in `align-rules-list' and
850 `align-exclude-rules-list'. See `align-rules-list' for more details
851 on the format of these lists."
857 align-region-separate)
865 align-exclude-rules-list))
870 align-mode-exclude-rules-list
871 align-exclude-rules-list) nil
872 separator
882 align-exclude-rules-list)))))))
884 ;;;###autoload
886 "Align the current region using an ad-hoc rule read from the minibuffer.
887 BEG and END mark the limits of the region. This function will prompt
888 for the REGEXP to align with. If no prefix arg was specified, you
889 only need to supply the characters to be lined up and any preceding
890 whitespace is replaced. If a prefix arg was specified, the full
891 regexp with parenthesized whitespace should be supplied; it will also
892 prompt for which parenthesis GROUP within REGEXP to modify, the amount
893 of SPACING to use, and whether or not to REPEAT the rule throughout
894 the line. See `align-rules-list' for more information about these
895 options.
897 For example, let's say you had a list of phone numbers, and wanted to
898 align them so that the opening parentheses would line up:
900 Fred (123) 456-7890
901 Alice (123) 456-7890
902 Mary-Anne (123) 456-7890
903 Joe (123) 456-7890
905 There is no predefined rule to handle this, but you could easily do it
907 region, call `align-regexp' and type in that regular expression."
937 ;;;###autoload
939 "Align the selected region as if it were one alignment section.
940 BEG and END mark the extent of the region. If RULES or EXCLUDE-RULES
941 is set to a list of rules (see `align-rules-list'), it can be used to
942 override the default alignment rules that would have been used to
943 align that section."
947 ;;;###autoload
949 "Call `align' on the current alignment section.
950 This function assumes you want to align only the current section, and
951 so saves you from having to specify the region. If RULES or
952 EXCLUDE-RULES is set to a list of rules (see `align-rules-list'), it
953 can be used to override the default alignment rules that would have
954 been used to align that section."
958 ;;;###autoload
960 "Highlight the whitespace which a given rule would have modified.
961 BEG and END mark the extent of the region. TITLE identifies the rule
962 that should be highlighted. If RULES or EXCLUDE-RULES is set to a
963 list of rules (see `align-rules-list'), it can be used to override the
964 default alignment rules that would have been used to identify the text
965 to be colored."
970 "Title of rule to highlight: "
980 align-exclude-rules-list)))
981 face)
984 beg end 'entire
987 align-exclude-rules-list)
990 align-exclude-rules-list))
996 align-highlight-nochange-face))
1007 ;;;###autoload
1009 "Remove any highlighting that was added by `align-highlight-rule'."
1016 ;;; Internal Functions:
1019 "Match REGEXP in TeX mode, counting backslashes appropriately.
1020 END denotes the end of the region to be searched, while REVERSE, if
1021 non-nil, indicates that the search should proceed backward from the
1022 current position."
1038 result))
1041 "Is there a section divider between BEG and END?
1042 SEPARATOR specifies how to look for the section divider. See the
1043 documentation for `align-region-separate' for more details."
1046 nil)
1067 yes))))
1070 "Adjust COLUMN according to the given RULE.
1071 SPACING specifies how much spacing to use.
1072 TAB-STOP specifies whether SPACING refers to tab-stop boundaries."
1076 column
1084 stops nil)
1086 column)))
1089 "Given a position in the buffer, state what column it's in.
1090 POS is the position whose column will be taken. Note that this
1091 function will change the location of point."
1096 "Align the regions specified in REGIONS, a list of cons cells.
1097 PROPS describes formatting features specific to the given regions.
1098 RULE specifies exactly how to perform the alignments.
1099 If FUNC is specified, it will be called with each region that would
1100 have been aligned, rather than modifying the text."
1108 "Given a list of AREAS and formatting PROPS, align according to RULE.
1109 AREAS should be a list of cons cells containing beginning and ending
1110 markers. This function sweeps through all of the beginning markers,
1111 finds out which one starts in the furthermost column, and then deletes
1112 and inserts text such that all of the ending markers occur in the same
1113 column.
1115 If FUNC is non-nil, it will be called for each text region that would
1116 have been aligned. No changes will be made to the buffer."
1120 column))
1124 ecol change look)
1126 ;; Determine the alignment column.
1151 ;; Make all ending positions to occur in the goal column. Since
1152 ;; the whitespace to be modified was already deleted by
1153 ;; `align-region', all we have to do here is indent.
1178 ;; This code works around an oddity in the
1179 ;; FORCE argument of `move-to-column', which
1180 ;; tends to screw up markers if there is any
1181 ;; tabbing.
1203 "Align a region based on a given set of alignment rules.
1204 BEG and END specify the region to be aligned. Either may be nil, in
1205 which case the range will stop at the nearest section division (see
1206 `align-region-separate', and `align-region-heuristic' for more
1207 information').
1209 The region will be divided into separate alignment sections based on
1210 the value of SEPARATE.
1212 RULES and EXCLUDE-RULES are a pair of lists describing how to align
1213 the region, and which text areas within it should be excluded from
1214 alignment. See the `align-rules-list' for more information on the
1215 required format of these two lists.
1217 If FUNC is specified, no text will be modified. What `align-region'
1218 will do with the rules is to search for the alignment areas, as it
1219 regularly would, taking account for exclusions, and then call FUNC,
1220 first with the beginning and ending of the region to be aligned
1221 according to that rule (this can be different for each rule, if BEG
1222 and END were nil), and then with the beginning and ending of each
1223 text region that the rule would have applied to.
1225 The signature of FUNC should thus be:
1227 (defun my-align-function (beg end mode)
1229 Otherwise BEG to END will be a region of text that matches the rule's
1231 (unless (and mode (listp mode))
1234 This feature (of passing a FUNC) is used internally to locate the
1235 position of exclusion areas, but could also be used for any other
1236 purpose where you might want to know where the regions that the
1237 aligner would have dealt with are."
1251 ;; unless the `run-if' form tells us not to, look for the
1252 ;; rule..
1263 group group-c
1264 spacing spacing-c
1265 tab-stop tab-stop-c
1266 repeat repeat-c
1267 valid valid-c
1268 pos-list first
1269 regions index
1270 last-point b e
1271 save-match-data
1272 exclude-p
1273 align-props)
1275 ;; if beg and end were not given, figure out what the
1276 ;; current alignment region should be. Depending on the
1277 ;; value of `align-region-separate' it's possible for
1278 ;; each rule to have its own definition of what that
1279 ;; current alignment section is.
1295 align-region-heuristic))))
1299 terminus t))))
1302 here nil)
1314 align-region-heuristic))))
1320 here nil)
1329 ;; If we have a region to align, and `func' is set and
1330 ;; reports back that the region is ok, then align it.
1335 ;; determine first of all where the exclusions
1336 ;; lie in this region
1338 ;; guard against a problem with recursion and
1339 ;; dynamic binding vs. lexical binding, since
1340 ;; the call to `align-region' below will
1341 ;; re-enter this function, and rebind
1342 ;; `exclude-areas'
1345 nil)
1347 beg end 'entire
1348 exclude-rules nil
1360 ;; set `case-fold-search' according to the
1361 ;; (optional) `case-fold' property
1365 ;; while we can find the rule in the alignment
1366 ;; region..
1371 end-mark t)))
1373 ;; give the user some indication of where we
1374 ;; are, if it's a very large region being
1375 ;; aligned
1378 "Aligning `%s' [rule %d of %d] (%d%%)..."
1380 rule-index rule-count
1384 ;; if the search ended us on the beginning of
1385 ;; the next line, move back to the end of the
1386 ;; previous line.
1390 ;; lookup the `group' attribute the first time
1391 ;; that we need it
1401 spacing-c t))
1410 align-to-tab-stop)))
1411 tab-stop-c t))
1413 ;; test whether we have found a match on the same
1414 ;; line as a previous match
1421 ;; lookup the `repeat' attribute the first time
1424 repeat-c t))
1426 ;; lookup the `valid' attribute the first time
1429 valid-c t))
1431 ;; remember the beginning position of this rule
1432 ;; match, and save the match-data, since either
1433 ;; the `valid' form, or the code that searches for
1434 ;; section separation, might alter it
1438 ;; unless the `valid' attribute is set, and tells
1439 ;; us that the rule is not valid at this point in
1440 ;; the code..
1443 ;; look to see if this match begins a new
1444 ;; section. If so, we should align what we've
1445 ;; collected so far, and then begin collecting
1446 ;; anew for the next alignment section
1449 thissep))
1452 rule func)
1454 regions nil
1455 align-props nil))
1458 ;; restore the match data
1461 ;; check whether the region to be aligned
1462 ;; straddles an exclusion area
1471 excls nil)
1474 ;; go through the list of parenthesis groups
1475 ;; matching whitespace text to be
1476 ;; contracted/expanded (or possibly
1477 ;; justified, if the `justify' attribute was
1478 ;; set)
1483 ;; we have to use markers, since
1484 ;; `align-areas' may modify the buffer
1489 ;; record this text region for alignment
1495 spacing)
1498 tab-stop))))
1512 ;; if any further rule matches are
1513 ;; found before `eol', then they are
1514 ;; on the same line as this one; this
1515 ;; can only happen if the `repeat'
1516 ;; attribute is non-nil
1523 ;; if `repeat' has not been set, move to
1524 ;; the next line; don't bother searching
1525 ;; anymore on this one
1529 ;; when they are no more matches for this rule,
1530 ;; align whatever was left over
1541 ;; Provide:
1547 ;;; align.el ends here