- implementations-list - lists.ourproject.org

visual-mode and X-selections
by Hans-Peter Deifel 01 Nov '12

01 Nov '12

Hi List! I think that the interaction between visual-mode and the X11 selections is not optimal. Since I don't know if the current behavior is intentional, I haven't yet opened a bug report. The selected text in visual-mode is currently copied via the function x-select-text. With the Emacs 24.1 default configuration, this copies to the X-selection CLIPBOARD (configurable through x-select-enable-clipboard and x-select-enable-primary.) In the rest of Emacs, this function is only used for the explicit copy/yank commands. Copying the active region is controlled by the variable select-active-regions and uses the PRIMARY X-selection by default. This behavior is consistent with most other X applications: The mouse selection is saved in PRIMARY and the explicit copy/paste commands use the CLIPBOARD. Thus, it would be nice if Evil would also use the PRIMARY selection by default for the selected text in visual-mode. I currently use the following redefinition of evil-visual-update-x-selection, that does what I need: #+BEGIN_SRC elisp (defun evil-visual-update-x-selection (&optional buffer) "Update the X selection with the current visual region." (with-current-buffer (or buffer (current-buffer)) (when (and (evil-visual-state-p) (fboundp 'x-select-text) (or (not (boundp 'ns-initialized)) (with-no-warnings ns-initialized)) (not (eq evil-visual-selection 'block))) (x-set-selection 'PRIMARY (buffer-substring-no-properties evil-visual-beginning evil-visual-end)) (setq x-last-selected-text-primary )))) #+END_SRC Regards, Hans-Peter

2 1

Towards evil 1.0
by Frank Fischer 01 Nov '12

01 Nov '12

Hi folks, I've just went once again through all open issues in the issue tracker. I marked those that I think should be fixed for 1.0 with "milestone 1.0". The plan is to get them fixed quickly so version 1.0 of evil can be released by the end of the year. I'm not going to investigate any other of the issues until then. If you think other issues are very important and should be dealt with in 1.0, please comment them in the tracker. Of course, any help (submitting patches etc. ;)) is greatly appreciated. Best regards Frank

1 0

Debugger entered--Lisp error: (error "\"Domaine\": pattern not found")
by Guido Van Hoecke 01 Nov '12

01 Nov '12

Hi, Operating steps: 1) /Domaine <enter> 2) c f e Champ <enter> 3) n 4) . 5) n And if the pattern is no longer found, I get a new window with this debugger message: Debugger entered--Lisp error: (error "\"Domaine\": pattern not found") signal(error ("\"Domaine\": pattern not found")) error("\"%s\": %s not found" "Domaine" "pattern") (condition-case nil (funcall search-func string) (search-failed (goto-char orig) (error "\"%s\": %s not found" string (if regexp-p "pattern" "string")))) (let* ((orig (point)) (start (or start (if forward (min (point-max) (1+ orig)) orig))) (isearch-regexp regexp-p) (isearch-forward forward) (case-fold-search (unless (and search-upper-case (not (isearch-no-upper-case-p string nil))) case-fold-search)) (search-func (evil-search-function forward regexp-p evil-search-wrap))) (set-text-properties 0 (length string) nil string) (goto-char start) (condition-case nil (funcall search-func string) (search-failed (goto-char orig) (error "\"%s\": %s not found" string (if regexp-p "pattern" "string")))) (setq isearch-string string) (isearch-update-ring string regexp-p) (when (boundp (quote isearch-filter-predicate)) (funcall isearch-filter-predicate (match-beginning 0) (match-end 0))) (goto-char (match-beginning 0)) (cond ((and forward (< (point) start)) (setq string "Search wrapped around BOTTOM of buffer")) ((and (not forward) (> (point) start)) (setq string "Search wrapped around TOP of buffer")) (t (setq string (evil-search-message string forward)))) (evil-flash-search-pattern string t)) (progn (let* ((orig (point)) (start (or start (if forward (min (point-max) (1+ orig)) orig))) (isearch-regexp regexp-p) (isearch-forward forward) (case-fold-search (unless (and search-upper-case (not (isearch-no-upper-case-p string nil))) case-fold-search)) (search-func (evil-search-function forward regexp-p evil-search-wrap))) (set-text-properties 0 (length string) nil string) (goto-char start) (condition-case nil (funcall search-func string) (search-failed (goto-char orig) (error "\"%s\": %s not found" string (if regexp-p "pattern" "string")))) (setq isearch-string string) (isearch-update-ring string regexp-p) (when (boundp (quote isearch-filter-predicate)) (funcall isearch-filter-predicate (match-beginning 0) (match-end 0))) (goto-char (match-beginning 0)) (cond ((and forward (< (point) start)) (setq string "Search wrapped around BOTTOM of buffer")) ((and (not forward) (> (point) start)) (setq string "Search wrapped around TOP of buffer")) (t (setq string (evil-search-message string forward)))) (evil-flash-search-pattern string t))) (if (and (stringp string) (not (string= string ""))) (progn (let* ((orig (point)) (start (or start (if forward (min ... ...) orig))) (isearch-regexp regexp-p) (isearch-forward forward) (case-fold-search (unless (and search-upper-case (not ...)) case-fold-search)) (search-func (evil-search-function forward regexp-p evil-search-wrap))) (set-text-properties 0 (length string) nil string) (goto-char start) (condition-case nil (funcall search-func string) (search-failed (goto-char orig) (error "\"%s\": %s not found" string (if regexp-p "pattern" "string")))) (setq isearch-string string) (isearch-update-ring string regexp-p) (when (boundp (quote isearch-filter-predicate)) (funcall isearch-filter-predicate (match-beginning 0) (match-end 0))) (goto-char (match-beginning 0)) (cond ((and forward (< (point) start)) (setq string "Search wrapped around BOTTOM of buffer")) ((and (not forward) (> (point) start)) (setq string "Search wrapped around TOP of buffer")) (t (setq string (evil-search-message string forward)))) (evil-flash-search-pattern string t)))) (when (and (stringp string) (not (string= string ""))) (let* ((orig (point)) (start (or start (if forward (min (point-max) (1+ orig)) orig))) (isearch-regexp regexp-p) (isearch-forward forward) (case-fold-search (unless (and search-upper-case (not (isearch-no-upper-case-p string nil))) case-fold-search)) (search-func (evil-search-function forward regexp-p evil-search-wrap))) (set-text-properties 0 (length string) nil string) (goto-char start) (condition-case nil (funcall search-func string) (search-failed (goto-char orig) (error "\"%s\": %s not found" string (if regexp-p "pattern" "string")))) (setq isearch-string string) (isearch-update-ring string regexp-p) (when (boundp (quote isearch-filter-predicate)) (funcall isearch-filter-predicate (match-beginning 0) (match-end 0))) (goto-char (match-beginning 0)) (cond ((and forward (< (point) start)) (setq string "Search wrapped around BOTTOM of buffer")) ((and (not forward) (> (point) start)) (setq string "Search wrapped around TOP of buffer")) (t (setq string (evil-search-message string forward)))) (evil-flash-search-pattern string t))) evil-search("Domaine" t t) (while (< var --cl-dotimes-temp--) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search) (incf var)) (let ((--cl-dotimes-temp-- (or count 1)) (var 0)) (while (< var --cl-dotimes-temp--) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search) (incf var))) (catch (quote --cl-block-nil--) (let ((--cl-dotimes-temp-- (or count 1)) (var 0)) (while (< var --cl-dotimes-temp--) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search) (incf var)))) (cl-block-wrapper (catch (quote --cl-block-nil--) (let ((--cl-dotimes-temp-- (or count 1)) (var 0)) (while (< var --cl-dotimes-temp--) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search) (incf var))))) (block nil (let ((--cl-dotimes-temp-- (or count 1)) (var 0)) (while (< var --cl-dotimes-temp--) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search) (incf var)))) (dotimes (var (or count 1)) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search)) (save-restriction (when (and (not (evil-operator-state-p)) (not (eobp)) (save-excursion (goto-char (point-max)) (bolp))) (evil-narrow nil (1- (point-max)))) (dotimes (var (or count 1)) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search))) (evil-with-adjust-cursor (dotimes (var (or count 1)) (evil-search (if evil-regexp-search (car-safe regexp-search-ring) (car-safe search-ring)) isearch-forward evil-regexp-search))) evil-search-next(nil) call-interactively(evil-search-next nil nil) How can I just get a message in the mini-buffer? I failed to find a variable that I can set to control this behavior. Thanks in advance, Guido.

2 2

ggVG doesn't copy the last line of a buffer
by Dan Rosén 31 Oct '12

31 Oct '12

Hi, This is an issue I have: When I have a file which ends with a non-blank line, then ggVG will copy (and select) the entire buffer, but that last line. ggVG$ works, but that is a bit annoying. Is there a way to make G go to the last character of the last line, and not only the last line? Thanks, Dan

2 1

Change inner paren doesn't work in python mode
by Alessandro Piras 31 Oct '12

31 Oct '12

Hi guys, ci( does not work in python mode. to replicate: --- example.py --- for i in range(10): print (1, 2, 3) --------------------------- position the cursor over the "2" issue ci( result: --- example.py --- f): print (1, 2, 3) -------------------------- Cheers, Alessandro

3 3

Insert mode - point doesn't move to next line
by aditya siram 31 Oct '12

31 Oct '12

I'm having an issue with the master branch where the cursor in Insert mode doesn't always move to the next line with Return or Ctrl-J. I can reproduce this in the following way: 1. open a new buffer with `:new` 2. Go into Insert mode with `i`. 3. Type `hello world` 4. Hit Enter, the cursor goes to the beginning of the line just typed and not the next line. This also happens intermittently in eshell where when I enter a command like `ls` the cursor moves to the beginning of this line rather than the prompt that comes up after the output. Thanks ... -deech

3 6

Normal Mode issues with tab in org-mode
by aditya siram 31 Oct '12

31 Oct '12

In Normal mode when I hit <Tab> on a headline in org-mode it doesn't expand. It works fine in Insert mode. Thanks ... -deech

2 1

tick-dot not working
by Jason Miller 31 Oct '12

31 Oct '12

The normal command '. prints out the following error message: Symbol's function definition is void: goto-last-change Any idea what's going on here? -Jason

2 1

Empty line at EOB
by Frank Fischer 30 Oct '12

30 Oct '12

Hi friends of evil, recently there have been a lot of issues related to the final-newline/empty-line-at-eob behavior of Emacs. Before I try to fix those issue and provoke further issues, I would like to discuss the problem in public. When Vegard and I discussed this topic some time ago, we pointed out several advantages and disadvantages of certain approaches to this problem (see below) and decided for one of them. However, the latest bug reports make clear this may not be so easy (I had somehow the feeling at that time that sooner or later someone *will* come up with bug reports but I hoped that they would be easy to solve -- now I'm not so sure about the latter anymore). The purpose of this post is to initiate a discussion about how the problem should be handled in evil. Let me start with a description of the problem. In the unix world a line is usually defined as a sequence of characters followed by a newline character \n. In other words, the newline character is the termination character of a line. Sequences of characters that do not end in a newline are therefore *incomplete* or non-proper lines (some programs even used to refuse working correctly on incomplete lines). This is also visible in text editors like vim. In vim (in standard configuration) each line is automatically terminated by newline (when saved to disk). Furthermore the number of lines in a file is exactly the number of newlines. If vim opens a file with an incomplete last line then it appends that newline when saving the file back to disk (and showing [noeol] in the status bar). But more importantly, it is *impossible* to move the cursor beyond that last newline. This means if a file contains "abc\n" vim shows one line and the cursor cannot be moved to the second line. Emacs is different. Emacs can also append a missing newline to a buffer depending on the value of `require-final-newline'. The difference is that in Emacs it is possible to move point *visually* to a position after the final newline (point-max) and Emacs shows point on the next line. Thus, in Emacs one has the *visual* impression that the file contains one additional line. In some sense, in Emacs the newline character is rather a line-separator than a line terminator (at least for the visual impression). The trouble for evil are commands like "G". Vim moves point to the last real line, i.e. to a position not behind the final newline. But Emacs would move point to a position after that final newline, giving a slightly different impression. For evil this means that we have two general approaches: 1. Do it the Vim way. This is what we try currently. In this approach we do not allow point to be moved to (point-max). This is done by adjusting point to the previous line if it is moved to point-max (the function `evil-adjust-point' is responsible for this). As a result the behavior is closer to Vim's. The downside is that a) the behavior is different to Emacs-state and b) it causes trouble some modes like eshell, that somehow exploit that the final line does not need to end in a newline. Furthermore it is not trivial to do the right thing in all cases. In particular some Emacs non-evil commands may have problems with evil's point-adjustment. 2. Do it the Emacs way. In this approach we ignore completely the special handling of the final newline. We allow that point is placed on that "additional" line. This is of course a lot easier to implement. But it also breaks compatibility with vim in a not-so-uncommon situation (e.g., the G command behaves differently and the file always looks as if it contains one line more in evil than in vim). Both approaches have their advantages and disadvantages. But the real question is, what users want. Is vim compatibility significant in this situation or can you live with Emacs' behavior? Please feel free to comment and discuss. Best regards, Frank

4 4

Re:implementations-list Digest, Vol 48, Issue 8
by damien.thiriet77 28 Oct '12

28 Oct '12

I agree with previous posts. I think compatibility with other modes is more useful than a full vim behavior implementation. Btw, I didn’t face situations where having G at (max-point) would be a problem. Damien > ------------------------------ > > Message: 4 > Date: Sat, 27 Oct 2012 15:10:24 -0400 > From: Barry OReilly > Subject: Re: Empty line at EOB > To: "vi/Vim emulation in Emacs" > > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > My preference is to avoid conflict with other Emacs modes like eshell and > auto-revert-tail-mode . That it simplifies the Evil implementation is > bonus. >

2 1