From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Cc: Dmitry Gutov <dgutov@yandex.ru>
Subject: Re: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls
Date: Wed, 29 Nov 2017 20:53:47 -0500 [thread overview]
Message-ID: <jwvwp28edp6.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <20171129233238.504B5204F1@vcs0.savannah.gnu.org> (Dmitry Gutov's message of "Wed, 29 Nov 2017 18:32:38 -0500 (EST)")
> Replace prog-widen with consolidating widen calls
So, IIUC the idea is that the multi-major-mode framework will *have* to
use narrowing to indicate to the sub-modes the boundaries of the current
chunk, right?
Stefan
> ---
> doc/lispref/text.texi | 45 +++++----------------------------------------
> etc/NEWS | 8 ++++----
> lisp/indent.el | 12 +++++++++---
> lisp/progmodes/prog-mode.el | 28 ++--------------------------
> lisp/progmodes/python.el | 34 ++++++++--------------------------
> lisp/progmodes/ruby-mode.el | 1 -
> lisp/vc/add-log.el | 4 +++-
> 7 files changed, 31 insertions(+), 101 deletions(-)
> diff --git a/doc/lispref/text.texi b/doc/lispref/text.texi
> index 1e19f75..5a63e5b 100644
> --- a/doc/lispref/text.texi
> +++ b/doc/lispref/text.texi
> @@ -2407,42 +2407,17 @@ such multi-mode indentation.
> This variable, when non-@code{nil}, holds the indentation context for
> the sub-mode's indentation engine provided by the superior major mode.
> The value should be a list of the form @code{(@var{first-column}
> -@w{(@var{start} . @var{end})} @code{prev-chunk})}. The members of the
> -list have the following meaning:
> +@code{...rest})}. The members of the list have the following meaning:
> @table @var
> @item first-column
> The column to be used for top-level constructs. This replaces the
> default value of the top-level column used by the sub-mode, usually
> zero.
> -@item start
> -@itemx end
> -The region of the code chunk to be indented by the sub-mode. The
> -value of @var{end} can be @code{nil}, which stands for the value of
> -@code{point-max}.
> -@item prev-chunk
> -If this is non-@code{nil}, it should provide the sub-mode's
> -indentation engine with a virtual context of the code chunk. Valid
> -values include:
> -
> -@itemize @minus
> -@item
> -A string whose contents is the text the sub-mode's indentation engine
> -should consider to precede the code chunk. The sub-mode's indentation
> -engine can add text properties to that string, to be reused in
> -repeated calls with the same string, thus using it as a cache. An
> -example where this is useful is code chunks that need to be indented
> -as function bodies, but lack the function's preamble---the string
> -could then include that missing preamble.
> -@item
> -A function. It is expected to be called with the start position of
> -the current chunk, and should return a cons cell
> -@w{@code{(@var{prev-start} . @var{prev-end})}} that specifies the
> -region of the previous code chunk, or @code{nil} if there is no previous
> -chunk. This is useful in literate-programming sources, where code is
> -split into chunks, and correct indentation needs to access previous
> -chunks.
> -@end itemize
> +@item rest
> +Reserved for future use. The intent is to provide the sub-mode's
> +indentation engine with a virtual context of the code chunk. Working
> +patches that use this in a significant fashion are welcome.
> @end table
> @end defvar
> @@ -2457,16 +2432,6 @@ function's value is the column number to use for top-level constructs.
> When no superior mode is in effect, this function returns zero.
> @end defun
> -@defun prog-widen
> -Call this function instead of @code{widen} to remove any restrictions
> -imposed by the mode's indentation engine and restore the restrictions
> -recorded in @code{prog-indentation-context}. This prevents the
> -indentation engine of a sub-mode from inadvertently operating on text
> -outside of the chunk it was supposed to indent, and preserves the
> -restriction imposed by the superior mode. When no superior mode is in
> -effect, this function just calls @code{widen}.
> -@end defun
> -
> @node Region Indent
> @subsection Indenting an Entire Region
> diff --git a/etc/NEWS b/etc/NEWS
> index 4ccf468..6e1561d 100644
> --- a/etc/NEWS
> +++ b/etc/NEWS
> @@ -1108,10 +1108,10 @@ programming languages in the same buffer, like literate programming
> environments or ANTLR programs with embedded Python code.
> A major mode can provide indentation context for a sub-mode through
> -the 'prog-indentation-context' variable. To support this, modes that
> -provide indentation should use 'prog-widen' instead of 'widen' and
> -'prog-first-column' instead of a literal zero. See the node
> -"(elisp) Mode-Specific Indent" in the ELisp manual for more details.
> +the 'prog-indentation-context' variable. To support this, modes
> +should use 'prog-first-column' instead of a literal zero and never
> +call 'widen' in their indentation functions. See the node "(elisp)
> +Mode-Specific Indent" in the ELisp manual for more details.
> ** ERC
> diff --git a/lisp/indent.el b/lisp/indent.el
> index d5ba0bd..ccf0e99 100644
> --- a/lisp/indent.el
> +++ b/lisp/indent.el
> @@ -69,6 +69,8 @@ variable is `indent-relative' or `indent-relative-maybe', handle
> it specially (since those functions are used for tabbing); in
> that case, indent by aligning to the previous non-blank line."
> (interactive)
> + (save-restriction
> + (widen)
> (syntax-propertize (line-end-position))
> (if (memq indent-line-function
> '(indent-relative indent-relative-maybe))
> @@ -84,7 +86,7 @@ that case, indent by aligning to the previous non-blank line."
> (indent-line-to column)
> (save-excursion (indent-line-to column))))
> ;; The normal case.
> - (funcall indent-line-function)))
> + (funcall indent-line-function))))
> (defun indent--default-inside-comment ()
> (unless (or (> (current-column) (current-indentation))
> @@ -144,7 +146,9 @@ prefix argument is ignored."
> (indent--default-inside-comment)
> (when (or (<= (current-column) (current-indentation))
> (not (eq tab-always-indent 'complete)))
> - (funcall (default-value 'indent-line-function))))
> + (save-restriction
> + (widen)
> + (funcall (default-value 'indent-line-function)))))
> (cond
> ;; If the text was already indented right, try completion.
> @@ -538,7 +542,9 @@ column to indent to; if it is nil, use one of the three methods above."
> (forward-line 1)))))
> ;; Use indent-region-function is available.
> (indent-region-function
> - (funcall indent-region-function start end))
> + (save-restriction
> + (widen)
> + (funcall indent-region-function start end)))
> ;; Else, use a default implementation that calls indent-line-function on
> ;; each line.
> (t (indent-region-line-by-line start end)))
> diff --git a/lisp/progmodes/prog-mode.el b/lisp/progmodes/prog-mode.el
> index f727e45..b36d242 100644
> --- a/lisp/progmodes/prog-mode.el
> +++ b/lisp/progmodes/prog-mode.el
> @@ -64,37 +64,13 @@ mode, it should bind this variable to non-nil around the call.
> The non-nil value should be a list of the form:
> - (FIRST-COLUMN (START . END) PREVIOUS-CHUNKS)
> + (FIRST-COLUMN ...REST)
> FIRST-COLUMN is the column the indentation engine of the sub-mode
> should use for top-level language constructs inside the code
> chunk (instead of 0).
> -START and END specify the region of the code chunk. END can be
> -nil, which stands for the value of `point-max'. The function
> -`prog-widen' uses this to restore restrictions imposed by the
> -sub-mode's indentation engine.
> -
> -PREVIOUS-CHUNKS, if non-nil, provides the indentation engine of
> -the sub-mode with the virtual context of the code chunk. Valid
> -values are:
> -
> - - A string containing text which the indentation engine can
> - consider as standing in front of the code chunk. To cache the
> - string's calculated syntactic information for repeated calls
> - with the same string, the sub-mode can add text-properties to
> - the string.
> -
> - A typical use case is for grammars with code chunks which are
> - to be indented like function bodies -- the string would contain
> - the corresponding function preamble.
> -
> - - A function, to be called with the start position of the current
> - chunk. It should return either the region of the previous chunk
> - as (PREV-START . PREV-END), or nil if there is no previous chunk.
> -
> - A typical use case are literate programming sources -- the
> - function would successively return the previous code chunks.")
> +REST is currently unused, but can be defined in future versions.")
> (defun prog-indent-sexp (&optional defun)
> "Indent the expression after point.
> diff --git a/lisp/progmodes/python.el b/lisp/progmodes/python.el
> index d4226e5..104889a 100644
> --- a/lisp/progmodes/python.el
> +++ b/lisp/progmodes/python.el
> @@ -287,10 +287,6 @@
> ;;; 24.x Compat
> \f
> -(unless (fboundp 'prog-widen)
> - (defun prog-widen ()
> - (widen)))
> -
> (unless (fboundp 'prog-first-column)
> (defun prog-first-column ()
> 0))
> @@ -785,7 +781,7 @@ work on `python-indent-calculate-indentation' instead."
> (interactive)
> (save-excursion
> (save-restriction
> - (prog-widen)
> + (widen)
> (goto-char (point-min))
> (let ((block-end))
> (while (and (not block-end)
> @@ -883,8 +879,6 @@ keyword
> :at-dedenter-block-start
> - Point is on a line starting a dedenter block.
> - START is the position where the dedenter block starts."
> - (save-restriction
> - (prog-widen)
> (let ((ppss (save-excursion
> (beginning-of-line)
> (syntax-ppss))))
> @@ -1022,7 +1016,7 @@ keyword
> (looking-at (python-rx block-ender)))
> :after-block-end)
> (t :after-line))
> - (point)))))))))
> + (point))))))))
> (defun python-indent--calculate-indentation ()
> "Internal implementation of `python-indent-calculate-indentation'.
> @@ -1030,8 +1024,6 @@ May return an integer for the maximum possible indentation at
> current context or a list of integers. The latter case is only
> happening for :at-dedenter-block-start context since the
> possibilities can be narrowed to specific indentation points."
> - (save-restriction
> - (prog-widen)
> (save-excursion
> (pcase (python-indent-context)
> (`(:no-indent . ,_) (prog-first-column)) ; usually 0
> @@ -1081,7 +1073,7 @@ possibilities can be narrowed to specific indentation points."
> (`(,(or :inside-paren-newline-start-from-block) . ,start)
> ;; Add two indentation levels to make the suite stand out.
> (goto-char start)
> - (+ (current-indentation) (* python-indent-offset 2)))))))
> + (+ (current-indentation) (* python-indent-offset 2))))))
> (defun python-indent--calculate-levels (indentation)
> "Calculate levels list given INDENTATION.
> @@ -4589,8 +4581,6 @@ To this:
> Optional argument INCLUDE-TYPE indicates to include the type of the defun.
> This function can be used as the value of `add-log-current-defun-function'
> since it returns nil if point is not inside a defun."
> - (save-restriction
> - (prog-widen)
> (save-excursion
> (end-of-line 1)
> (let ((names)
> @@ -4644,7 +4634,7 @@ since it returns nil if point is not inside a defun."
> (and (= (current-indentation) 0) (throw 'exit t))))
> (and names
> (concat (and type (format "%s " type))
> - (mapconcat 'identity names ".")))))))
> + (mapconcat 'identity names "."))))))
> (defun python-info-current-symbol (&optional replace-self)
> "Return current symbol using dotty syntax.
> @@ -4788,12 +4778,10 @@ likely an invalid python file."
> "Message the first line of the block the current statement closes."
> (let ((point (python-info-dedenter-opening-block-position)))
> (when point
> - (save-restriction
> - (prog-widen)
> (message "Closes %s" (save-excursion
> (goto-char point)
> (buffer-substring
> - (point) (line-end-position))))))))
> + (point) (line-end-position)))))))
> (defun python-info-dedenter-statement-p ()
> "Return point if current statement is a dedenter.
> @@ -4809,8 +4797,6 @@ statement."
> "Return non-nil if current line ends with backslash.
> With optional argument LINE-NUMBER, check that line instead."
> (save-excursion
> - (save-restriction
> - (prog-widen)
> (when line-number
> (python-util-goto-line line-number))
> (while (and (not (eobp))
> @@ -4819,14 +4805,12 @@ With optional argument LINE-NUMBER, check that line instead."
> (not (equal (char-before (point)) ?\\)))
> (forward-line 1))
> (when (equal (char-before) ?\\)
> - (point-marker)))))
> + (point-marker))))
> (defun python-info-beginning-of-backslash (&optional line-number)
> "Return the point where the backslashed line start.
> Optional argument LINE-NUMBER forces the line number to check against."
> (save-excursion
> - (save-restriction
> - (prog-widen)
> (when line-number
> (python-util-goto-line line-number))
> (when (python-info-line-ends-backslash-p)
> @@ -4835,15 +4819,13 @@ Optional argument LINE-NUMBER forces the line number to check against."
> (python-syntax-context 'paren))
> (forward-line -1))
> (back-to-indentation)
> - (point-marker)))))
> + (point-marker))))
> (defun python-info-continuation-line-p ()
> "Check if current line is continuation of another.
> When current line is continuation of another return the point
> where the continued line ends."
> (save-excursion
> - (save-restriction
> - (prog-widen)
> (let* ((context-type (progn
> (back-to-indentation)
> (python-syntax-context-type)))
> @@ -4869,7 +4851,7 @@ where the continued line ends."
> (python-util-forward-comment -1)
> (when (and (equal (1- line-start) (line-number-at-pos))
> (python-info-line-ends-backslash-p))
> - (point-marker))))))))
> + (point-marker)))))))
> (defun python-info-block-continuation-line-p ()
> "Return non-nil if current line is a continuation of a block."
> diff --git a/lisp/progmodes/ruby-mode.el b/lisp/progmodes/ruby-mode.el
> index dc1b0f8..7c10114 100644
> --- a/lisp/progmodes/ruby-mode.el
> +++ b/lisp/progmodes/ruby-mode.el
> @@ -1364,7 +1364,6 @@ delimiter."
> "\\)\\>")))
> (eq (ruby-deep-indent-paren-p t) 'space)
> (not (bobp)))
> - (widen)
> (goto-char (or begin parse-start))
> (skip-syntax-forward " ")
> (current-column))
> diff --git a/lisp/vc/add-log.el b/lisp/vc/add-log.el
> index 392147b..9da8abc 100644
> --- a/lisp/vc/add-log.el
> +++ b/lisp/vc/add-log.el
> @@ -1133,6 +1133,8 @@ identifiers followed by `:' or `='. See variables
> Has a preference of looking backwards."
> (condition-case nil
> (save-excursion
> + (save-restriction
> + (widen)
> (if add-log-current-defun-function
> (funcall add-log-current-defun-function)
> ;; If all else fails, try heuristics
> @@ -1147,7 +1149,7 @@ Has a preference of looking backwards."
> (when (string-match "\\([^ \t\n\r\f].*[^ \t\n\r\f]\\)"
> result)
> (setq result (match-string-no-properties 1 result)))
> - result))))
> + result)))))
> (error nil)))
> (defvar change-log-get-method-definition-md)
> _______________________________________________
> Emacs-diffs mailing list
> Emacs-diffs@gnu.org
> https://lists.gnu.org/mailman/listinfo/emacs-diffs
next parent reply other threads:[~2017-11-30 1:53 UTC|newest]
Thread overview: 194+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20171129233237.27462.23351@vcs0.savannah.gnu.org>
[not found] ` <20171129233238.504B5204F1@vcs0.savannah.gnu.org>
2017-11-30 1:53 ` Stefan Monnier [this message]
2017-11-30 8:59 ` [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Dmitry Gutov
2017-11-30 10:58 ` Dmitry Gutov
2017-11-30 15:31 ` Tom Tromey
2017-11-30 21:28 ` Dmitry Gutov
2017-11-30 21:46 ` Alan Mackenzie
2017-11-30 23:03 ` [SUSPECTED SPAM] " Stefan Monnier
2017-12-01 16:07 ` Alan Mackenzie
2017-11-30 23:09 ` Dmitry Gutov
2017-12-01 15:49 ` Alan Mackenzie
2017-12-01 16:26 ` Stefan Monnier
2017-12-01 18:20 ` Alan Mackenzie
2017-12-01 18:59 ` Dmitry Gutov
2017-12-01 19:51 ` Stefan Monnier
2017-12-01 20:50 ` Dmitry Gutov
2017-12-02 2:24 ` Stefan Monnier
2017-12-02 20:01 ` Dmitry Gutov
2017-12-02 23:47 ` Stefan Monnier
2017-12-03 3:38 ` Eli Zaretskii
2017-12-03 23:43 ` Dmitry Gutov
2017-12-04 3:38 ` Eli Zaretskii
2017-12-04 11:53 ` Dmitry Gutov
2017-12-04 16:41 ` Eli Zaretskii
2017-12-04 17:45 ` Stefan Monnier
2017-12-05 0:10 ` Dmitry Gutov
2017-12-03 16:42 ` Dmitry Gutov
2017-12-03 21:23 ` Stefan Monnier
2017-12-03 23:58 ` Dmitry Gutov
2017-12-01 17:06 ` Drew Adams
2017-12-01 18:03 ` Stefan Monnier
2017-12-01 21:27 ` Vitalie Spinu
2017-12-01 21:38 ` Dmitry Gutov
2017-12-01 22:45 ` Alan Mackenzie
2017-12-02 2:53 ` Stefan Monnier
2017-12-02 14:02 ` Tom Tromey
2017-12-02 23:48 ` Richard Stallman
2017-12-01 19:13 ` Dmitry Gutov
2017-12-01 22:35 ` Alan Mackenzie
2017-12-01 23:24 ` Dmitry Gutov
2017-12-02 2:47 ` Stefan Monnier
2017-12-02 20:28 ` Alan Mackenzie
2017-12-03 0:03 ` Stefan Monnier
2017-12-03 12:18 ` Alan Mackenzie
2017-12-03 16:02 ` Dmitry Gutov
2017-12-03 3:52 ` Dmitry Gutov
2017-12-03 14:54 ` Alan Mackenzie
2017-12-03 18:40 ` Stefan Monnier
2017-12-03 22:26 ` Alan Mackenzie
2017-12-03 23:42 ` Stefan Monnier
2017-12-04 2:33 ` syntax-propertize and CC-mode (was: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls) Stefan Monnier
2017-12-03 23:53 ` [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Dmitry Gutov
2017-12-02 8:27 ` Eli Zaretskii
2017-12-02 10:50 ` Dmitry Gutov
2017-12-02 11:10 ` Eli Zaretskii
2017-12-02 16:41 ` Stefan Monnier
2017-12-02 17:13 ` Eli Zaretskii
2017-12-02 17:53 ` Stefan Monnier
2017-12-02 18:33 ` Eli Zaretskii
2017-12-02 20:18 ` Dmitry Gutov
2017-12-02 20:14 ` Dmitry Gutov
2017-12-02 20:58 ` Eli Zaretskii
2017-12-02 21:35 ` Dmitry Gutov
2017-12-03 15:28 ` Eli Zaretskii
2017-12-03 16:35 ` Dmitry Gutov
2017-12-03 17:20 ` Eli Zaretskii
2017-12-03 19:43 ` Dmitry Gutov
2017-12-04 15:52 ` Eli Zaretskii
2017-12-04 16:35 ` Stefan Monnier
2017-12-04 16:56 ` Eli Zaretskii
2017-12-04 22:57 ` Dmitry Gutov
2017-12-04 23:27 ` Dmitry Gutov
2017-12-03 18:59 ` Alan Mackenzie
2017-12-03 19:25 ` Eli Zaretskii
2017-12-03 21:20 ` Alan Mackenzie
2017-12-04 16:10 ` Eli Zaretskii
2017-12-04 16:23 ` Alan Mackenzie
2017-12-04 16:48 ` Eli Zaretskii
2017-12-03 22:01 ` Stefan Monnier
2017-12-04 0:37 ` Dmitry Gutov
2017-12-04 15:52 ` Alan Mackenzie
2017-12-04 16:46 ` Eli Zaretskii
2017-12-05 13:08 ` Dmitry Gutov
2017-12-05 19:01 ` CC Mode in MMM Mode(s). [Was: Re: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls] Alan Mackenzie
2017-12-05 23:34 ` Dmitry Gutov
2017-12-06 18:19 ` CC Mode in MMM Mode(s) Alan Mackenzie
2017-12-07 0:21 ` Dmitry Gutov
2017-12-07 19:49 ` Richard Stallman
2017-12-07 23:43 ` Dmitry Gutov
2017-12-08 21:36 ` Richard Stallman
2017-12-09 15:20 ` Dmitry Gutov
2017-12-03 21:52 ` [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls Stefan Monnier
2017-12-04 0:03 ` Dmitry Gutov
2017-12-04 2:24 ` [SUSPECTED SPAM] " Stefan Monnier
2017-12-04 10:03 ` Dmitry Gutov
2017-12-04 16:21 ` Eli Zaretskii
2017-12-04 17:12 ` Stefan Monnier
2017-12-04 17:40 ` Eli Zaretskii
2017-12-04 17:52 ` Stefan Monnier
2017-12-04 19:53 ` Eli Zaretskii
2017-12-04 20:36 ` Eli Zaretskii
2017-12-04 21:00 ` Stefan Monnier
2017-12-04 21:50 ` Dmitry Gutov
2017-12-06 18:41 ` Dmitry Gutov
2017-12-09 10:47 ` Eli Zaretskii
2017-12-09 11:05 ` Eli Zaretskii
2017-12-10 5:01 ` Stefan Monnier
2017-12-10 6:53 ` Eli Zaretskii
2017-12-10 20:08 ` Stefan Monnier
2017-12-11 14:18 ` Getting rid of prog-indentation-context Stefan Monnier
2017-12-11 16:18 ` Eli Zaretskii
2017-12-11 17:08 ` Stefan Monnier
2017-12-11 17:26 ` Stefan Monnier
2017-12-11 18:02 ` Eli Zaretskii
2017-12-11 18:53 ` Ingo Lohmar
2017-12-11 21:42 ` Dmitry Gutov
2017-12-09 17:56 ` [SUSPECTED SPAM] Re: [Emacs-diffs] scratch/widen-less a4ba846: Replace prog-widen with consolidating widen calls John Wiegley
2017-12-10 20:19 ` Dmitry Gutov
2017-12-10 20:38 ` Stefan Monnier
2017-12-10 21:41 ` Dmitry Gutov
2017-12-11 9:53 ` Tom Tromey
2017-12-11 15:31 ` Stefan Monnier
2017-12-10 20:39 ` Eli Zaretskii
2017-12-10 21:39 ` [SUSPECTED SPAM] Re: [Emacs-diffs] scratch/widen-less a4ab846: " John Wiegley
2017-12-10 21:43 ` Dmitry Gutov
2017-12-10 21:53 ` [SUSPECTED SPAM] Re: [Emacs-diffs] scratch/widen-less a4ba846: " Dmitry Gutov
2017-12-11 16:04 ` Eli Zaretskii
2017-12-11 16:25 ` Dmitry Gutov
2017-12-11 17:43 ` Eli Zaretskii
2017-12-11 18:22 ` Eli Zaretskii
2017-12-11 20:47 ` John Wiegley
2017-12-11 21:35 ` Dmitry Gutov
2017-12-11 21:43 ` John Wiegley
2017-12-14 9:32 ` Dmitry Gutov
2017-12-14 13:20 ` Dmitry Gutov
2017-12-15 11:56 ` Dmitry Gutov
2017-12-14 14:01 ` Stefan Monnier
2017-12-14 14:17 ` Dmitry Gutov
2017-12-14 14:32 ` Stefan Monnier
2017-12-14 15:17 ` Robert Weiner
2017-12-15 11:54 ` Dmitry Gutov
2017-12-15 11:54 ` Dmitry Gutov
2017-12-20 0:08 ` Dmitry Gutov
2017-12-20 2:41 ` Stefan Monnier
2017-12-20 19:13 ` John Wiegley
2017-12-20 22:30 ` Dmitry Gutov
2017-12-21 1:33 ` John Wiegley
2017-12-21 22:07 ` Dmitry Gutov
2017-12-21 23:49 ` John Wiegley
2017-12-11 17:21 ` Stefan Monnier
2017-12-11 18:04 ` Eli Zaretskii
2017-12-11 22:20 ` Stefan Monnier
2017-12-10 22:43 ` Dmitry Gutov
2017-12-10 23:30 ` Dmitry Gutov
2017-12-11 0:26 ` Dmitry Gutov
2017-12-04 21:46 ` Dmitry Gutov
2017-12-04 22:05 ` Stefan Monnier
2017-12-04 22:45 ` Dmitry Gutov
2017-12-05 6:03 ` Eli Zaretskii
2017-12-05 10:42 ` Dmitry Gutov
2017-12-05 17:49 ` Eli Zaretskii
2017-12-04 16:12 ` Eli Zaretskii
2017-12-04 16:49 ` Stefan Monnier
2017-12-04 17:28 ` Eli Zaretskii
2017-12-04 21:52 ` Dmitry Gutov
2017-12-05 5:08 ` Eli Zaretskii
2017-12-05 5:33 ` Eli Zaretskii
2017-12-05 10:55 ` Dmitry Gutov
2017-12-05 17:53 ` Eli Zaretskii
2017-12-05 18:40 ` Dmitry Gutov
2017-12-05 20:49 ` Eli Zaretskii
2017-12-05 23:16 ` Dmitry Gutov
2017-12-06 9:28 ` Eli Zaretskii
2017-12-06 13:36 ` Dmitry Gutov
2017-12-08 16:41 ` Eli Zaretskii
2017-12-09 15:17 ` Dmitry Gutov
2017-12-09 15:43 ` Eli Zaretskii
2017-12-10 19:59 ` Dmitry Gutov
2017-12-10 20:04 ` Eli Zaretskii
2017-12-05 12:55 ` Dmitry Gutov
2017-12-05 17:57 ` Eli Zaretskii
2017-12-05 18:54 ` Dmitry Gutov
2017-12-05 20:48 ` Eli Zaretskii
2017-12-05 21:08 ` Ingo Lohmar
2017-12-06 9:26 ` Eli Zaretskii
2017-12-06 13:37 ` Dmitry Gutov
2017-12-15 15:48 Wedler, Christoph
2017-12-16 15:00 ` Stefan Monnier
2017-12-16 17:34 ` Dmitry Gutov
2017-12-18 12:39 ` Wedler, Christoph
2017-12-18 14:50 ` Dmitry Gutov
2017-12-18 17:41 ` Wedler, Christoph
2017-12-19 0:27 ` Dmitry Gutov
2017-12-19 11:27 ` Wedler, Christoph
2017-12-20 0:07 ` Dmitry Gutov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvwp28edp6.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).