comparison lisp/erc/erc-dcc.el @ 75259:f45c5edf0be4

Merge from erc--main--0 Highlights: - Display messages starting with "/" but are not commands correctly. - Add erc-capab.el file, with capab-identify module. - Fix various ERC menu bugs and add "Current channel" submenu. - Make header-line display look nicer. - Fix warning when auto-authenticating to bitlbee. - New option erc-system-name allows the hostname next to your nick to be customized. Revision: [e-mail]/emacs--devo--0--patch-599 Creator: Michael Olson <[e-mail]>

75258:38cd68f9ba51

It reads incoming bytes from the network and stores them in the DCC
buffer, and sends back the replies after each block of data per the DCC
protocol spec.  Well not really.  We write back a reply after each read,
rather than every 1024 byte block, but nobody seems to care."
  (with-current-buffer (process-buffer proc)
    (setq buffer-read-only nil) ;; FIXME
    (goto-char (point-max))
    (insert (string-make-unibyte str))

    (setq erc-dcc-byte-count (+ (length str) erc-dcc-byte-count))
    (erc-assert (= erc-dcc-byte-count (1- (point-max))))
    (and erc-verbose-dcc
         (erc-display-message
          nil 'notice erc-server-process
          'dcc-get-bytes-received
          ?f (file-name-nondirectory buffer-file-name)
          ?b (number-to-string erc-dcc-byte-count)))
    (cond
     ((and (> (plist-get erc-dcc-entry-data :size) 0)
           (> erc-dcc-byte-count (plist-get erc-dcc-entry-data :size)))
      (erc-display-message
       nil '(error notice) 'active
       'dcc-get-file-too-long
       ?f (file-name-nondirectory buffer-file-name))
      (delete-process proc))
     (t
      (process-send-string
       proc (erc-pack-int erc-dcc-byte-count 4))))))


(defun erc-dcc-get-sentinel (proc event)
  "This is the process sentinel for CTCP DCC SEND connections.
It shuts down the connection and notifies the user that the

75259:f45c5edf0be4

It reads incoming bytes from the network and stores them in the DCC
buffer, and sends back the replies after each block of data per the DCC
protocol spec.  Well not really.  We write back a reply after each read,
rather than every 1024 byte block, but nobody seems to care."
  (with-current-buffer (process-buffer proc)
    (let ((inhibit-read-only t))
      (goto-char (point-max))
      (insert (string-make-unibyte str))

      (setq erc-dcc-byte-count (+ (length str) erc-dcc-byte-count))
      (erc-assert (= erc-dcc-byte-count (1- (point-max))))
      (and erc-verbose-dcc
           (erc-display-message
            nil 'notice erc-server-process
            'dcc-get-bytes-received
            ?f (file-name-nondirectory buffer-file-name)
            ?b (number-to-string erc-dcc-byte-count)))
      (cond
       ((and (> (plist-get erc-dcc-entry-data :size) 0)
             (> erc-dcc-byte-count (plist-get erc-dcc-entry-data :size)))
        (erc-display-message
         nil '(error notice) 'active
         'dcc-get-file-too-long
         ?f (file-name-nondirectory buffer-file-name))
        (delete-process proc))
       (t
        (process-send-string
         proc (erc-pack-int erc-dcc-byte-count 4)))))))


(defun erc-dcc-get-sentinel (proc event)
  "This is the process sentinel for CTCP DCC SEND connections.
It shuts down the connection and notifies the user that the